Nimbu vs Shopify
Built for agencies.
Shopify is built for merchants.
Shopify is a good platform for one merchant running one brand. Your agency builds and runs many client sites at once, carries them for years, and answers for where their data lives. Nimbu is built around that portfolio instead: EU jurisdiction, native GDPR consent, content and commerce in one model, and no app-stack tax or rev-share ceiling between your work and your margin.
The rev-share ceiling and the app-stack bill
On Shopify, the merchant is Shopify's customer. Your agency is the channel. The Partner Program places a recurring-revenue ceiling on your referral share, and every time the program terms change, your margin model changes with them.
Partner rev-share ceiling
You build the store, the merchant pays Shopify, and you earn a referral share that sits behind a ceiling and the program's current terms. The merchant is Shopify's customer.
The app-stack tax
Advanced consent, structured content, deeper localization, and bespoke checkout logic are not in core Shopify. They come from apps with their own monthly fees that land in your client's proposal and your conversations.
White-label on Nimbu
You build on Nimbu directly, run client sites from one account, ship them under your own banner, and price the project on your terms. No rev-share ceiling. No app stack to defend line by line.
One white-label platform. The commercial relationship is between you and your client.
An answer you put in the proposal
Shopify is incorporated in North America and runs on US cloud infrastructure. A US-incorporated platform is reachable by US authorities under the CLOUD Act regardless of where the servers sit. GDPR consent on a Shopify store comes from a third-party app you configure and re-audit separately.
Nimbu is built and run by Zenjoy, a Belgian company regulated by the APD. Customer data is EU-hosted. Consent is in the platform: model purposes and cookies, then drop a privacy-first banner into any theme with one Liquid tag. Sensitive customer fields are encrypted at rest with EU-held keys.
- Belgian company under APD and EU law EU jurisdiction is the structural answer for a client's legal team.
- EU-hosted customer data No US-parent CLOUD Act reachability over your client's records.
- Consent in the platform One consent_manager tag replaces a third-party CMP and a class of audit risk.
- Sensitive fields encrypted with EU-held keys Field-level, part of the Custom Field model.
Developer control
Backend logic inside the platform, not through an app layer
On Shopify, control past a certain point means leaving the platform: custom server-side logic runs through external Functions, and content modeling beyond product fields means an app. Online Store 2.0 and Hydrogen were real shifts your team absorbs as a rebuild.
Nimbu gives you backend control without a separate frontend stack or servers to own. Liquid themes you already know. Cloud Code for functions, custom routes, scheduled jobs, and callbacks, running on a sandboxed runtime with a curated module library. A full REST API with 200+ documented endpoints. And fields you add without a migration.
- Liquid you already know Git-based Liquid themes, no build step. 76 Drops expose the full domain.
- REST API, 200+ endpoints OAuth2 and OpenID Connect, versioned contract, webhooks on content and commerce events.
- Fields without migrations Channels and Custom Fields let you add a field without a migration or an app.
An operator on the platform, not an assistant in the UI
Shopify's AI is Sidekick: it helps a person work inside Shopify's admin. It answers questions and speeds up clicks for the merchant at the keyboard.
Nimbu is built so an agent operates the real platform. Because Nimbu is API-first, fully CLI-driven, and runs server-side Cloud Code, an agent can push a theme, create a product, run a Cloud Code function, and deploy on a live site. The nimbu CLI ships as an open agent skill for Claude Code, GitHub Copilot, and 35+ agents. JSON and TSV output, OS-keychain auth, readonly mode, and command allowlists: hand an agent exactly as much as you want it to have.
The dimensions that matter to an agency
Named directly, stated factually. The differences are structural, not cosmetic.
| Dimension | Nimbu | Shopify |
|---|---|---|
| Built for | Agencies running a client portfolio | Single merchants running a brand |
| Jurisdiction and data | Belgian company, APD, EU-hosted customer data | North America incorporated, US cloud (CLOUD Act reachable) |
| GDPR consent | Native consent_manager tag, CDN-served script | Third-party consent app, separate configuration |
| Sensitive-field encryption | Encrypted at rest, EU-held keys, field-level | Per app or merchant configuration |
| CMS and content modeling | Channels and Custom Fields, no migrations | Thin; apps or workarounds needed |
| Commerce depth | Variants, pricing schemes, 13-state orders, gift cards | Deep, often via paid apps |
| Multilingual | Native, language-aware search, included | Via apps or Markets |
| Server-side logic | Cloud Code in-platform, curated modules | External Functions and app layer |
| Agent operation | CLI as open agent skill, agent operates the site | Sidekick assists in the admin UI |
| Agency model | White-label, you own the client relationship | Partner rev-share, Shopify owns the merchant |
| Payment gateways | Mollie, Stripe, MultiSafepay, PayPal, Adyen | Broadest in market, global coverage |
What Shopify does better
An honest read of the gaps
A comparison that only flatters one side is not worth reading. Shopify is genuinely stronger in a few places, and for some projects those strengths decide it.
Ecosystem size
Shopify's app store and theme marketplace are the deepest in commerce. If a niche capability exists, there's probably a Shopify app for it. Nimbu's answer is a complete core plus Cloud Code, not thousands of add-ons.
Payment-rail breadth
Shopify Payments and its gateway coverage are best-in-class worldwide. Nimbu covers the European gateways agencies use most (Mollie, Stripe, MultiSafepay, PayPal, Adyen) but does not match Shopify's global breadth.
SME brand recognition
Many merchants already know the Shopify name. For a high-volume single-brand DTC store where global payments and app depth matter more than EU jurisdiction, Shopify is often the right choice.
Who Nimbu is right for
Nimbu fits if you recognise your agency here. If it does not, we will tell you so.
-
You run many client sites
One platform and one dashboard, not a fresh stack each project.
-
Your clients ask where their data lives
A clean EU-jurisdiction answer in the proposal, not a consent app you re-audit every quarter.
-
The project is content and commerce together
Multilingual sites, structured content, and products and checkout in one model.
-
You want themes that last
No rebuild events. Git-based Liquid that deploys years from now without framework churn.
-
You want server-side control
Without owning a frontend stack or your own infrastructure.
-
You want an agent to run routine client work
A platform the agent can actually operate, not just assist in the UI.
We moved three Shopify clients to Nimbu and stopped paying for a separate consent app and four other monthly add-ons. One dashboard, one EU answer for legal, and the margin improvement was immediate.
See it on your own client work
Bring a real client project: a store you are scoping or one you are tired of carrying on Shopify. We will walk through what it looks like on Nimbu, migration included. We reply personally to schedule.
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.