Skip to content

For developers

The whole platform from
your terminal.

Liquid, a 200+ endpoint REST API, server-side Cloud Code, and a CLI that ships as an open agent skill. Drive it by hand or hand it to an agent. No mystery framework, no build pipeline to configure.

terminal ~ nimbu
# install + local dev in three commands
$ brew install nimbu
$ nimbu auth login
$ nimbu init my-site && nimbu server
local dev server running on :3000
$ nimbu themes push
40 files pushed. Site is live.

Hand the CLI to your agent. It operates the real platform.

The nimbu CLI ships as an open agent skill with one-line integration for Claude Code, GitHub Copilot, Cursor, VS Code, Gemini CLI, OpenAI Codex, and 35+ agents. JSON and TSV output, OS-keychain auth, readonly mode, and command allowlists. You decide what the agent can touch.

  • JSON and TSV output Every command returns structured data an agent can parse.
  • Readonly mode and allowlists Scope what the agent can do without revoking credentials.
  • 35+ agents supported Claude Code, Copilot, Cursor, VS Code, Gemini CLI, Codex, and more.

200+ endpoints. One surface for content, commerce, customers, and search.

The REST API is the architecture. Content models, products, orders, customers, groups, and search are all queryable from one surface. OAuth2 and OpenID Connect, granular scopes, a versioned contract, and webhooks on content, commerce, and customer events. Whatever the platform stores, you can read and write programmatically.

  • OAuth2 and OpenID Connect Granular read/write scopes. OIDC for authenticated portals.
  • Versioned contract No surprise breaking changes between deploys.
  • Webhooks on every event Content publish, order state, customer creation, and more.
api-query.sh
# query products over the REST API
$ curl https://api.nimbu.io/v1/products \
$ -H "Authorization: Bearer $NIMBU_TOKEN" \
$ -G --data-urlencode "q=linen"
{ "count": 2, "results": [{ "name": "Linen Apron", "price": "29.00" }] }

Cloud Code

Server-side logic without standing up infrastructure.

Functions, custom HTTP routes, cron-scheduled jobs, and callbacks on customer and order events. Sandboxed V8 runtime with a curated module library: http, crypto, jwt, csv, pdf, s3, mail, mollie, and more. Common cases covered. No Lambda to babysit, no separate serverless stack to provision.

  • Test before it touches production Use @nimbu/testing with in-memory fixtures.
  • Curated modules included http, crypto, jwt, csv, pdf, s3, mail, mollie, and more.
  • Customer context available request.customer in scope, no extra credentials.
cloud-code/pricing.js
// custom HTTP route recalculates an order total
$ Nimbu.defineRoute("POST", "/hooks/recalculate-pricing", async (req, res) => {
$ const order = await Nimbu.orders.find(req.body.order_id);
$ const total = order.items.reduce((sum, i) => sum + i.qty * i.unit_price, 0);
$ await Nimbu.orders.update(order.id, { recalculated_total: total });
res.json({ ok: true, total });
$ });

No build step. No framework lock. No migrations.

Themes are Git-based Liquid. Content models flex without a redeploy. EU data handling built in from day one.

Git-based Liquid themes

76 Drops expose the full domain to your templates. 20+ tags cover what content sites need: nav, paginate, search, cache, seo_metadata, consent_manager. A theme you wrote three years ago still deploys.

Content modeling without migrations

Channels plus dynamic Custom Fields (text, select, relations, gallery, geo, date, calculated, encrypted, localized). Add a field on a live type. Existing entries keep working.

No build step

Write Liquid, push, the site is live. No Gatsby-to-Next churn waiting. A Git diff is a deploy, not a build artifact.

EU data handling included

Belgian company under APD. EU-hosted customer data. GDPR consent built in. Sensitive fields encrypted at rest with EU-held keys.

Copyable prompts. Tested and ready to hand to your agent.

Adjust the site name and field values for your project, then paste into Claude Code, Copilot, Cursor, or any agent running the nimbu skill.

prompts.txt
prompt 1: create a products template with pagination
Using the nimbu CLI skill, create a "products" theme template that lists all
products in the current site with pagination of 24 per page, then push the theme.
prompt 2: add a custom field to a channel
Using the nimbu CLI skill, add an integer custom field "reading_time" to the
"blog" channel, then list the channel's fields back to me as a table.
prompt 3: Cloud Code route with tests
Using the nimbu CLI skill, write a Cloud Code HTTP route that recalculates an
order total from its line items, add a @nimbu/testing test with in-memory
fixtures, and run the test before deploying.

Resources

Everything you need to build with Nimbu.

Reference

Docs

The full platform reference: Liquid, Cloud Code, CLI, and API. Start here.

docs.nimbu.io

Platform

REST API

200+ endpoints, OAuth2, webhooks, and the full data model reference.

API reference

Platform

Cloud Code

Functions, routes, jobs, and callbacks. Curated modules. No infra to manage.

Cloud Code docs

Platform

Liquid themes

76 Drops, 20+ tags, Git-based deploys. If you know Shopify Liquid, you are productive on day one.

Themes reference

Platform

Agent-native CLI

Open agent skill for Claude Code, Copilot, Cursor, and 35+ others. One-line install.

Agent-native

Our devs shipped the first client site the same week. Liquid they already knew, the CLI handled the rest, and handing it to the agent for the repetitive scaffolding saved us a full day on the first project.

Lead developer, Zenjoy

Start with the docs, or put a real project on Nimbu.

You can read the docs, install the CLI, and wire up the agent skill right now. A live production site runs on a provisioned account. When you are ready, book a demo and we will set it up.