Astro CMS: which headless CMS ships a real Astro integration
Astro can read from any CMS with an API, so the question is how much glue you write. Of the 36 platforms here, 8 ship an official Astro loader or integration and 29 have a page in Astro's own CMS guides. A Git-based Astro CMS skips the API entirely: it edits the Markdown files Astro already reads.
Reviewed by Eugene SuslovFacts read November 2026No affiliate links

- 36
- platforms that work with Astro
- 8
- ship an official Astro loader or integration
- 29
- have a guide in Astro's docs
- 7
- edit Markdown in your repository
Three ways content reaches an Astro site
- A loader at build time. Astro's Content Layer pulls entries into a typed content collection when the site builds. Fast pages, and a rebuild for every publish, usually triggered by a webhook.
- A fetch at request time. With server rendering, a page calls the CMS on each request, so edits show at once. Any API works; you write the client and handle caching.
- Files in the repository. A Git-based CMS commits Markdown that Astro reads with its built-in loader. No API and no SDK, and every edit is a commit and a rebuild.
An astro headless cms with an official loader turns the first route into a few lines of config and gives you typed entries. Without one, the second route is always open: the CMS's own JavaScript client inside an Astro page.
Every Astro CMS we review
36 platforms whose docs, packages or Astro's own guides cover Astro. Each card links to a full review with pricing, hosting and limits.
Showing 8 of 36 platforms

Payload
FeaturedBest for Next.js teams who want to own the database
A MIT-licensed CMS that installs into your Next.js app rather than sitting beside it. Config is TypeScript, the admin panel is generated from it, and the database is yours.
- Runs inside your Next.js app, same repo and same deploy
- Postgres, MongoDB or SQLite, your instance
- Admin UI generated from a TypeScript config
- Next.js
- React
- Vue / Nuxt
- TypeScript / Next.js

Best for structured content at scale
The structured-content platform behind a large share of serious Next.js marketing sites. You build the editing Studio as React code in your own repository; Sanity hosts the content and serves it over GROQ.
- GROQ query language, plus a GraphQL API you deploy per dataset
- Studio is React code in your repo, not a hosted form builder
- Image CDN with on-the-fly transforms and hotspot cropping
- Next.js
- React
- Vue / Nuxt
- TypeScript / React (Studio)

Best for enterprise governance
The enterprise default, and a Salesforce company since September 2026. Mature APIs, serious governance and localisation, EU data residency, and a pricing model that jumps from free to $300 a month with nothing in between.
- Content Delivery, Preview, Management and GraphQL APIs
- Environments and environment aliases for safe schema changes
- Deep localisation and role-based governance
- Next.js
- React
- Vue / Nuxt
- Hosted SaaS

Best visual editing
The visual editor everyone else copies, wrapped around a component-based content model. Metered on seats, traffic, API calls, locales and AI credits, with a published 97% uptime figure on the self-serve tiers.
- Real visual editing against your own live front end
- Content Delivery and Management APIs, plus GraphQL on Premium and Elite
- Image Service with on-the-fly transformation
- Next.js
- React
- Vue / Nuxt
- Hosted SaaS

Best known open source option
The best-known open-source headless CMS, self-hostable and Node-based. The MIT grant is narrower than everyone assumes: having a Strapi Cloud account is one of the things that voids it.
- Self-hostable Node.js CMS with an admin panel non-developers can use
- Auto-generated REST and GraphQL APIs from your content types
- Role-based permissions and a plugin ecosystem
- Next.js
- React
- Vue / Nuxt
- JavaScript / Node.js

Best for an existing SQL database
Wraps any existing SQL database in a REST and GraphQL API plus an admin app. Not open source, but free and fully permissive for organisations under $5m revenue and 50 staff.
- Points at an existing SQL database rather than owning one
- REST, GraphQL and realtime APIs generated from your schema
- Flows for automation, and a vendor MCP server
- Next.js
- React
- Vue / Nuxt
- TypeScript / Node.js

Best for publishing and newsletters
A publishing platform with memberships and newsletters built in, MIT licensed and genuinely self-hostable. Excellent at articles, deliberately narrow at everything else.
- Content API and Admin API over a real publishing model
- Memberships, paid subscriptions and email newsletters in core
- MIT licensed, self-host with no vendor limits
- Next.js
- React
- Vue / Nuxt
- JavaScript / Node.js

