A headless CMS for agencies, one org per client
Run every client site from one login. Each client gets their own org, their own content, and their own invoice. Their staff can be scoped to production while your team works in staging. When the engagement ends, the account keeps running without you.
One org per client
Your account can belong to any number of orgs, and the dashboard switches between them. Templates, entries, media, and API keys never cross an org boundary.
The client holds the card
Invite their finance contact as billing. That role reaches the subscription and nothing else, so they can change plans without seeing a template.
Staging you keep, production they see
Scope a client's members to a single environment. Your team works in staging, syncs when it's ready, and the client's staff never sees the mess in between.
Five roles, not two
Owner, admin, editor, billing, viewer. A client reviewer gets viewer, their writer gets editor, and your developers keep admin.
How does an agency manage multiple clients in one CMS?
One org per client. That's the whole model. A Draftbase user account isn't tied to a single org, so the same login covers a portfolio of twelve client sites, and switching between them is a dropdown rather than a second password manager entry.
Everything scopes to the org: templates, entries, media, webhooks, API keys, members. Nothing is shared across the boundary, which means there's no configuration mistake that shows one client's drafts to another. It also means each org carries its own plan and its own usage limits, counted separately.
The alternative pattern, one org with an environment per client, looks cheaper. Don't. Environments cap at 5 on the Scale plan, members are counted org-wide, and a client's billing contact would sit inside an org holding every other client's content.
Who pays, and who keeps the keys
The awkward part of client work is usually billing. An agency that puts ten client subscriptions on its own card is running a collections business it didn't ask for. Draftbase splits that apart with a dedicated billing role.
| Role | Typically | Reaches |
|---|---|---|
| Owner | Whoever created the org | Everything, and can't be removed or demoted |
| Admin | Your developers | Templates, environments, API keys, members, billing |
| Billing | The client's finance contact | Subscription and invoices only |
| Editor | The client's content team | Entries and media, no schema changes |
| Viewer | Client-side reviewers and stakeholders | Read-only |
One decision to make on day one: who creates the org. Ownership can't be reassigned later, and the API returns OWNER_IMMUTABLE if you try. If the client should still own the account two years after your last invoice, have them sign up and invite you as admin. You'll have the same working access either way.
Can a client's staff be kept out of staging?
Yes, and it's one field on the membership. Scope a member to a single environment and that's the only one they load. Leave the scope off and they see all of them.
The practical shape: your team holds admin across staging and production, the client's writers are editors scoped to production, and the redesign nobody has approved yet stays in staging where it belongs. Content moves between environments with a sync, not a copy-paste session.
Environment counts come from the plan, so check the math before promising a client a three-stage workflow. Hobby has 1. Startup has 2. Growth has 3, Scale has 5, and Enterprise is uncapped. Prices are on the pricing page, where prices go.
Headless WordPress per client, or one CMS across the roster?
Most agencies doing headless work today are running WordPress behind WPGraphQL, one install per client. It works. The cost shows up in the parts nobody quotes for: plugin updates across twelve installs, a PHP upgrade that breaks two of them, and a rich text field that arrives as an HTML string your React app has to trust.
| Per-client concern | Headless WordPress install | Draftbase org |
|---|---|---|
| Hosting and patching | Yours, per install, forever | Hosted |
| Rich text in React | HTML string, sanitized and parsed by you | MDX rendered by <MDXContent> |
| Client billing | Host invoice, usually yours to rebill | Client's own card, billing role |
| Staging | A second install and a sync plugin | An environment, synced from the dashboard |
WordPress still wins on two things worth admitting. The plugin ecosystem has an answer for every client request, and the editor is one your client's marketing hire already knows. If the brief is a brochure site for a non-technical team, that familiarity is worth more than any renderer. Draftbase earns its place when the frontend is React and the content has to arrive as components. The React CMS page covers how that rendering path works.
What we haven't built yet
No agency tier, no reseller discount, no commission. Every org pays the public price. There's no single dashboard showing usage across all your client orgs either, so checking twelve of them means switching twelve times.
We'd rather say that plainly than sell a partner program that doesn't exist. If you run client sites and any of the gaps above would block you, tell us which one. That's what decides what gets built.
Tell us about your client work
How many client sites, what they're built on, and what would have to be true for Draftbase to hold them. A real reply from someone who knows the product, not a discovery call.
Or skip the conversation. Hobby is free with no card, so you can model a client's content and see how it renders this afternoon.
Frequently asked questions
Is there an agency or partner plan?
Not yet. Every org runs on the same public plans: Hobby free, Startup $49/mo, Growth $299/mo, Scale $499/mo, Enterprise custom. An agency running six client orgs pays six subscriptions, usually on six different cards, since each client can own their own billing. If you want a partner arrangement, email us and say how many client sites you run.
How does an agency manage multiple clients in one account?
One org per client, and one login across all of them. Your user account can belong to as many orgs as you like, and the dashboard switches between them. Content, media, templates, API keys, and members are scoped to a single org, so nothing leaks between two clients by accident.
Can the client pay their own bill?
Yes. Draftbase has a dedicated billing role, separate from admin. Invite the client's finance contact as billing, and they can see and manage the subscription without touching templates or entries. The card belongs to the client, and the org keeps running when your engagement ends.
Can I limit a client's staff to one environment?
Yes. A membership can be scoped to a single environment, so a client's marketing hire only ever sees production while your team works in staging. Leave the scope off and the member sees every environment in the org. Environment counts come from the plan: 1 on Hobby, 2 on Startup, 3 on Growth, 5 on Scale.
Can I hand the org over to the client at the end of a project?
Not automatically. Org ownership can't be reassigned in the dashboard today, and the API rejects it with an OWNER_IMMUTABLE error. So decide up front: if the client should own the account long term, have them create the org and invite you as admin. You get the same access either way, and they keep the keys.
Do you support headless WordPress migrations?
Not as a service, and there's no importer yet. Draftbase is a product, not a development shop. Teams moving a client off WordPress typically script the export against the management API and the SDK's typed client. If you want the migration done for you, hire an agency and point them here.