Pricing · public beta
Free while the beta runs. Free to run after it, too.
Every feature on this site is in the MIT core, nothing is metered, and no plan unlocks anything. What a plan buys is people: support with a response time in writing, and a licence agreement with your name on it.
Everything is free until the beta ends
Community was always free. While the beta runs the Team and Enterprise plans are too, support included, for the teams running Apograph in earnest and telling us what breaks. Nothing is capped and nothing is metered.
-
Community
Free forever, under MIT
The whole product on your own hardware. Every feature on this site is in it — none of them is paid-only.
Unlimited members · workspaces · segments · API tokens · installations
- Every feature on this site, none of them held back
- No limit on anything while the beta runs
- REST, GraphQL, MCP and webhooks, from the same tokens
- Single sign-on through OpenID Connect, GitHub or SAML
- The AI assistant, against your own model key
- Version history on every save, and the full activity log
- Community support on GitHub
-
Most teams choose this
Team
Free during the beta, then $99 per month
The same product, with somebody to call. For a team that wants a response time in writing and a say in what gets built.
Unlimited members and installations during the beta
- Everything in Community — it is the same software
- Email support, answered within two working days
- Upgrade guidance before each release that changes configuration
- A licence agreement with your organisation named on it
- A say in what gets built next
-
Enterprise
Free during the beta, then priced against your size
For an organisation whose security review starts before the evaluation does.
Unlimited everything · a conversation, not a checkout
- Everything in Team
- Four-hour response, on a channel with names in it
- A security review answered by the people who wrote the code
- Air-gapped deployment, with no call home — it never had one
- Migration from your current CMS, done with you
Who gets what, line by line
| Capability | Community | Team | Enterprise |
|---|---|---|---|
| The product Identical in all three. Every one of these is in the MIT core, and no plan unlocks any of them. | |||
| Members and roles | Included | Included | Included |
| Content model | Included | Included | Included |
| Content library | Included | Included | Included |
| Writing and rich text | Included | Included | Included |
| Languages and translation | Included | Included | Included |
| Publishing | Included | Included | Included |
| Publication protection and review | Included | Included | Included |
| Version history | Included | Included | Included |
| Media library | Included | Included | Included |
| Delivery API — REST and GraphQL | Included | Included | Included |
| Webhooks | Included | Included | Included |
| Agents and MCP | Included | Included | Included |
| Content alarms | Included | Included | Included |
| Apograph AI | Included | Included | Included |
| Content export and import | Included | Included | Included |
| Records, API calls and bandwidth | Unlimited | Unlimited | Unlimited |
| Air-gapped deployment | Included | Included | Included |
| Limits None while the beta runs. The other tab shows where they will sit. | |||
| Workspaces | Unlimited | Unlimited | Unlimited |
| Segments | Unlimited | Unlimited | Unlimited |
| API tokens | Unlimited | Unlimited | Unlimited |
| Activity log history | Full | Full | Full |
| Members covered by the licence | Unlimited | Unlimited | Unlimited |
| Production installations | Unlimited | Unlimited | Unlimited |
| Development and staging | Unlimited | Unlimited | Unlimited |
| Sign-on Every adapter is installed by every plan during the beta. | |||
| Single sign-on (OIDC, GitHub) | Included | Included | Included |
| SAML 2.0 and enforced sign-on | Included | Included | Included |
| People, and paper The only thing a plan changes during the beta. None of it is software. | |||
| Support | GitHub issues | Email, 2 working days | 4-hour response, shared channel |
| Upgrade guidance | The changelog and the docs | Before each release | Planned with you |
| Security review | The source, and the docs | Written answers | Answered by the engineers |
| Licence agreement | MIT | MIT, plus an agreement naming you | Negotiated terms |
| Migration from another CMS | Not included | Not included | Done with you |
Nothing on this tab expires. Beta users hear the end date well in advance, and nothing you already run will ever be charged for or taken away: the beta ends, the software stays. The other tab is what the same plans will cost afterwards.
Free to run. Paid for room, plug-ins and support.
The same product on every plan. Community caps four things — workspaces, segments, API tokens, and how far back the activity log reads — and a plan lifts them, adds single sign-on and activity export, and puts a response time in writing.
-
Community
Free forever, under MIT
The whole product on your own hardware. Every feature on this site is in it — none of them is paid-only.
Unlimited members · 3 workspaces · 3 segments · 2 API tokens
- Every feature on this site, none of them held back
- No limit on members, records, API calls or bandwidth
- REST, GraphQL, MCP and webhooks, from the same tokens
- The AI assistant, against your own model key
- Version history on every save, and 30 days of activity log
- Content export and import, in four formats
- Community support on GitHub
-
Most teams choose this
Team
$99 per month, billed yearly at $79
Room to grow, and the governance a team needs once it has to answer to somebody about who did what.
10 members included, then $3 each · 1 production installation, then $29 each
- Everything in Community, with its four limits lifted
- Unlimited workspaces, segments and API tokens
- Activity log history that does not stop at thirty days
- Single sign-on through OpenID Connect or GitHub
- Activity log export, to keep it outside the database
- Unlimited development and staging installations
- Email support, answered within two working days
-
Enterprise
On request priced against your size and your terms
For an organisation whose security review starts before the evaluation does.
Unlimited members · unlimited production installations
- Everything in Team
- SAML 2.0, and single sign-on you can enforce
- Activity log export straight into your own SIEM
- Air-gapped deployment, with no call home
- Four-hour response, on a channel with names in it
- Migration from your current CMS, done with you
Who gets what, line by line
| Capability | Community | Team | Enterprise |
|---|---|---|---|
| The product Identical in all three. Every one of these is in the MIT core, and no plan unlocks any of them. | |||
| Members and roles | Included | Included | Included |
| Content model | Included | Included | Included |
| Content library | Included | Included | Included |
| Writing and rich text | Included | Included | Included |
| Languages and translation | Included | Included | Included |
| Publishing | Included | Included | Included |
| Publication protection and review | Included | Included | Included |
| Version history | Included | Included | Included |
| Media library | Included | Included | Included |
| Delivery API — REST and GraphQL | Included | Included | Included |
| Webhooks | Included | Included | Included |
| Agents and MCP | Included | Included | Included |
| Content alarms | Included | Included | Included |
| Apograph AI | Included | Included | Included |
| Content export and import | Included | Included | Included |
| Records, API calls and bandwidth | Unlimited | Unlimited | Unlimited |
| Air-gapped deployment | Included | Included | Included |
| Limits Four caps on Community, lifted by a plan. Contract terms rather than locks — the core is MIT, and we would rather you heard that from us. | |||
| Workspaces | 3 | Unlimited | Unlimited |
| Segments | 3 | Unlimited | Unlimited |
| API tokens | 2 | Unlimited | Unlimited |
| Activity log history | 30 days | Full | Full |
| Members covered by the licence | n/a | 10, then $3 each | Unlimited |
| Production installations | n/a | 1, then $29 each | Unlimited |
| Development and staging | Unlimited | Unlimited | Unlimited |
| Plug-ins What the core will not carry: sign-on adapters, and a way to get the activity log out. | |||
| Single sign-on (OIDC, GitHub) | Not included | Included | Included |
| SAML 2.0 and enforced sign-on | Not included | Not included | Included |
| Activity log export | Not included | File | File and SIEM |
| People, and paper What you get from us rather than from the software. | |||
| Support | GitHub issues | Email, 2 working days | 4-hour response, shared channel |
| Upgrade guidance | The changelog and the docs | Before each release | Planned with you |
| Security review | The source, and the docs | Written answers | Answered by the engineers |
| Licence agreement | MIT | MIT, plus an agreement naming you | Negotiated terms |
| Migration from another CMS | Not included | Not included | Done with you |
Planned terms, published early so nobody meets them for the first time on an invoice. The code enforces none of them during the beta, and nothing here is final until the 1.0 changelog says so. Whatever changes, the two rules hold: no feature is paid-only, and the caps are contract terms rather than locks.
What a plan never changes
Open source is the product, not a trial of it
-
Every feature is in the core
Nothing on this site is paid-only. Translation, version history, the media library, the activity log, publication protection, the delivery API, webhooks, MCP and Apograph AI are all MIT. A plan raises a limit or adds a plug-in — it never unlocks a capability Community already has.
-
Free means production, not a demo
No time limit, no watermark, and no cap on members, records, API calls or bandwidth, on any plan. After 1.0, three workspaces and three segments carry a real site with a real team behind it; during the beta not even those are counted.
-
We do not host it
There is no cloud edition and none is planned. If a hosted CMS is what you want, choose one — we would rather say so now than at the end of an evaluation.
Before you decide
Questions about the money
Answered plainly, including the one about whether this page will look different in a year.
Is everything really free during the beta?
Yes. Community is free forever regardless, and for as long as the beta runs the Team and Enterprise plans cost nothing either, support included. There is nothing to sign up for and nothing to pay. When the beta ends you will hear the date well in advance, and nothing you already have will be taken away or charged for.
Can we run Apograph for free, in production, forever?
Yes. Community has no time limit and no cap on members, records, API calls or bandwidth, and every feature on this site is in it. After 1.0 four things are capped — workspaces, segments, API tokens, and how far back the activity log reads — and plenty of teams never reach any of them. During the beta nothing is capped at all.
What exactly am I paying for?
Two things. Room: unlimited workspaces, segments and API tokens, and activity log history that does not stop at thirty days. And what the core does not carry: single sign-on, activity log export, support with a response time in writing, and a licence agreement with your organisation named on it. The software is the same on every plan.
Why cap workspaces and segments at all?
Because they are the two things that track what a company is actually doing with the product. One site with one segment is a team trying it; twelve workspaces or a dozen customer segments is an agency or a business gating content per client, and that is the point at which paying for it is reasonable. We would rather meter something honest like that than meter your API calls, your records or your bandwidth — those are free, and staying free.
What counts as a production installation?
One deployment serving real readers or real editors. Development, staging, preview and CI installations are unlimited on every plan, including the paid ones, and always will be — charging for a staging environment is how a tool teaches people to test in production.
How are the limits enforced?
As terms of the licence agreement, not as locks in the code. Nothing calls home, because a deployment that phones out is not one a bank or a hospital can run, and those are the deployments that buy Enterprise. The core is MIT, so every cap is a contract term with an honest signal, and we would rather you knew that from us. During the beta there are no limits to enforce.
Do we pay for the AI assistant?
No, on any plan including Community. It talks to whichever model you configure — Claude, an OpenAI-compatible endpoint, or something on your own hardware through Ollama or vLLM. You pay that provider, or nobody, and never us.
When can we buy a plan?
Not before the beta ends. Billing is not open, there is nothing to sign and nothing to pay, and every plan is free in the meantime. You will hear the end date well before anything changes.
You can have all of it for nothing, today
Clone it, point it at a Postgres, and run the whole product with no key and no account. Come back to this page when somebody asks you who they can call.