Best pay-for-what-you-use pricing
A GraphQL-first hosted CMS with an imgix-backed asset pipeline and the most granular pricing here. Ten separate meters, each with a published add-on rate.
- GraphQL Content Delivery API with responsive image variants
- Real-time Updates API for live edit overlays
- Asset API backed by imgix transformations
- Next.js
- React
- Vue / Nuxt
- Hosted SaaS

Best for content federation
GraphQL-native from the start, and the only platform here treating content federation as a first-class feature. Growth is $199/mo and caps you at 10,000 entries.
- GraphQL-first content API with a visual Schema Builder
- Content federation: stitch remote sources into one API
- Components, live preview and assignment workflows
- Next.js
- React
- Vue / Nuxt
- Hosted SaaS

Cheapest realistic paid entry
Slice-based page building with a realistic paid entry at $10 a month. Priced per repository and metered on locales, which is the axis that has caught customers out before.
- Slices: reusable page sections editors compose themselves
- Visual Page Builder with unlimited documents on every tier
- 4 million API calls a month even on the free plan
- Next.js
- React
- Vue / Nuxt
- Hosted SaaS

Best for marketer-built landing pages
A visual CMS that has become an AI development platform. Metered in Agent Credits and priced per user, with the drag-and-drop page building still underneath.
- Visual drag-and-drop editing against your own components
- Agent Credits as the primary meter, not documents or calls
- Built-in MCP servers on Pro, custom ones on Team
- Next.js
- React
- Vue / Nuxt
- Hosted SaaS

Best for Laravel teams
A Laravel-native CMS with a perpetual $349-per-site licence rather than a subscription. Headless mode, the REST API and GraphQL are all Pro features, so the free edition cannot be used headlessly.
- Built on Laravel, flat-file or database content
- Blueprints and 40+ fieldtypes for content modelling
- REST and GraphQL APIs, on the Pro licence only
- REST API
- GraphQL API
- Vue / Nuxt
- PHP / Laravel
Best git-backed visual editing
Visual editing on top of Markdown and JSON in your own Git repository, Apache-2.0 licensed. The content stays in your repo whether or not you keep paying.
- Content lives as Markdown or JSON in your Git repo
- Visual editing against your live front end
- Apache-2.0, with a self-hostable backend
- Next.js
- React
- Astro
- TypeScript / Node.js

Best for content and customer data on one contract
A hosted headless CMS sold inside an agentic experience platform with a CDP and AI agents attached. Free, Build and Growth are now priced in public; the uptime SLA and custom data residency stay on quoted Enterprise.
- Delivery, GraphQL and Management APIs in 7 cloud regions
- Visual Editor, Timeline preview, branches and workflows
- Lytics CDP, personalisation and Agent OS on one contract
- Next.js
- React
- Vue / Nuxt
- Hosted SaaS (AWS, Azure or Google Cloud)

Free git-based editing
A free, MIT-licensed admin panel that commits Markdown to your Git repository. Abandoned as Netlify CMS, handed to new maintainers, and shipping releases again.
- Content committed as Markdown to your own Git repo
- MIT licensed; paid hosted backend (Decap Turbo) optional
- A single-page admin app you host yourself
- React
- Next.js
- Vue / Nuxt
- JavaScript / React

Best for governed, multi-brand content operations
Formerly Kentico Kontent, a hosted headless CMS built around editorial workflow, governance and compliance. Its pricing calculator returns a volume discount rather than a price, and every plan is quoted.
- Delivery REST, GraphQL, Sync and Management APIs
- Workflows, spaces, collections and Mission Control
- Data centres in the US, Netherlands, Australia and Canada
- Next.js
- React
- Vue / Nuxt
- Hosted SaaS (Microsoft Azure regions)

Code-first GraphQL backend
A code-first headless CMS and GraphQL backend. You define the schema in TypeScript and get a Prisma-backed database, a typed GraphQL API and an admin UI generated from it.
- Schema defined in TypeScript, admin UI generated from it
- Typed GraphQL API with fine-grained access control
- Prisma under the hood, Postgres, MySQL or SQLite
- React
- Next.js
- Astro
- TypeScript / Node.js

