Strapi for publishers: open-source headless, paid editorial tiers

What is Strapi?

Strapi is a headless content management system: an admin panel for editors and an API for developers, with no public-facing theme. It is published as open-source code on GitHub under the strapi/strapi repository, and the vendor sells paid plans on top. The latest release on GitHub when we checked was v5.57.0, published 7 October 2026.

For a news or magazine site, that means two projects instead of one. Strapi holds articles, authors, categories and media. A separate front end, often built on a framework such as Next.js, fetches that content and renders pages. If you are weighing this model against a traditional CMS, the headless guide sets out the cost of that split.

Who is Strapi best for?

Strapi fits a publisher that already has, or will hire, JavaScript developers and wants control over hosting and data. It suits a multi-channel operation where the same articles feed a website, an app and a newsletter tool through one API. The free tier covers drafts, roles, translation and media, so a small team can start without a subscription.

It is a poor fit for a small newsroom with no developer. Nothing in Strapi produces a public website, so a non-technical editor cannot install it and start publishing. Teams that need enforced multi-stage approval on a budget should read the workflow section below before committing.

Editorial workflow

Strapi ships three built-in admin roles: Author, who creates and manages their own content, Editor, who can create content and manage and publish any content, and Super Admin. The documentation lists role-based access control as a free feature.

Draft & Publish is also free. Each entry is a Draft, Modified (published earlier, with unsaved changes) or Published. Scheduling is different: to publish at a set time you add the entry to a Release and schedule the release, and the documentation ties that to the Growth and Enterprise plans.

Formal review is a paid feature. Review Workflows give you stages such as To do, In progress, Ready to review and Reviewed, with roles controlling who may move an item in and out of each stage. The documentation says they are exclusive to the Enterprise plan, and the pricing page marks Audit Logs the same way. Content History is listed at 14 days on Growth.

What the front end must handle: preview. Strapi does not render your site, so previews depend on your code. You configure a preview handler in /config/admin.ts that builds a front-end URL, and your developers build a preview route that switches on draft content. The documentation points to Next.js draft mode and Nuxt preview mode as examples. The free plan gives a full-screen preview; the side-by-side Live Preview is on paid plans.

SEO, structured data and feeds

Strapi is an API, so search visibility is decided by the front end. None of the Strapi documentation pages we read for this profile describe a built-in sitemap generator, structured-data output or redirect manager. Treat each as a task for your front end unless a plugin you have checked says otherwise.

In practice, the front end team must deliver:

• Sitemaps and news sitemaps: generated from the Strapi API, with accurate lastmod dates. Publishers who want Google News coverage should read Google’s own news sitemap documentation.
• Structured data: Article or NewsArticle JSON-LD built from your content fields, using schema.org types. Store the fields you need (author, publication date, image) as proper content-type attributes so the markup can be generated.
• Redirects: a redirect map applied at the web server, CDN or framework level. If you migrate from another CMS, URL changes are your responsibility.
• Canonical tags, titles and meta descriptions: add fields for them to your content types and render them in the page head.
• Feeds: RSS or Atom generated from the API by your front end.
• Preview and draft isolation: make sure draft content is never publicly served or indexed.

Media, multilingual and performance

The Media Library is free and organises assets in folders of unlimited depth. Editors can add alt text and captions, crop with a focal point, and replace a file while keeping its ID. Strapi can generate responsive image sizes; the documented breakpoints are 500, 750 and 1000 pixels. Official upload providers are local disk (the default), Amazon S3 and Cloudinary, and the default maximum file size is 1GB.

Internationalization is free and uses a pre-created list of more than 500 locales; custom locales cannot be created. The documentation says content is edited one locale at a time. Automatic AI translation requires the Growth or Enterprise plan. For performance, caching and CDN configuration happen on your front end and hosting, not inside Strapi.

Hosting and requirements

Strapi runs on Node.js. The installation documentation supports only Active LTS or Maintenance LTS versions, listed as v22, v24 and v26, and says odd-numbered “Current” releases are not supported. You need a SQL database: MySQL 8.0 or later, MariaDB 10.3 or later, PostgreSQL 14.0 or later, or SQLite. It also says Python is required if you use SQLite.

The same page states that Strapi does not support MongoDB or other NoSQL databases, nor cloud-native databases such as Amazon Aurora or Google Cloud SQL. If your infrastructure team has standardised on one of those, check before you commit. Plan for a persistent database, backups, and file storage that survives restarts.

Extending Strapi

Strapi exposes REST and GraphQL APIs on every plan, according to the pricing page. Content types are modelled in the admin panel or in code, and the preview handler is configured in code. Custom media providers can be written following the vendor’s guide. We have not verified the size of the plugin ecosystem, so we do not quote a number.

What Strapi costs

The licence is free for the Community Edition. The vendor’s self-hosted pricing page lists Growth at $45 per month including three seats, with extra seats at $15 per month, and Enterprise at custom pricing. It does not state the currency beside the figures, so confirm it when you buy.

Paid plans add Live Preview, Releases, Content History, AI credits, and, on Enterprise, Review Workflows and Audit Logs. SSO is listed as an add-on on Growth and included on Enterprise. Beyond the subscription, budget for hosting, a database, developer time for the front end, and maintenance. See the cost guide and the licence guide for how these line up against other systems.

Where Strapi falls short

• No front end. Everything a reader sees, including SEO output, must be built separately.
• Approval workflow is paid. Review Workflows and Audit Logs sit on the Enterprise plan, so a small paid team gets drafts and roles only.
• Single-locale editing. Editors work on one locale at a time.
• Narrow database support. SQL only, with some cloud-native databases excluded.
• Mixed licence. The code under ee/ is not MIT. Check which features you rely on before assuming everything is open.
• Node.js upkeep. Only LTS Node versions are supported, so you will upgrade the runtime on a schedule.

The verdict for publishers

Strapi is a sound choice for a publisher with in-house developers, a clear front-end plan and a need for an API-first content store they host themselves. The free edition covers drafts, roles, translation and media. The paid tiers cover the parts newsrooms often want: live preview, scheduled releases, audit logs and staged review.

It is the wrong choice if you want a site working next week without developers. Compare it with other headless options and with self-hosted traditional systems on the comparison hub before you decide. This profile is based on vendor documentation; see how we test for what a documentation-only review means.