For developers
No black box, no vendor magic. The whole codebase is public, the API is documented, and the install is one command on your own server. b10cks is close to the CMS you would have built, except it already exists.
Open source under AGPLv3. Every feature on every plan.
The day this fixes
You know the week. The content model drifted from what the frontend expects, the preview URL only half works, and a field rename in the CMS UI quietly broke a build at 2am. Somewhere in there you wrote a sync script you never wanted to own.
b10cks puts the structure where the rest of your code lives. Define block schemas, keep them in Git, ship them through CI. The editor, the canvas, and the API pick up the change together, so there is nothing left to sync by hand.
Structured content / any frontend
// You define the structure.
// You build the experience.
{
"component": "hero",
"heading": "Ship it",
"body": [
{ "component": "feature_grid", "cols": 3 }
]
}What you actually get
Familiar technology, predictable endpoints, and no proprietary query language to learn before you can fetch a page.
Laravel on the backend, Vue 3 with TypeScript in the app. MySQL, MariaDB, or SQLite. If you have shipped a Laravel app, you can extend b10cks.
A stable v1, an OpenAPI spec you can import or generate a client from, cursor pagination, draft and published querying, and rate limit headers you can see.
Define block schemas in TypeScript, version them in Git, deploy through CI. Changes reach the editor, the canvas, and the API without a manual sync step.
Every lifecycle event fires: publish, unpublish, draft save, locale update, schema change. HMAC signatures, delivery logs, and exponential backoff are included.
Local disk, S3, GCS, or anything S3-compatible. MySQL fulltext or OpenSearch, switchable per space with the same API surface either way.
b10cks hands you structured content and stays out of the presentation. Your components, your design system, your deploy pipeline.
Reassurance
Run the same open-source platform on your own infrastructure. AWS, GCP, Azure, DigitalOcean, Hetzner, Fly.io, Kubernetes, or a plain VPS. Add a domain and TLS and you are in production.
Self-hosting buys you data residency, cost control, and no upstream dependency for content delivery. It costs you the operations work. That trade is yours to make, and you can change your mind later.
curl -fsSL https://get.b10cks.com | shOne command to get started.
No compatibility waiting room
b10cks does not render your pages, so it never gates which framework version you run. When your framework ships a new rendering mode or your host adds a feature, you use it the day it lands.
Build the structure once
Start on b10cks Cloud in a minute, or clone the repo and run it yourself. The platform is the same either way.