Familiar editor, existing content
GPL software your client already knows how to use, with a REST API in core and GraphQL via a plugin. Nobody can reprice it, and nobody is maintaining it for you either.
- REST API in core since 4.7, GraphQL via WPGraphQL
- GPLv2 or later, so no vendor can change the terms
- An editor most clients have already been trained on
- Next.js
- React
- Vue / Nuxt
- PHP

Best for structured PHP sites
A PHP CMS whose GraphQL API ships in the free edition, so headless Craft is priced by logins rather than traffic. Own a one-off licence or rent it inside Craft Cloud, while Craft 6 moves onto Laravel.
- GraphQL API in every edition, including free Solo
- Paid editions priced by logins: $279 or $399 once
- Craft Cloud bundles the licence into hosting
- Next.js
- React
- Vue / Nuxt
- PHP / Yii 2 (Craft 5); Laravel in Craft 6

Free to start
A straightforward hosted CMS with a clean REST API, a hosted MCP server, AI content tooling and pricing that starts at $49. Deliberately simple rather than deep.
- REST API and hosted MCP server, with good SDKs
- AI content generation included on every tier
- Free tier with 1,000 objects and 2 members
- Next.js
- React
- Vue / Nuxt
- Hosted SaaS
Best for adding a blog to an existing app
A hosted pages-and-blog CMS owned by Tiugo Technologies since 2022. Unlimited users on every plan and pricing by content counts, but the Write API and webhooks are add-ons from Advanced and locales start on Professional.
- Page Types, Collections, Components and a fixed-schema blog engine
- Unlimited users on every plan, metered on calls and content counts
- Write API and webhooks sold as add-ons from the Advanced plan
- Next.js
- React
- Vue / Nuxt
- Hosted SaaS (Heroku and AWS)

Free to start
A fast GraphQL CMS built for agencies, with multi-project management and a genuinely generous free tier at 5,000 entries and a million API calls.
- GraphQL API with a fast query layer
- Blueprint-based content modelling
- Free tier with 3 users and 5,000 entries
- Next.js
- React
- Vue / Nuxt
- Hosted SaaS

Free to start
A headless CMS with product information management and ecommerce in the same GraphQL API. Built for catalogue-driven commerce rather than general content.
- PIM, CMS and ecommerce in one GraphQL API
- Product catalogue modelling as a first-class concept
- Free tier with 100 items and 25 orders a month
- Next.js
- React
- Vue / Nuxt
- Hosted SaaS

Proprietary
A page-management-first headless CMS with unlimited content models, API requests and locales on every plan. Aimed at marketing teams that want sitemap-aware page structures.
- Page management and sitemap structure, not just content
- Unlimited content models, API requests and locales
- Digital asset management included
- Next.js
- React
- Vue / Nuxt
- Hosted SaaS

Best for portfolios of static sites
A git-based visual editor and static host billed per organisation, not per site. In-place editing needs CloudCannon to run the build, and there is no content delivery API.
- Visual editing on the built page via Editable Regions
- Hosting, builds, forms and CDN on every plan
- Unlimited sites; users are the meter at $10/mo
- Astro
- Svelte / SvelteKit
- React
- Hosted SaaS over Git

Best for governed multi-site estates
A Java CMS that serves headless APIs and visual page editing from one multi-site instance. Source-available under BSL 1.1, and free in production only while the largest of your revenue, budget or funding stays at or below $5m.
- Universal Visual Editor for headless front ends
- REST, GraphQL and a Page API from one instance
- Free at or under $5m Total Finances, all features
- Next.js
- React
- Vue / Nuxt
- Java / Tomcat

Open source, self-hosted
A Node.js CMS with in-context visual editing and an MIT-licensed core, plus a paid Pro edition and a multi-site product for agencies.
- In-context editing directly on the rendered page
- MIT-licensed core, free to self-host
- Pro at $199/mo, multi-site Assembly at $499/mo
- REST API
- Astro
- JavaScript / Node.js

