Platform overview
One platform for sites,
portals, and authenticated work.
Complex data models, customer accounts, commerce, multilingual, search, Liquid themes or headless, Cloud Code, and a 200+ endpoint REST API. EU-hosted, agent-native, stable on purpose. Stop stitching five tools per client project.
One system, not five contracts
Most agencies assemble a client site from at least five vendors: a CMS, a shop, an i18n layer, search, consent, and a separate backend for anything behind login. That is five contracts, five integration seams, and five things that can break on launch night. Nimbu is one system. The same content and custom data model feeds Liquid themes and a headless frontend. Commerce, multilingual, search, customers, and your complex logic are part of the core.
Five vendors, five failure surfaces
CMS, commerce, consent, search, and translation for the public site. Auth, a backend layer, and workflow integrations for anything behind login. Five contracts, five update cycles, and one seam that fails on launch night.
One platform for every client experience
The same data model feeds Liquid themes and a headless frontend. Commerce, multilingual, search, customers, and logic are part of the core, not bolted on. One update cycle, one dashboard, one support queue.
EU infrastructure, not a setting
Belgian company under APD jurisdiction. EU-hosted customer data. Field-level encryption with EU-held keys. GDPR consent built into the platform with one Liquid tag. A structural answer for your client's legal team.
One data model, one API, one boundary. Inside EU infrastructure.
Start where your concern is
Each capability has its own page. Pick the one that matches your current question.
Agent-native
Agents build and operate real sites
The nimbu CLI ships as an open agent skill for Claude Code, GitHub Copilot, and 35+ agents. API-first, CLI-driven, with server-side Cloud Code.
CMS and data modeling
Channels and Custom Fields, no migrations
Structured content and complex data with relations, calculated, encrypted, and localized values. Add a field to a live type without a migration.
Commerce
Built in, not bolted on
Variants, pricing schemes, a 13-state order machine, coupons, gift cards, customer groups, and EU gateways.
Themes and Liquid
Git-based Liquid, no build step
A theme from three years ago still deploys. 76 Drops and 20+ tags. The same model for gated and public experiences.
Cloud Code
Server-side logic inside the platform
Functions, custom routes, scheduled jobs, and callbacks on customer and order events. Sandboxed V8, curated modules, no infra to stand up.
REST API
200+ endpoints, one versioned contract
OAuth2 and OIDC, webhooks, and a versioned contract. The same API powers the dashboard, the CLI, Cloud Code, and any agent.
Multilingual
Locales, translated products, language-aware search
Per-site locales, translated products including pricing and checkout, and language-aware Elasticsearch. Included, not bolted on.
EU and privacy
A trust answer for the proposal
Belgian company under EU jurisdiction. EU-hosted data, consent in the platform, field-level encryption with EU-held keys.
How it fits a typical agency workflow
Build, hand off, edit, iterate. By hand or by agent.
A developer who knows Shopify Liquid is productive on day one: same layouts, templates, snippets, and assets. The client gets a CMS-grade editor with draft, scheduled, and published lifecycle. Everything reachable in the dashboard is reachable over the REST API and the CLI.
- Build with Liquid or headless Git-based themes, no build pipeline. Or point any frontend at the REST API.
- Hand off a real editor Draft, scheduled, and published lifecycle. SEO fields, audit trail, consent in one Liquid tag.
- Iterate, by hand or by agent The nimbu CLI ships as an open agent skill for Claude Code, GitHub Copilot, and 35+ agents.
Fewer seams, not more features
Completeness is about owning fewer integration points, not accumulating features. Here is what changes when the platform is one piece instead of five.
One platform to learn, then reuse
CMS, commerce, multilingual, search, and consent in one core. One thing to learn on the first project, then reuse on every client site without reassembly.
One contract, one roadmap
Five vendors become one vendor relationship. One renewal date, one place the data lives, one roadmap to follow.
One dashboard for the whole portfolio
Manage every client site from one screen. No five logins, no five dashboards.
One call on launch night
One support queue, talking to the people who wrote the code. Not five tier-1 queues pointing at each other.
No integration work to redo
The cost of a stitched stack is the integration work you redo on every project and the failure surface you carry for years after launch.
- 15+
- years in production
- 300+
- sites and shops
- 550K+
- orders processed
- 200+
- API endpoints
We run our whole client portfolio from one dashboard. One thing to learn, one contract, and when something needs attention on launch night, there is one number to call.
A trust answer you can put in a proposal
When the client's legal team asks where data lives and who can reach it, Nimbu gives you a structural answer, not a setting you found in a dropdown.
-
Belgian company under APD and EU jurisdiction
EU law applies to your client's data. Not a US-incorporated parent under the CLOUD Act.
-
Customer data hosted in the EU by architecture
Not a region setting that depends on a data-transfer framework a court can invalidate.
-
GDPR consent built into the platform
Model consent purposes once, then drop them into any theme with one Liquid tag.
-
Sensitive fields encrypted at rest with EU-held keys
Field-level encryption, part of the Custom Field model. DPA available on request.
See Nimbu on your own client work
Book a 30-minute intro call. We reply personally to schedule it, then walk Nimbu against a real project from your portfolio.
Request received.
We read every request personally and will get back to you to schedule the call.
Book a demo
We reply personally to plan a 30-minute call.
Something went wrong while sending. Please try again in a moment.