Keeping track of every change

Content changes over time, and sometimes you need to go back. We've added a lightweight version control system for Items (pages, articles, blocks, and more) directly into Backstage, our content editor, with full support in our MCP (Model Context Protocol) tools as well.

How it works

Every item can have historical snapshots that record its state at a point in time. Snapshots reuse the existing OriginalItemId link on the item, so no new database structures were needed — the same field already used for language versions now also carries version history, distinguished by a negative version number.

• Manual versions – from the editor's menu, next to "Duplicate page", you'll find a new "Create new version" action that snapshots the current state without changing anything else.
• Automatic daily snapshots – the first time you save an item on a new calendar day, the previous day's state is automatically archived before your changes are applied. No extra clicks needed.
• Version history dialog – the Properties tab now shows the current version number and a button that opens a dialog listing every saved version, complete with save date, a direct link to open that version in the editor, and a one-click revert.
• Read-only snapshots – when you open a historical version directly, the Save button is disabled to prevent accidentally overwriting the live item. Reverting is done explicitly from the version history dialog instead.

Available through MCP too

AI assistants and automation using our MCP server can create version snapshots, list version history, and revert items to a previous version — the same building blocks that power the Backstage UI are exposed as MCP tools, so editorial workflows can be scripted or assisted by AI.

Why it matters

Version history gives editors confidence to experiment: try a new headline, restructure a page, or let an AI assistant make bulk edits, knowing a safety net is always just a click away.