b10cks vs. WordPress
Headless WordPress is a patch on an architecture that predates the idea. A retrofitted REST API, an editor that stops working, and a plugin bill you only see later. b10cks was an API from the first line.
Every feature. Unlimited editors. From €0 / month.
Credit where it is due
WordPress runs 43% of the web, and that reach is earned. The community is the largest in CMS history, the ecosystem answers almost every question you have, and for a site where the theme renders the pages it is still a pragmatic, battle-tested choice. If WooCommerce is your store and your storefront, nothing here beats it.
Where it costs you
Headless WordPress works. It just gives back less than the WordPress you know, and the missing pieces are the ones editors touch every day.
Gutenberg renders blocks inside WordPress themes. Decoupled, it becomes a rich text field that emits HTML you have to parse. Click-to-edit and live preview go with it.
Plugins built on hooks, shortcodes, PHP rendering or WooCommerce do not travel. The ecosystem you chose WordPress for shrinks to the part that speaks JSON.
The built-in preview opens a WordPress-rendered page. Wiring preview to your actual Next.js or Nuxt frontend is development work, not a toggle.
The native model is Posts, Pages and Custom Post Types. Nested, composable blocks need ACF, a third-party plugin with its own licence.
Localization means WPML or Polylang, both paid, both with their own quirks. Field-level translation and inheritance are not part of the deal.
Studies suggest 35% of headless WordPress migrations end up slower than the site they replaced, usually through over-fetching, hydration choices and request waterfalls.
Not an argument against headless
None of this is a reason to avoid headless. It is a reason to ask whether WordPress is the right backend for it. If your theme renders your site, stay where you are, you are getting the best of it.
Native, not retrofitted
Visual editing in your own frontend, structured blocks, localization, version history with rollback, staging, CDN and image processing. b10cks ships all of it on every plan. WordPress can match most of the list, one plugin at a time.
What it actually costs
WordPress core is free under the GPL. The stack around it is not. Hosting runs $100 to $2,000 a year, ACF Pro $149 to $249, WPML $99 to $199, a security plugin $99 to $500. A lean headless setup lands between $500 and $1,000 a year before anyone writes code, and that is without staging or editorial tooling.
On WordPress.com, plugins start at Business, $25 a month, and the headless story stays limited even there.
Start free. Build from here.
€0/ month to start
Who should pick which
WordPress is the right answer when the theme renders your frontend and no decoupling is planned. When your team is deep in the ecosystem and the plugin workflow is a feature, not a liability. When WooCommerce runs the store and the storefront together. And when you are migrating an old site step by step and a full replacement is off the table.
Pick b10cks when
You are building with Next.js, Nuxt, Astro or anything else that fetches JSON. You want visual editing that works in that frontend, structured blocks without ACF, and locales without a yearly plugin licence. You want a smaller security surface and a bill you can predict.
AGPLv3
Unlimited
Unlimited
None
Self-hosting is one command under AGPLv3. Move between Cloud and your own server with a content export at any time.
Make room for your next build
Start on the free plan, model your content in blocks, and connect the framework you already use.