Build client sites
you won't rebuild.

One platform for CMS, commerce, multilingual and search. Git-based themes you deploy for years, with no framework churn and no migrations. Built in Belgium, hosted in the EU, with consent included.

Book a demo Explore the docs

YOU BUILD

theme / blocks

HERO

FEATURE

CARDS

$ git push deployed.

THEY EDIT, SAFELY

visual editor LIVE

HERO

FEATURE

CARDS

Trusted to build and run authenticated tools and sites across Europe

15+
years in production: 300+
sites and shops: 550K+
orders processed

The work that pays keeps turning into a one-off

Portals, B2B tools, member areas. On most stacks they start as logged-in views and become a custom backend your team runs for years.

The brief said views and files

The scope grows into relational data, per-customer pricing, group access, and workflows. A portal or B2B build routinely runs over quote and months past plan, and you cannot resell the approach on the next client.

Five vendors for one experience

CMS, commerce, consent, search, and translation for the public site. Auth, a backend layer, and workflow integrations for what sits behind login. Five contracts, five update cycles, and one seam that fails on launch night.

Then the frontend keeps moving

Six months later a dependency goes stale or a major version lands. Yesterday's deploy needs a migration before tonight's release. You send the re-estimate, and the client asks why the platform changed.

One model for login, complex data, commerce, and content. Here is how.

One model for login and complex data

Channels and Custom Fields, first-class customer accounts and groups, and Cloud Code with the logged-in customer in context. Build portals and B2B tools without stitching a backend or owning infrastructure.

Flexible data without migrations Add a field to a live type; existing entries keep working.
Customers and permissions first-class Accounts, groups for B2B access and pricing, fields encrypted with EU-held keys.
Same model, same API, any delivery Render in Liquid or point any frontend at the REST API. One source of truth.

Explore the platform

cloud-code/auth.js

// gate a B2B view on the logged-in customer

$ const customer = request.customer

$ if (!customer.groups.includes('vip')) return deny()

$ const price = recalculatePricing(customer, cart)

// request.customer context, no extra creds

For your developers

Agents build and run real Nimbu sites today

This is not a roadmap. Because Nimbu is API-first, fully CLI-driven, and runs server-side Cloud Code, an agent drives the real platform end to end. The nimbu CLI ships as an open agent skill for Claude Code, GitHub Copilot, and 35+ other agents.

How agent-native works

Diagram of the agent loop: an agent makes a change, the site updates, and a live preview comes straight back

One platform, not five stitched tools

A CMS, a BaaS, a consent tool, search, and a custom backend: five logins, five bills, five things that can fail on launch night. Nimbu is one data model, one update cycle, one place to look.

Data modeling and customers

Commerce

Variants, pricing schemes, a 13-state order machine, gift cards, customer groups, and EU gateways.

Cloud Code

Functions, custom routes, scheduled jobs, and callbacks on customer and order events. Curated modules, testable, no infra.

REST API

200+ endpoints, OAuth2 and OIDC, webhooks, a versioned contract. The same API powers everything.

Multilingual and search

Native locales, translated products, pricing and checkout, and language-aware Elasticsearch. Included, not bolted on.

European by construction

The closer you can hand to a client's legal team

When the DPO asks where customer data lives and who can reach it, Nimbu gives you a structural answer you put in the proposal.

Belgian company under APD and EU jurisdiction

EU law is the law that applies to your client's data.
EU-hosted customer data and GDPR consent built in

One consent_manager tag replaces a third-party CMP and a class of audit risk.
Sensitive fields encrypted at rest with EU-held keys

Field-level, part of the Custom Field model. Not a US-incorporated parent under the CLOUD Act.

When the client's legal team asked where the data lived and who could reach the authenticated parts, we had the EU jurisdiction and DPA answer in the proposal, and the platform that actually delivered the portal.

Technical lead, Zenjoy

How Nimbu compares

Where Nimbu sits against the usual options agencies weigh.

Nimbu compared with Typical US SaaS CMS
Dimension	Nimbu	Typical US SaaS CMS
Jurisdiction	Belgian company, APD, EU law	US-incorporated, CLOUD Act reach
Data hosting and encryption	EU-hosted, field-level EU keys	Region setting, US parent
Consent and cookies	Built in (consent_manager)	Separate tool
Login and complex data	Customers, groups, Cloud Code in one model	Limited or external glue
Build step	None, Git-based Liquid	Framework-dependent
Add a field	No migration	Often a migration
Commerce	Included, B2B rules	Add-on or separate platform
Agent-native	CLI as open agent skill, API-first	Partial

See Nimbu on your own client work

Book a 30-minute intro call. We reply personally to schedule it.