Open source, self-hosted
A free, MIT-licensed Git-based CMS written as a successor to Decap. Most Decap configs switch with one script tag, but Bitbucket, Azure DevOps and Git Gateway sites cannot. Still a pre-1.0 beta with one maintainer.
- Reads Decap and Netlify CMS config: swap one script tag
- GitHub, GitLab and Gitea or Forgejo backends only
- First-class i18n with built-in AI translation on your own key
- Astro
- Next.js
- Svelte / SvelteKit
- JavaScript / Svelte, runs entirely in the browser

Open source, self-hosted
An open-source CMS for GitHub-hosted static sites that needs no install at all: authorise the hosted app against your repo and start editing.
- No install: authorise the hosted app against a GitHub repo
- Content committed directly to your repository
- Configured with a single YAML file
- Astro
- Next.js
- React
- TypeScript / Next.js

Open source, self-hosted
A CMS that lives inside VS Code. Content stays as Markdown in your repo and the editing interface is an editor panel, which suits developer-authored sites.
- Runs as a VS Code extension, no separate app
- Markdown and front matter in your own repo
- Content dashboard, media library and SEO checks
- Astro
- Next.js
- React
- TypeScript / VS Code

Open source, self-hosted
A git-based CMS with MIT-licensed packages, an AGPL-3.0 Studio, an official MCP server and cloud tiers starting at $9 a month. Content stays in your repository as JSON and Markdown.
- Git-based: content as JSON and Markdown in your repo
- MIT-licensed CLI, SDK and MCP packages; AGPL-3.0 Studio
- Official MCP server for AI clients
- Next.js
- React
- Vue / Nuxt
- TypeScript / Node.js

Free to start
Visual editing built entirely from your own React components, defined in code as bricks. The design system stays authoritative and editors compose within it.
- Content blocks are React components you write
- Visual editing constrained by your design system
- Free tier with 1 user and up to 60 pages
- React
- Next.js
- Astro
- Hosted SaaS

Open source, self-hosted
A small, self-hosted PHP headless CMS that adds content management to any project without imposing structure. MIT licensed and deliberately minimal.
- Runs on plain PHP with no heavy framework
- REST API and GraphQL for content delivery
- MIT licensed core
- REST API
- GraphQL API
- Vue / Nuxt
- PHP

Free to start
A hosted headless CMS with generated, typed SDKs and an OpenAPI schema per project. Free tier with 1,000 objects, paid from $37 a month.
- OpenAPI schema and generated SDKs per project
- REST and GraphQL content APIs
- Free tier with 2 members and 1,000 objects
- Next.js
- React
- Astro
- Hosted SaaS

Free to start
A Japanese hosted headless CMS with a clean API and a free tier at 10,000 content entries. Widely used in Japan and increasingly outside it.
- Simple REST content API with good SDKs
- Free Hobby tier with 3 members and 10,000 entries
- Content review and approval on higher tiers
- Next.js
- React
- Vue / Nuxt
- Hosted SaaS

