Astro CMS: choosing the right headless CMS for Astro.
The best Astro CMS depends on who edits your content and how. We compare content collections, git-based CMSs, API-based and self-hosted headless systems, and headless WordPress.
Your editors decide
Your team decides which CMS fits.
No CMS is a valid answer
Astro reads content from the repository type-safely. For developer-maintained sites that is the cheaper option.
Stay switchable
We wrap CMS access in a data layer of its own, so changing vendors hits that layer only.
Our own products, live in the browser.
Screenshots from Mini Marvin, our own progressive web app running in the browser.
Swipe baby names instead of scrolling
Mini Marvin is our progressive web app for finding baby names: swipe through 10,000+ first names right in the browser, no app store needed.
Before you buy a CMS, check whether you need one.
-
Astro does not need a CMS
Content can live in the project as Markdown, MDX, Markdoc, JSON, YAML or TOML and be queried type-safely through content collections.
More on this
A collection is a set of structurally identical entries: all blog posts, all job openings, all locations. If developers or technical writers maintain the content, the pull request is the approval process. It also avoids a subscription, a second login and an API that can go down.
-
Content collections in detail
In src/content.config.ts you declare which fields an entry must have. Zod validates every file, and a missing required field breaks the build.
More on this
Two built-in loaders read the data: glob() for a directory of files, file() for several entries inside one file. Queries run through getCollection() and getEntry(), typed and filtered. Collections arrived in Astro 2.0, and the built-in caching holds up across thousands of entries.
-
Your editors decide the system
A team publishing daily needs something different from a team that changes a page four times a year.
More on this
Once people without Git access publish, once approvals are required, or once several languages run side by side, a system with an editing UI joins in. WordPress may stay in place and serve content only, see WordPress as a headless CMS.
-
Live collections for volatile data
Content collections are read at build time. Where prices, stock or appointments must be correct at the moment of the request, live collections fetch data per request.
More on this
They are configured in src/live.config.ts and queried through getLiveCollection(). That requires a server runtime, meaning a route with prerender = false and an adapter for the target environment. The bulk of the site stays static, see performance optimization.
-
Editing by chat, without a CMS seat
A typed, schema-validated model is machine-addressable. An agent can only fill fields that exist, and every change lands as a traceable commit.
More on this
A faulty edit fails in the build before it reaches the live site. Chat agents are day-to-day work for us, and our own WhatsApp AI agent is the evidence. What chat does not replace: multi-stage approvals and structural layout changes. More on editing your website by chat.
Not sure which CMS fits your team?
Describe in three sentences who maintains content at your company and how often. You get a recommendation with reasoning.
Five ways to get content into an Astro site.
These families differ mainly in who owns the system and who operates it.
| Family | Editing experience | Cost & operations | Fits when … |
|---|---|---|---|
| Content collections no CMS |
Files in the repository, edited by commit or pull request | No licence, development time only | Developers or technical writers maintain the content |
| Git-based CMS Decap, Keystatic, TinaCMS |
Browser editor with real fields, saves back into the repository | Open source, costs for authentication and hosting | One to five editors publish occasionally |
| API-based headless CMS Storyblok, Sanity, Contentful |
Visual editors, draft preview, roles, approvals, localisation | Subscription that grows with seats and traffic | Marketing publishes regularly, with approval stages |
| Self-hosted Strapi, Payload CMS, Directus |
Your own admin UI, modelled freely | No licence fee, plus server, database, updates and backups | The data has to stay in house |
| Headless WordPress | Familiar wp-admin, existing roles stay intact | Hosting as before, plus the Astro front end | Your team knows WordPress and wants to keep it |
How we set up your CMS with Astro.
Map the editorial reality
Who maintains what, how often and with which approval. We talk to the daily users first.
Design the content model
Which content types exist, which fields are required and what stays reusable.
Select a system
Two or three suitable options with their cost picture, plus a recommendation including its counterarguments.
Integrate and encapsulate
Content collections for everything known at build time, live collections where freshness matters.
Preview, roles, handover
We test preview, permissions and the deploy webhook before launch, then hand over with a walkthrough and ongoing maintenance if you want it.
Astro CMS: frequently asked questions.
Does Astro need a CMS?
No. Astro reads content straight from the project through content collections, validates it against a Zod schema and exposes it type-safely via getCollection(). It also needs no server for that: the site is prerendered and served as static HTML. A CMS is added once people without Git access have to publish.
What is the best CMS for Astro?
Your team decides, because technically almost any of them works. Git-based CMSs like Decap, Keystatic or TinaCMS suit small editorial teams close to the repository. API-based systems like Storyblok, Sanity or Contentful suit multiple editors, approvals and languages. Strapi, Payload CMS or Directus suit data that has to stay in house.
Can I use WordPress as a headless CMS with Astro?
Yes. A headless CMS manages content and serves it over an API while another system renders the pages. Your WordPress instance stays in place, your editors keep wp-admin, and Astro builds the front end. The whole move is described on WordPress as a headless CMS.
What are content collections in Astro?
Astro's built-in way to manage structurally identical content: all blog posts, all job openings, all locations. They are defined in src/content.config.ts, their schema is written and validated with Zod, and TypeScript types are derived automatically. They arrived in Astro 2.0 and cost no licence fee, since Astro is MIT-licensed.
Git-based CMS or API-based headless CMS, what is the difference?
A git-based CMS writes every change back into your repository as a commit, so content stays versioned in the project with no second database. An API-based system stores content at the vendor and Astro fetches it over an interface. Git-based is cheaper to operate, API-based brings roles, approvals and localisation.
Does the site rebuild every time content changes?
For build-time content, yes, and usually that is the point: the output is static HTML served without a database query. A webhook from the CMS triggers the build, which takes minutes for a typical marketing site. Where that is too slow, live collections fetch data per request.
Can editors preview drafts before publishing?
Yes, though the route depends on the system. API-based CMSs expose drafts through a dedicated preview token, so we build a server-rendered preview route that pulls exactly that draft. Git-based CMSs use branches and your host's deploy previews. We test this before launch, because adoption depends on it.
How much does an Astro CMS setup cost, and how long does it take?
The range follows from the number of content types and the depth of editorial features such as roles, approvals and languages. The licence cost of the chosen system adds to it. Content collections take one to two weeks, a git-based CMS two to four, an API-based one five to nine. Drivers on Astro development cost.
More on Astro.
The CMS question is one part of the project. Here are the others:
Content your team will maintain.
Tell us how your editorial work runs: who writes, who approves, how often. You get a reasoned CMS recommendation with a cost picture.
Request a CMS setup.
Briefly describe which content gets maintained and by whom. We come back with a recommendation.
We usually reply within 24 hours.
Remote and on site in Germany, Austria and Switzerland. International projects on request.
Related services.
Headless CMS Agency
Content modelling, integration and operations behind the CMS decision.
Learn moreWebflow Agency
When a visual tool with its own CMS and editor fits better.
Learn moreCustom Software Development
When the content model turns into an application with logins.
Learn moreIT Project Management
When the replatforming touches several teams and systems at once.
Learn more