For agencies
One b10cks instance, an isolated space per client, and pricing based on storage and traffic instead of seats. No per-client licence maths, no call with sales before a client can have localization.
Open source under AGPLv3. Unlimited editors in every space.
The day this fixes
A client asks for a second language. You check the plan. It is a tier up, and the tier is priced per seat, and now you are the one explaining a price increase you did not cause. Multiply that by every client in the portfolio.
b10cks removes the conversation. Every feature is available in every space from day one, and you pay for storage and traffic. What the client asks for on Monday, they can have on Monday.
The model
You pay for what the sites actually use. Clients get the whole feature set on day one, and you never price a project around a licence tier.
AGPLv3
Unlimited
One per client
Storage + traffic
Your infrastructure and hosting costs apply when you self-host. Move between Cloud and self-hosted with a configuration change.
How it works in practice
The parts of b10cks that matter when you are running fifteen client projects at once and half of them are in review.
Each client gets their own space: their content model, their team, their locales, their assets. Client A cannot see Client B, and permissions are per space.
Walk the client through the structure on the infinite canvas instead of a JSON schema. Reuse block libraries across spaces so you are not rebuilding the same hero every quarter.
Give stakeholders view or comment access. They annotate the actual page, you see their cursor during the call, and the feedback stops living in email.
Role-based access keeps client editors inside the guardrails. Visual editing means routine changes never come back to you. Full export means they own their data.
Run your largest clients on your own infrastructure and put the smaller ones on b10cks Cloud. Same platform, same features, one configuration change to move.
Open source means no per-instance licence. Usage pricing means no paying for capacity you did not use. Across a portfolio that difference compounds.
Reassurance
A good handover is the one where the client could leave and chooses not to. b10cks is open source, so the platform cannot be discontinued out from under a project you built. Content exports as structured JSON, assets included, whenever they ask.
That honesty is easier to sell than a lock-in you have to defend three years later.
Where b10cks is not the answer
If a client needs a site with no structured content at all, a page builder will be quicker. b10cks earns its place when the content outlives the layout and more than one person has to touch it.
Build the next one faster
Set up your first client space, reuse it as the template for the next, and keep the economics on your side.