Pricing
Priced by documents, not by editors.
Every plan includes the content lake, the query API, the studio and CDN delivery. What changes is how much content you store, how much of it you serve, and how much of our time you get when something is on fire.
Free
Freeone editor, forever
For a side project, a prototype, or the first honest test of whether this fits.
- One editor and two datasets
- 1,000 documents
- GROQ queries and the HTTP API
- Asset pipeline with CDN delivery
- Community support
Growth
Most popular
$29per editor / month
For a team that publishes every week and wants the workflow enforced by the tool.
- Unlimited editors and datasets
- 50,000 documents
- Draft previews and revision history
- Webhooks with filters and projections
- Roles, invitations and API tokens
- Email support in one business day
Scale
$99per editor / month
For several products on one lake, with the audit trail and the uptime to match.
- Everything in Growth
- Unlimited documents
- Audit log export
- Custom webhook projections and replay
- 99.95% uptime commitment
- Priority support with a two-hour response
Enterprise
Customannual contract
For a content estate that has to live in your own account, under your own rules.
- Everything in Scale
- Single-tenant deployment in your AWS account
- SSO with SAML and SCIM provisioning
- Custom data residency
- A named solutions engineer
- Migration support and a rehearsal cutover
Compare
What is in which plan.
Last changed when a plan changed.
| Included | FreeFree · one editor, forever | Growth$29 · per editor / month | Scale$99 · per editor / month | EnterpriseCustom · annual contract |
|---|---|---|---|---|
| One editor and two datasets | Included | Not included | Not included | Not included |
| 1,000 documents | Included | Not included | Not included | Not included |
| GROQ queries and the HTTP API | Included | Not included | Not included | Not included |
| Asset pipeline with CDN delivery | Included | Not included | Not included | Not included |
| Community support | Included | Not included | Not included | Not included |
| Unlimited editors and datasets | Not included | Included | Not included | Not included |
| 50,000 documents | Not included | Included | Not included | Not included |
| Draft previews and revision history | Not included | Included | Not included | Not included |
| Webhooks with filters and projections | Not included | Included | Not included | Not included |
| Roles, invitations and API tokens | Not included | Included | Not included | Not included |
| Email support in one business day | Not included | Included | Not included | Not included |
| Everything in Growth | Not included | Not included | Included | Not included |
| Unlimited documents | Not included | Not included | Included | Not included |
| Audit log export | Not included | Not included | Included | Not included |
| Custom webhook projections and replay | Not included | Not included | Included | Not included |
| 99.95% uptime commitment | Not included | Not included | Included | Not included |
| Priority support with a two-hour response | Not included | Not included | Included | Not included |
| Everything in Scale | Not included | Not included | Not included | Included |
| Single-tenant deployment in your AWS account | Not included | Not included | Not included | Included |
| SSO with SAML and SCIM provisioning | Not included | Not included | Not included | Included |
| Custom data residency | Not included | Not included | Not included | Included |
| A named solutions engineer | Not included | Not included | Not included | Included |
| Migration support and a rehearsal cutover | Not included | Not included | Not included | Included |
A tick means the plan’s own document lists that line. Everything is editable in the studio, and this table follows.
Pricing questions
Answered before you ask somebody to sign.
Everything below is a document in the dataset this page renders — the question, the answer, and the order they appear in.
- Achar is a content lake with a query language and a studio. You model your content as documents with a schema, author them in the studio, and read them from any surface with one HTTP API. The schema is shared by all three, so the studio draws its form from the same definition your queries run against.
- A page-based CMS stores the page. Achar stores the story and lets each surface decide what a story looks like, which is what makes the second frontend — an app, a partner feed, a support site — a query rather than a second copy of your content.
- You have to read one. Most reads are a filter and a projection, which is a line you can copy from the studio and adjust: the studio runs your query against the dataset as you write it, so the first draft of any query is a thing you can see working before it reaches your code.
- Yes, and the honest answer is that the modelling is the work rather than the transfer. A dataset exports and imports as portable JSON with its schema, and the migration is usually a script that maps fields, run first against a staging dataset and checked with a query before it is run again against production.
- In your own AWS account on the paid plans: DynamoDB for documents, S3 and CloudFront for media, Cognito for sign-in. You can deploy the backend with the CDK app in this repository, which means the content outlives any decision you make about us.
- Nothing stops working and nothing is deleted. The plan limits are checked when a document is written, so the editor is the first thing to tell you, and upgrading keeps every id, revision and reference exactly as they are.
- It drafts into the draft row and stops there. Suggestions are attached to a field with a schema behind it — an excerpt, a translation, a category — and a person accepts or rejects each one. Nothing reaches a published document without somebody pressing publish.
- Create a project, seed a dataset with the sample content in this repository, and query it. The whole path — schema, documents, query, published page — is about ten minutes, and there is a demo app that does nothing but call the API so you can see what a third-party client looks like.
Your content already wants to be structured.
Make a project, define a type, publish a document. The first three things you need are free, and the query you write for them is the same query you will be writing in three years.