Skip to content

Structured content.
EU-owned.

Model complex data with Channels and Custom Fields, power customer logins with Cloud Code context, and deliver in Liquid or over REST. Add a field without a migration. Built and run by an independent Belgian company.

Explore the docs Book a demo
nimbu channels
# add a field to a live channel, no migration
$ nimbu channels:fields:create articles --name subtitle --type text --localized
field created. Available in the editor and over the API now.
# query entries over REST
$ curl https://api.nimbu.io/v1/channels/articles/entries -H "Authorization: Bearer $TOKEN"
200 OK entries returned.

Channels and Custom Fields that bend to the project

Content types in Nimbu are Channels: structured types you define for whatever a project needs. Each holds Custom Fields that cover the real shape of content data. Add a field to a live Channel and existing entries keep working. No schema migration, no downtime, no content freeze.

  • Relations across Channels Link entries across content types with a typed relation field.
  • Encrypted fields with EU-held keys Mark a field encrypted and its values are protected at rest.
  • Localized on any field Turn any field per-locale. One model, all languages.
  • Calculated fields Values derived from other fields, no extra logic layer.
Explore the docs
Channels + Custom Fields
// field types: text, select, relations, gallery, geo,
// date, calculated, encrypted, localized
$ nimbu channels:fields:create articles \
$ --name subtitle --type text --localized
field created. No migration required.
// existing entries keep working immediately

A theme layer that outlives redesigns

Channels surface in templates as Drops. 76 Drops expose the full domain, and 20+ custom tags cover navigation, pagination, search, caching, inline editing, SEO metadata, and consent. Shopify-Liquid developers are productive on day one. When you want headless, the same model serves a static or JS frontend over REST without a second source of truth.

  • Git-based themes, push-to-deploy No build pipeline. A theme you write today works in three years.
  • 76 Drops, full domain access Articles, products, customers, orders, search, all reachable in templates.
  • Headless when you need it REST API delivers the same content to any frontend without a second source of truth.
Explore themes
templates/article.liquid
{% for article in channels.articles.entries %}
<h2>{{ article.title }}</h2>
<p>{{ article.subtitle }}</p>
<time>{{ article.published_at | date: "%B %e, %Y" }}</time>
{% endfor %}

Editorial lifecycle

Draft, schedule, publish. ACLs. Audit trail.

Every entry moves through a draft, scheduled, published lifecycle. Editors work without touching the live site. Content goes live when it is meant to, not the moment someone hits save.

01

Draft and scheduled publishing

Editors stage changes, schedule a launch date, and see the exact state of every entry. The live site stays clean until the moment it's meant to change.

02

SEO fields and ACLs built in

Title, description, and metadata on every entry, rendered via seo_metadata. ACLs so the agency controls who edits what. A client touches their own content, not the template layer.

03

Audit trail

Every change is recorded with who made it. When a client asks why a page reads differently than last week, the answer is there.

A clean editor with nothing they can break

Your clients see the fields you defined, in the language they work in, with nothing exposed that could detonate a layout. The model is yours to shape. The client sees only what that client should touch.

  • No template code exposed The editor shows content fields only. The Liquid layer is invisible to clients.
  • Localized fields as per-language inputs A field marked localized shows as a per-language tab, no translation plugin required.
  • Relations as pickers, not raw IDs Relation fields render as a content picker. Editors link entries without knowing the underlying model.
  • Around 40 content locales Native multilingual for Belgian clients editing in NL and FR without a plugin stitched on top.
  • Fewer breakage emails Field definitions constrain what editors can do. Fewer accidents, fewer rollbacks, fewer support requests.

The same content, over REST and the CLI

Everything in the editor is reachable over the API. The same REST API that powers the dashboard: OAuth2, OpenID Connect, a versioned contract, and 200+ documented endpoints. The CLI drives content the same way it drives themes, products, and translations. Scriptable end to end, with JSON output for tooling and agents.

Explore the API
nimbu channels
# list entries as JSON for tooling
$ nimbu channels:entries:list articles --format json
[{...}, {...}] // versioned REST contract
# create an entry from a script or agent
$ nimbu channels:entries:create articles --field title="Spring lookbook" --field status=draft
entry created.

Independent. EU-owned.

Re-evaluating after a recent acquisition?

If a platform decision got made for you, the question underneath is ownership. Who controls the platform your client content lives on, and what happens to it next.

Nimbu is built and run by Zenjoy, a Belgian company under EU jurisdiction, regulated by the APD. Independent, no acquisition pending, no parent company roadmap to answer to. Your content model, themes, and data stay reachable over the REST API and CLI at all times.

See how Nimbu compares to Contentful for a content team.

We model every client's content the same way and add fields mid-project without a single migration. Three years in, the themes still deploy and the clients stay in their lane.

Technical lead, Zenjoy

Start modeling content without the rebuild

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

Explore the docs Book a demo