Contentful is now a Salesforce product
Your data. Your jurisdiction.
Not theirs.
Salesforce completed its acquisition of Contentful in June 2026. The platform changed hands. The questions about who owns your clients' data, who controls the roadmap, and who can reach it under US law now have a different answer. Nimbu is an independent Belgian company. We host your data in the EU, ship Liquid delivery, and have built-in commerce. We are not on our way into anyone else's stack.
Brussels, not Washington
The structural change in an acquisition is jurisdiction. Contentful is US-incorporated and runs on US cloud infrastructure with US subprocessors. Salesforce is a US company. Any CMS platform incorporated in the United States is reachable by US authorities under the CLOUD Act, regardless of where its servers sit. A data-residency toggle set to EU does not change how the company is organised.
Nimbu is built and run by Zenjoy, a Belgian company under EU jurisdiction, regulated by the APD. Customer data is hosted in the EU. GDPR consent and cookie management ship inside the platform. Sensitive customer fields are encrypted at rest with keys held in the EU.
For an agency building for healthcare, legal, finance, or public-sector clients, the platform you choose is your client's compliance posture. After the acquisition, the sentence you'd be putting in the proposal is: our CMS is a Salesforce product hosted in the US.
APD registration, a downloadable DPA, and EU hosting detail are in our Trust center.
A platform that is not on its way into someone else's stack
What unsettles an agency about an acquisition is what comes after the deal. Pricing restructures around enterprise sales. The roadmap bends toward the parent's priorities, not yours. Features you depend on get folded into a suite, or sunset. Nimbu is bootstrapped and independent. No outside investors, no board steering toward an exit. No acquisition overhang and no pressure to re-platform you to fit someone else's product strategy.
- Bootstrapped, no outside investors We answer to customers, not to an acquirer's integration roadmap.
- Git-based Liquid, no build step A theme from three years ago still deploys. No framework upgrade cycle you absorb as unplanned cost.
- Stable contracts and pricing No restructure toward an enterprise sales motion after a deal closes.
Delivery and commerce
Structured content parity, plus what Contentful leaves out
You model content with Channels and Custom Fields: text, select, relations, gallery, geo, date, calculated, encrypted, and localized field types. You add a field without running a migration. Contentful leaves delivery and commerce to you. Nimbu includes both.
- Delivery. Contentful is headless-only. Nimbu ships content over Liquid, with 76 Drops and 20+ tags. A Shopify-Liquid developer is productive on day one. You still go headless over the REST API when a project calls for it.
- Commerce. Contentful has none. Nimbu has commerce built in: variants, pricing schemes, a 13-state order machine, coupons, gift cards, customer groups, and EU gateways.
- Multilingual. Around 40 locales, translated products, and language-aware Elasticsearch. Not a workaround.
Contentful vs Nimbu, line by line
Stated factually. The differences that matter to an agency are structural, not cosmetic.
| Dimension | Nimbu | Contentful |
|---|---|---|
| Company and ownership | Independent Belgian company, bootstrapped | Salesforce product, US-incorporated, acquired June 2026 |
| Jurisdiction | Belgian company, APD regulated, EU law | US-incorporated, US subprocessors, CLOUD Act exposure |
| Customer data hosting | EU-hosted data | US cloud infrastructure |
| GDPR consent management | Built into the platform | Third-party tool you add and re-audit |
| Sensitive-field encryption | Field-level, EU-held keys | Not specified for EU agencies |
| Content delivery | Liquid themes, no build step, plus headless option | Headless-only, you maintain a JS frontend |
| Commerce | Built in: variants, orders, gift cards, EU gateways | None, stitch a separate platform |
| Native multilingual | Around 40 locales, translated products, language-aware search | Localization for content, no native commerce locale |
| Server-side logic | Cloud Code in-platform, sandboxed runtime, curated modules | External functions you host |
| Add a content field | No migration | Model change, may require content migration |
| Agent operation | Agents build and operate sites today, CLI as open agent skill | AI assists inside the UI |
| Built for | Agencies running many client sites | Enterprise marketing teams |
What Contentful does better
We'd rather you hear this from us than find it later.
Enterprise integrations
A mature integration ecosystem
Contentful has a deep catalog of pre-built connectors. If your clients already run on Salesforce, Contentful now sits natively in that world. That fit is real and gets tighter after the acquisition.
Global CDN footprint
Built for very large content operations
Contentful's content-modeling tooling and CDN are built for multi-brand content operations across many regions and teams. If that is the shape of your work, it is a serious platform.
Self-qualifier
When Nimbu is probably not the right move
If a deep Salesforce integration is the center of your stack, or if you need an enterprise-scale global content operation across dozens of brands, Contentful is the more natural home. We'd rather tell you that now than six weeks into a migration.
From the field
When the acquisition closed, the first thing our clients asked was who now owns their data and what law applies. With Nimbu, that conversation is straightforward: Belgian company, EU hosting, APD. We had the answer in the proposal before the client asked.
Bring a real content model. We'll map it live.
Book a 30-minute call and bring a Contentful project. We will map your content types to Channels and Custom Fields live, and walk the migration path. 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.