Skip to content

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

Featured

Best 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
FreeCloud or self-hosted · Open source

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)
$0Managed SaaS · Proprietary

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
$0Managed SaaS · Proprietary

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
$0Managed SaaS · Proprietary

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
FreeManaged SaaS · Open source

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
FreeManaged SaaS · Source available

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
FreeManaged SaaS · Open source

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
€0Managed SaaS · Proprietary

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

PlatformOfficial loader or integration8Any Astro loader11Guide in Astro's docs29Request-time content22Visual editing11Content 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.

11 platforms
PlatformPackageMaintained by
Sanity@sanity/astroThe vendor
Storyblok@storyblok/astroThe vendor
Strapistrapi-community-astro-loaderCommunity
DatoCMS@datocms/astroThe vendor
TinaCMS@tinacms/astroThe vendor
CloudCannon@cloudcannon/editable-regionsThe vendor
ApostropheCMS@apostrophecms/apostrophe-astroThe vendor
Sveltia CMSastro-loader-sveltia-cmsCommunity
Contentrain@contentrain/queryThe vendor
React Bricksreact-bricksThe vendor
microCMSmicrocms-astro-loaderCommunity

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.

36 platforms in 5 groupsHow each platform connects to Astro11 of 36connect through an Astro loader or integration
Vendor loader8
Community loader3
Markdown in your repo3
Own client only4

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.

  1. 01Pick the routeBuild-time loader, request-time fetch or files in the repo. It decides how fast edits go live.
  2. 02Prefer an official loaderA vendor-maintained package follows Astro's releases; a community one may not.
  3. 03Check the editors' viewVisual editing for Astro is rare. Confirm preview before you promise it.
  4. 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.

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

ChatGPTClaudePerplexity

For scripts and agents

Markdownllms.txt

MCP server: https://busyless.space/api/mcp

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.