The site you ship this year
still deploys next year.
No build step. No framework upgrade cycle your team absorbs as unplanned cost. Git-based Liquid themes deploy in seconds, roll back in one command, and stay working for years.
Git, Liquid, push, roll back
A Nimbu theme is plain files in a Git repo: layouts, templates, snippets, and assets. Liquid renders them. No bundler to configure, no JS framework to pin, no build pipeline to keep green.
Edit locally, commit, push. nimbu themes push deploys. Your theme history lives in Git, so reviewing a change is a diff and reverting one is a checkout.
- No compile step What you push is what runs. The file and the rendered page are the same thing.
- Rollback in one command Every deploy is versioned. Roll back to any known-good state without touching the database.
- History in Git, not a vendor dashboard Diff a change, revert a file, branch for a client experiment. Standard tools, standard flow.
Shopify-Liquid devs already know the structure
Same engine. Same layouts, templates, snippets, and assets. The mental model transfers, so onboarding is reading a few tags rather than learning a platform.
Beyond a storefront, the surface is wider. 76 Liquid Drops expose the full domain to your templates. 20+ custom tags cover what real client sites ask for: navigation, pagination, language-aware search, fragment caching, inline editing, SEO metadata, and GDPR consent in one tag.
- 76 Liquid Drops Site, page, products, cart, customer, menus, channels, and more. The data a content site needs is already in scope.
- 20+ custom tags nav, paginate, search, cache, inline editor, seo_metadata, consent_manager, and more.
- Familiar structure from day one Layouts, templates, snippets, assets. Read the tags, then ship.
Stable doesn't mean frozen
The platform moves. Your themes don't have to.
A modern, maintained core runs underneath every theme. Security and CVE mitigation handled at the edge. You get an actively kept platform without the usual bill: the rebuild.
Ruby on Rails, Liquid, Puma
The core stack is current and actively maintained. No stale dependencies sitting under your client sites.
CVE mitigation at the edge
Security hygiene is handled at the platform level. Patches reach every site without a deploy on your side.
No Gatsby-to-Next-to-RSC churn
The rendering contract you write against is Liquid. Liquid is stable on purpose. We move the platform forward. You don't rebuild to keep up.
Every avoided migration is a re-estimate you never send
Framework churn is a real line item. Each forced upgrade means scoping, testing, regression-hunting, and a difficult conversation with a client who can't see what they're paying for.
Across a portfolio of client sites, that recurring tax is the quiet thing eating agency margin. Git-based Liquid with no build step takes that line item off the table.
Scope it once
A theme from three years ago still deploys today. The re-platform you would otherwise scope every couple of years becomes a re-estimate you never have to send.
Hours go to client work, not chasing a framework
The hours you would have spent on dependency upgrades and migration testing go to billable work instead. That margin compounds across a portfolio.
Predictable roadmap
We publish what ships and what we deliberately won't build. Plan against the platform with confidence.
We publish what changes and what we deliberately won't build, so you can plan against the platform with confidence.
Scriptable, reviewable in CI, drivable by an agent
Themes are managed from the command line. The same workflow an agency developer runs by hand is the one an AI agent can run end to end: push a theme, sync a site, deploy a fix, on a real site, today.
From the field
Four years, zero platform rebuilds across our client portfolio. We ship updates, not re-platforms. That alone has kept margins healthy and clients confident.
Build on a platform that won't make you rebuild it
Git-based Liquid. No build step. No framework upgrade cycle. The themes you ship keep deploying, and the margin you would lose to migrations stays yours.