Free to start
A Dutch headless CMS with personalisation and A/B testing built into the content layer rather than bolted on at the front end.
- Personalisation and A/B testing in the CMS itself
- REST and GraphQL content APIs
- Free Community tier with 3 users
- Next.js
- React
- Vue / Nuxt
- Hosted SaaS
Check the loader, the guide and live content
Tick what your Astro build needs; each platform shows its package where it has one.
What should the CMS give your Astro site?
8of 36 have it
| Platform | Official loader or integration8 | Any Astro loader11 | Guide in Astro's docs29 | Request-time content22 | Visual editing11 | Content in your repo7 |
|---|---|---|---|---|---|---|
| Sanity | ||||||
| Storyblok | ||||||
| DatoCMS | ||||||
| TinaCMS | ||||||
| CloudCannon | ||||||
| ApostropheCMS | ||||||
| Contentrain | ||||||
| React Bricks | ||||||
| Payload | ||||||
| Contentful | ||||||
| Strapi | ||||||
| Directus |
Read from each vendor's docs and npm packages and from Astro's CMS guides, 2026-11-20. "Not documented" means neither shows it.
Astro loaders and integrations, by maintainer
Who maintains the package decides how fast it follows Astro's releases.
| Platform | Package | Maintained by |
|---|---|---|
| Sanity | @sanity/astro | The vendor |
| Storyblok | @storyblok/astro | The vendor |
| Strapi | strapi-community-astro-loader | Community |
| DatoCMS | @datocms/astro | The vendor |
| TinaCMS | @tinacms/astro | The vendor |
| CloudCannon | @cloudcannon/editable-regions | The vendor |
| ApostropheCMS | @apostrophecms/apostrophe-astro | The vendor |
| Sveltia CMS | astro-loader-sveltia-cms | Community |
| Contentrain | @contentrain/query | The vendor |
| React Bricks | react-bricks | The vendor |
| microCMS | microcms-astro-loader | Community |
From npm, each package's repository and the vendor's docs, 2026-11-20.
A vendor-maintained loader is the safer bet for an Astro CMS: it moves with the vendor's API and is the vendor's job to keep current with Astro's releases. 21 more platforms, including Payload, Contentful, Directus and Ghost, have a page in Astro's guides but no loader, so you fetch with their own client. Some of those guide pages are short stubs that link out to the vendor.
Strapi, Sveltia CMS and microCMS have only a community loader. Community packages are often good, but check the release history and the Astro version in their peer dependencies before you build on one.
What a loader adds over a plain fetch
The same content, with types and a build that fails loudly.
A Content Layer loader puts CMS entries into a content collection, the same structure Astro uses for local Markdown. You query them with getCollection(), entries are checked against a schema, and a missing or misspelled field fails the build instead of shipping a broken page. A plain fetch gives you JSON and leaves the checking to you.
The trade is freshness. A loader runs at build time, so the site shows what the CMS held when it last built. For a headless cms for astro sites that change daily, that is fine with a webhook that triggers a deploy; for content that must change by the minute, fetch at request time instead.
How each platform connects to Astro
The route the docs support today, platform by platform.
- Sanity@sanity/astro
- Storyblok@storyblok/astro
- DatoCMS@datocms/astro
- TinaCMS@tinacms/astro
- CloudCannon@cloudcannon/editable-regions
- ApostropheCMS@apostrophecms/apostrophe-astro
- Contentrain@contentrain/query
- React Bricksreact-bricks
- Strapistrapi-community-astro-loader
- Sveltia CMSastro-loader-sveltia-cms
- microCMSmicrocms-astro-loader
From npm, each vendor's docs and Astro's CMS guides, 2026-11-20.
Publishing without a rebuild
A build-time loader means every publish waits for a deploy.
Most static hosts give each site a deploy hook: a URL that starts a build when called. Point the CMS's publish webhook at it and every publish rebuilds the site, which takes from seconds to minutes depending on the site's size. For a blog, a rebuild per publish is fine.
For a site with many publishes a day, the rebuilds add up. For a site where editors expect to see a change at once, an astro headless cms needs request-time content: server rendering with a fetch, or a loader that supports it. 22 platforms document that path for Astro.
Visual editing is rarer. Sanity, Storyblok, DatoCMS, Builder.io, TinaCMS, Contentstack, CloudCannon, dotCMS, ApostropheCMS, React Bricks and Prepr CMS document clicking the page to edit it in an Astro site. Most others offer a preview link at best, so check the review before promising editors a visual tool.
Git-based: Markdown Astro already reads
The simplest integration is none at all.
7 platforms here are Git-based: TinaCMS, Decap CMS, CloudCannon, Sveltia CMS, Pages CMS, Front Matter CMS and Contentrain. They give editors a form over the Markdown and JSON files in your repository, and Astro's built-in loader reads those files as it would without a CMS. For a docs site or a blog, that makes an astro js cms almost free to add.
The limits are Git's: every edit is a commit and a rebuild, and large collections strain the Git host's API. Our Git-based CMS page covers the setup and the sign-in work each one needs.
Open source options for Astro
Self-hosted, with the content in your own database or repository.
13 of the platforms here are open source: Payload, Strapi, Ghost, TinaCMS, Decap CMS, Keystone, WordPress (headless), ApostropheCMS, Sveltia CMS, Pages CMS, Front Matter CMS, Contentrain and Cockpit. The Git-based ones among them need no server at all for the content, since it lives in your repository. The rest need a database and a host, and some keep single sign-on or workflows in a paid edition: our open source headless CMS page lists what each free edition holds back.
How to choose the best CMS for Astro
Four checks, in the order they usually rule platforms out.
- 01Pick the routeBuild-time loader, request-time fetch or files in the repo. It decides how fast edits go live.
- 02Prefer an official loaderA vendor-maintained package follows Astro's releases; a community one may not.
- 03Check the editors' viewVisual editing for Astro is rare. Confirm preview before you promise it.
- 04Count the rebuildsWith a build-time loader, every publish is a deploy. Check your host's build minutes.
The best CMS for Astro is often the simplest one that fits. A content site edited by a few people rarely needs more than Markdown and a Git-based editor; a site with many editors and frequent changes earns a hosted platform with an official loader.
Where to go from here
- Headless CMS for Next.js46 platforms, 34 of them also on this page.
- Headless CMS for React48 platforms, 33 of them also on this page.
- Enterprise headless CMS31 platforms, 17 of them also on this page.
- Content engineeringWhat a headless CMS makes possible once content is structured.
- Content automationPipelines that publish into a CMS without copy and paste.
Head-to-head comparisons
- Sanity vs ContentfulOne bills each editor by the month. The other is a flat $300 that stops at twenty users and three locales.
- Sanity vs StrapiOne will never let you hold the database. The other will, and its MIT grant has conditions about exactly that.
- Sanity vs StoryblokOne makes the page the thing editors work on, block by block, in place. The other makes the document the thing you reuse, then previews the pages built from it.
Headless CMS for Astro, answered
Which Astro CMS platforms ship an official loader or integration?
Sanity, Storyblok, DatoCMS, TinaCMS, CloudCannon, ApostropheCMS, Contentrain and React Bricks. Each publishes its own Astro package, so it follows the vendor's API changes.Which headless CMS platforms have a guide in Astro's documentation?
29 of the platforms here: Payload, Sanity, Contentful, Storyblok, Strapi, Directus, Ghost, DatoCMS, Hygraph, Prismic, Builder.io, Statamic, TinaCMS, Decap CMS, Kontent.ai, Keystone, WordPress (headless), Craft CMS, Cosmic, ButterCMS, Caisy, Crystallize, CloudCannon, ApostropheCMS, Pages CMS, Front Matter CMS, Flotiq, microCMS and Prepr CMS. Some guides are short pages that link to the vendor's own docs.Can an Astro site show CMS changes without a rebuild?
Yes, with server rendering: the page fetches from the CMS on each request, so a published change shows on the next visit. With a build-time loader, a publish triggers a rebuild through a webhook instead.Does Astro need a CMS for a Markdown blog?
No. Astro reads Markdown from your repository with its built-in loader. A Git-based CMS adds a form for people who do not edit files, and commits their changes as Markdown.What is a content loader in Astro?
A loader is a function that fills an Astro content collection from any source: local files, an API or a CMS. Astro ships loaders for files; CMS vendors and the community publish loaders for their APIs, so CMS entries are queried like Markdown.Does TinaCMS work with Astro?
Yes. TinaCMS maintains `@tinacms/astro`, Astro's docs carry a Tina guide, and Tina offers an Astro starter. Content stays as Markdown or MDX in your repository, which Astro reads directly.Does Storyblok have an official Astro integration?
Yes. Storyblok maintains `@storyblok/astro`, and Astro's docs carry a Storyblok guide. It is one of the vendor-maintained packages listed above.Does Sanity have an official Astro integration?
Yes. Sanity maintains `@sanity/astro`, which connects an Astro site to Sanity and supports visual editing, and Astro's docs carry a Sanity page.
Picking the provider is the easy half.
busyless runs content and search as a system: we choose the data sources and tools, build the pipelines on top, and measure what they feed. If that is the part you are missing, talk to us.
Ask an assistant about this page
An independent comparison. No provider pays to be listed or to rank higher, outbound links carry nofollow, and we earn nothing if you sign up. Prices and terms were read from each vendor's own pages in November 2026 and change without notice.
Missing, or out of date?
Every entry here was read off the company's own website and dated, so some of it will have moved since. Corrections are free and so is being added. There is no fee, no sponsored position, and nothing that money moves up this page.