For agencies
The platform for
web agencies.
Ship client sites, portals, B2B tools, and data-rich authenticated experiences from one EU platform. Give every client a clean data and consent answer. Run the whole portfolio by hand or by agent.
The tax of the stack the industry handed you
You build and run experiences for clients who expect them to keep working. These problems are real costs. Nimbu removes each one.
The rebuild treadmill
Every JS framework cycle turns into a rebuild your team absorbs as unplanned cost. The platform re-platforms itself, and the re-estimate lands on your desk. That churn is margin you never see.
Client compliance asks you cannot answer
Where is the customer data hosted, and who can reach it? Most platforms are incorporated in the US, subject to the CLOUD Act regardless of server location. When the DPO asks, 'it's complicated' loses the project.
Five stitched tools for anything real
CMS, shop, multilingual, search, consent. Then for portals and B2B tools: add auth, a custom backend, and integrations. Five vendors, five invoices, five things that can break on launch night.
One platform, one vendor relationship, one place to call when something needs attention.
The answer you put in proposals
Belgian company under APD, EU-hosted customer data, and GDPR consent built into every site. Field-level encryption with EU-held keys. When the client's DPO asks where data lives and who can reach it, you have a structural answer ready, not a follow-up call with a US vendor.
- Belgian company under APD and EU jurisdiction EU law is the law that applies to your client's data.
- EU-hosted data, 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.
Stable on purpose
Sell the same site in 2030 without a rebuild conversation
Git-based Liquid with no build step and no framework upgrade cycle. A theme you wrote three years ago still deploys today. No Gatsby-to-Next-to-Hydrogen churn waiting for you. If your team knows Shopify Liquid, they are productive on day one.
- No build step No pipeline to configure, no framework to upgrade.
- 76 Liquid Drops, 20+ custom tags Full domain coverage: customer, channels, commerce, search, nav, paginate.
- Every avoided rebuild is margin you keep No re-estimate to send a client because the platform changed.
One platform instead of five stitched tools
CMS-grade Channels, real commerce backend, native multilingual, search, consent, and the authenticated app primitives in one system. One vendor relationship, one support queue, one place to call when something needs attention on launch night.
- One vendor, one support queue Not five contracts to renew and five things that can fail on launch night.
- One data model for content + commerce + custom data No sync layer, no second dashboard, no separate infra.
- European gateways first-class Mollie, Stripe, MultiSafepay, PayPal, and Adyen built in.
Your developers and your AI agents speak the same CLI
The whole platform is programmable. The same nimbu CLI your team runs is the one an agent drives, building and operating real sites, models, customer data, commerce, and logic over authenticated flows today. One toolchain for everyone.
- nimbu CLI ships as an open agent skill Claude Code, GitHub Copilot, and 35+ agents. One-line integration.
- JSON and TSV output, readonly mode, allowlists Hand an agent exactly as much access as you want it to have.
- Routine client work runs by hand on Tuesday, by agent on Wednesday No second toolchain to learn.
From daily production
Four years, zero platform rebuilds or backend glue layers for the logged-in tools. That is margin we used to lose every cycle.
Common questions
Yes. Client sites carry your work, not a Nimbu badge. You own the client relationship, the build, and the ongoing retainer. Nimbu is the platform underneath.
Your client does. Customer data is EU-hosted and reachable over the REST API and the CLI. It is never boxed in by what the platform decided to support.
Yes. The dashboard handles content, commerce, and custom Channels with draft and published states and role-based access. You decide how much access each client gets.
Nothing forced. No framework migration event at end of term. A theme from three years ago still deploys. Renewal is a continuation, not a re-platform you have to sell.
Yes, both directions. Content, products, and orders move in and out over the REST API and the CLI, by hand or by agent. No lock-in holding your data hostage.
When something breaks, you talk to people who wrote the code, not a tier-1 ticket queue. For an agency on a client launch, that is the difference that matters.
See Nimbu on your own client work
Book a 30-minute intro call. We reply personally to schedule it. We will walk through your client portfolio, including portals and B2B tools, and how your team and agents run the full surface from one platform. A live site needs a provisioned account, which we set up with you.
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.