Skip to content

Strapi

Strapi turns content types such as a product guide or event into entries your website can request. Run the CMS yourself or pay Strapi Cloud to host it.

Visit Strapi

What needs hosting if you choose Strapi?

Strapi Community is free open-source CMS software. If you self-host it, plan where the CMS server, database and uploaded files will run and who will maintain them. Strapi Cloud can run the CMS for you. The public website still needs its own hosting.

A paid Cloud plan buys hosting resources. A separate CMS license can buy features such as Content History. On November 12, 2026, the Cloud pricing page showed Starter at US$35 per project per month, with 100,000 requests and 50 GB of media delivery per month and 50 GB of media storage per environment. Starter sleeps when idle. Compare the price and backup schedule for the plan you would use.

Who can edit an entry and who can publish it?

The Strapi admin panel has roles for the people who work on content. An Author can create and manage their own entries, and an Editor can publish. Check the role’s actual permissions and enable Draft & Publish for the specific content type if a writer needs to save drafts for review.

Keep this content type private so visitors cannot read it directly from the CMS. The site’s server uses a credential limited to the reads it needs and returns only the published content intended for visitors. Keep that credential on the server and drafts in the authorized editing view. With Draft & Publish enabled, an automated REST write can publish immediately unless it explicitly requests draft status. Check that before connecting an importer or an automation.

What does a Strapi backup leave out?

The local export can include entries, relations, schema definitions, configuration and uploaded files. It does not carry admin accounts or API tokens. If you keep media in a separate storage service, verify which actual files are in the export and plan how to copy any missing originals.

An import can replace the destination’s data and uploads and requires matching content types. Test the move with an isolated destination database and separate media storage. Strapi warns that an import can delete remote files if the target shares storage with another environment. Keep the production bucket disconnected.

How can you rehearse an edit and a restore without touching the live CMS?

Sketch a fictional event entry, its published page and a disposable destination. Keep every real database, CMS token and media bucket disconnected.

  1. Give the editor a draft
    Draw a new date in the admin panel and the old date on the public page. Decide who can publish the new date. Mark whether a future automated write is expected to save a draft or publish immediately.
  2. Check what the site can read
    Draw an anonymous request straight to the CMS and mark it denied. Then draw a visitor opening the site. The site’s server keeps its read credential private and returns only the published event with the old date. Keep the new date in the authorized editing view until the publisher approves it.
  3. Draw the destination before moving data
    Give the destination matching content types and its own database and media storage. List the accounts and tokens that would need recreation. Compare the event date and image on the sketch before reconnecting anything.