Version history for Strapi 5

Keep every version of your Strapi 5 entries: one on every save, autosaves every 60 seconds, a history per locale. Works on Community Edition.

On Strapi 5 Community Edition, an entry keeps only its current state. Revisionary keeps every version next to it, inside the admin your editors already use.

A version on every save

Each entry of a versioned content type gets a Version history panel in the Content Manager. It shows the latest versions, who made them and how much changed. While someone types, their work is autosaved every 60 seconds as a light version, so a closed browser loses nothing.

The panel sits next to the fields you edit, like any other Strapi pane.

Changes are recorded wherever they come from: the Content Manager, the REST API, GraphQL, the Document Service (your own code), cron jobs and imports. Turn a source off per content type, and exclude fields that should never be stored, like secrets, counters or computed values.

Browse the history

The Revisionary page lists every version of the entry, newest first, grouped by day. Each version shows its author, its state and what changed: +8 added, ~12 modified, −2 removed. Filter by published versions, versions in review, drafts or autosaves, and switch locale: each translation has its own history.

Consecutive autosaves fold into one line. Named versions carry a pin.

Above the content, a timeline lays out the whole history on one line. Drag it, scroll it or use the arrow keys: the version in the middle is the one you see.

Name the versions that matter

Give a version a name, like “Approved by legal” or “Before the redesign”, to find it again. Named versions are never removed by retention rules or limits.

Storage you can predict

Keep autosaves 7, 30 or 90 days, or forever, globally or per content type, and cap the versions kept per entry. Before you save a shorter retention, Revisionary tells you how many versions it would remove and how much space it would free. Named and published versions, versions in the trash and any version an autosave depends on are never removed.

Runs where your Strapi runs

Strapi 5 on Community Edition, Node.js 20, 22 or 24, and PostgreSQL, MySQL or SQLite. Nothing to change in your content types and no extra service to run.

Questions and answers

Does it work on Strapi Community Edition?

Yes. Revisionary runs on Strapi 5 Community Edition: no paid Strapi plan is required.

Which changes are recorded?

Saves from the Content Manager, the REST API, GraphQL, the Document Service, cron jobs and imports. Each source can be turned off per content type, and fields can be excluded.

What happens to the history if my subscription ends?

Recording stops after a 14-day grace period. Every version already recorded stays readable and restorable, and nothing is deleted.