---
copyright: "© 2026 DSR Corporation"
title: "Never lose a word"
slug: page-history
order: 50
type: doc
description: "Every save is versioned. Compare, preview, and revert any page — backed by a full audit trail."
seoTitle: "Versioned docs: page history, diff & revert"
seoDescription: "Every save is versioned. Browse page history, compare and preview any revision, and revert with one click — all self-hosted and backed by a full audit trail."
icon: History
visibility: public
llmSummary: "DSR Docs snapshots every page on every save, giving a version timeline, a diff against the current text, a rendered preview of any revision, and one-click reversible revert. Snapshots are hidden from search and navigation, visible only to editors and admins, and paired with a full admin audit log. Self-hosted in a single Docker container, so all revision history stays on your own infrastructure (on-prem/air-gapped capable)."
faq:
  - q: "Does DSR Docs keep version history for documentation pages?"
    a: "Yes, for every page, automatically. A snapshot is captured on every save, so there is nothing to enable and nothing to schedule. It works the same whether the page was written in the built-in editor or committed through the Git-backed docs-as-code workflow."
  - q: "Can I revert a documentation page to an earlier version?"
    a: "Yes, in one click from the page's timeline. A revert is itself a save, so it appends a new snapshot rather than rewriting the past — you can always roll forward again."
  - q: "Can I see what changed between two versions of a page?"
    a: "Yes. Any point in the timeline shows a diff against the current text, plus a fully rendered preview of how the page looked that day — not just the raw Markdown."
  - q: "Who can see page history, and does it leak into search?"
    a: "Snapshots are visible only to editors and admins, and they are filtered out of search and navigation, so readers never stumble into an old revision. Every change is also recorded in the admin audit log — what was edited, when, and by whom."
  - q: "Where is the revision history stored?"
    a: "On your own infrastructure. DSR Docs is self-hosted in a single Docker container, so every snapshot stays inside your deployment — including on-premises and air-gapped installations, where a hosted version-history service would not be an option."
---

# Never lose a word

Every save of every page is snapshotted automatically. There's no toggle to remember and nothing to set up — the version-history safety net is just *on*.

Open any page's history and you get:

- **A timeline** of every version, newest first.
- **A diff** against the current text, so "what changed" is obvious at a glance.
- **A rendered preview** of exactly how the page looked on any given day.
- **One-click revert** — and because a revert is itself a save, it's always reversible.

## How does per-page version history work in DSR Docs?

Because a snapshot is captured on every save, page history works the same whether you author in the built-in editor or commit through the Git-backed docs-as-code workflow. There's nothing to enable and nothing to schedule — the snapshot is simply a byproduct of saving. Since DSR Docs is self-hosted in a single Docker container, every revision lives on your own infrastructure, so your history stays intact even in on-prem or air-gapped deployments.

## Can I compare and revert a page to an earlier version?

Yes. Pick any point in the timeline to see a diff, preview the fully rendered page as it stood that day, and restore it with one click. Reverting doesn't rewrite the past — it appends a new snapshot — so you can always roll forward again.

## A trail you can trust

Snapshots are filtered out of search and navigation, visible only to editors and admins. Paired with a complete admin audit log of every change, you always know what was edited, when, and by whom. Mistakes become a non-event, and compliance becomes a checkbox you've already ticked.

Version history is one piece of a single self-hosted engine. See how [one engine renders every API](one-engine) and how [your docs get found by Google and AI](seo-and-discoverability).

> [!IMPORTANT]
> **Want this on your own documentation?** Write to docs@dsr-corporation.com. Ask about migration, licensing, or anything this page didn't cover.