The whole 23blocks platform — the code now open source — packaged to run on your own cloud. We deploy and maintain it for you, or you run it yourself with our recipes. Start big from day zero, or graduate from the shared platform when you outgrow it.
Every option runs the same open-source blocks. What changes is who deploys and who operates.
We host it · multi-tenant
Use 23blocks as a service. Zero infrastructure to run, every block on day one, pay-as-you-grow. The fastest way to launch.
We operate it · your infra
We deploy the platform into your own cloud and run it for you — updates, monitoring, and support tiers included. Ownership without the operational burden.
Purchase our deployment recipes — the production-grade infrastructure definitions and playbooks — and run the open-source blocks on your own.
Both options are "23blocks in a Box" — the same platform on your infrastructure, run by us or by you.
The code is free and open. The value is getting it deployed and kept running — well.
The blocks are open source — the code is yours, free. Read it, extend it, and take updates on your own schedule. No licenses, no lock-in.
The production-grade infrastructure definitions and playbooks that stand the platform up properly — the same ones we use. Run them yourself, or let us run them for you.
Want us to run it? We deploy a single-tenant copy in your account and maintain it — updates, monitoring, and support — on the same architecture that runs 23blocks.
Moving off the shared platform? A proven, rehearsed process migrates your data with parity checks and rollback armed the whole way — cut over in a single maintenance window.
Whether you already know you need your own infrastructure or you're growing into it, there's a path.
You already know you need your own infrastructure — for scale, compliance, data residency, or because you run your own application alongside the blocks. Deploy 23blocks-in-a-Box directly and start on infrastructure you own from the first commit.
You started on the shared platform to move fast, and you outgrew it — that's a good problem. Keep the exact same platform and move it onto infrastructure you own, with a reversible migration and no code rewrite.
If any of these describe you — today or on the horizon — running on your own infrastructure is the right call.
Your traffic and data warrant infrastructure sized and tuned for you alone — not a fair share of a shared cluster.
You want to own deploys, scaling decisions, maintenance windows, and incident response — not wait on a shared roadmap.
You need your data in your own account, region, or under your own compliance controls.
At your scale, dedicated infrastructure is cheaper and more forecastable than shared per-usage pricing.
You run your own application alongside the blocks — your own API, custom domains, bespoke infra — and want it all in one account.
The model can be hybrid. Keep select blocks on the shared platform while the rest run on your own infrastructure — a supported, deliberate choice.
Six phases take you onto infrastructure you own. Graduating from shared adds the data migration — in one reversible maintenance window.
Each block is open source and forked into your own org. The code becomes yours to run and update.
Your own pipeline builds the images and publishes them to your own registry. Your build, your artifacts.
The recipes stand up a dedicated, single-tenant copy of the platform in your account — the same architecture that runs 23blocks.
Graduating from shared? Your data is copied — tenant-isolated — into your own database, and verified table by table. Skipped when starting fresh.
Each app points at your own hosts — a URL change, nothing else. The same API key already works on both.
We prove the product works end-to-end on your infrastructure — and, when graduating, that zero traffic is left on the shared platform.
When you graduate from shared, auth, the full read path, and one real write are all checked behind the maintenance page before anyone is let back in — so any issue is caught with zero user exposure. If needed, rollback is simply flipping the URLs back: instant, no rebuild, with shared data never touched during the window.
A casting and talent production platform ran eleven blocks on the shared platform as a single tenant, spanning four consumer surfaces — a talent app, an admin console, a public website, and their own API that consumes the blocks. As they scaled, they moved to 23blocks-in-a-Box on infrastructure they own.
They now run the identical 23blocks platform entirely on their own cloud account, on open-source code they own, with their data migrated and parity-verified, and all four consumer surfaces cut over. Verified result: zero traffic left on the shared platform. Rollback stayed armed on every surface throughout.
Total user-facing disruption: a single maintenance window — with the one real issue of the night caught and fixed behind the maintenance page, zero exposure to real users.
Every In a Box engagement is scoped to your footprint. Here's what comes with it.
The code, forked into your org — yours to keep and update.
Production-grade infrastructure definitions and playbooks.
A single-tenant copy stood up on infrastructure you own.
When graduating — your data moved and verified table by table.
Optional — we operate it for you, with support & SLA tiers.
Your team owning the platform from day one, with the engineering playbook.
Every engagement is scoped to your footprint. Need a staging environment? Because In a Box runs in your own account, a full staging copy is available as an advanced add-on — run by us or by your team. Talk to us for a tailored proposal.
Same product, your infrastructure. We deploy and maintain it, or you run our recipes — reversible, either way.
Get product updates, engineering posts, and new block announcements delivered to your inbox.