Virtum

Virtum Docs

Docs that know what you run.

Documentation, runbooks and reports wired to the real systems they describe.

Become a design partner See all 60 features

Private development Design partners Q1 2027 · wider access Q2 2027 (targets)

Why it exists

Documentation goes stale the day it is written.

Runbooks live in someone's head, service reports take days to put together, and nobody knows which page to trust. Docs links every page to the systems it describes and flags it when they change, turns runbooks into procedures that actually run, and builds reports from verified evidence.

How it works

Write or import → Link → Keep fresh → Answer and report

  1. 01Write or importWrite in the editor, or bring in Confluence, Notion and git.
  2. 02LinkPages connected to the assets, incidents and findings they describe.
  3. 03Keep freshOwners, review dates and alerts when the real system changes.
  4. 04Answer and reportQuestions answered with citations; reports built from evidence.

In practice

Documentation that keeps up

  1. A firewall rule changes in Deploy.

  2. The network design page is flagged: what it describes has changed.

  3. Docs drafts an edit to bring it up to date. Its owner approves it.

  4. Someone asks "how do we restore the database?" and gets an answer with sources.

  5. The service report builds itself from verified evidence.

Who it's for

Built for the people who run it.

  • IT and engineering teams

    Documentation you can trust.

  • Service providers

    Client reports that write themselves.

  • Everyone

    Answers without asking around.

How it connects

Connected to everything else.

Work passes between Virtum's services on its own. Nothing is retyped, and nothing falls between tools.

  • Docs ↔ Operations · incidents

    Operations

    Incidents become postmortems; runbooks run from alerts.

  • Deploy → Docs · assets

    Deploy

    Every asset is documented automatically.

  • Security → Docs · evidence

    Security

    Compliance evidence and board reports.

  • Docs → Planner · report actions

    Planner

    Report actions become tasks.

See it end to end →

What it does today

Everything in Docs.

60 features across 10 areas. Search them, or open an area. The roadmap shows what comes next.

60 features
Spaces A home for every team's knowledge.6
  • Spaces per team or department
  • Space overview, page tree and members
  • Templates on the home page
  • Tags
  • An incidents space created for you
  • A page for every asset, kept current automatically
Writing Write once, keep it right.7
  • Markdown editor with slash commands
  • Drafts, review and publishing
  • Full version history and comparisons
  • Warnings when someone else edited mid-change
  • Attachments
  • Move, archive, restore and delete
  • Reusable templates
Review and governance Knowledge with an owner and a review date.8
  • Comments on pages or on a quoted sentence
  • @mentions and resolved threads
  • Review queue for due and overdue pages
  • Pages without an owner flagged
  • Classification: public, internal, confidential, restricted
  • Retention holds
  • Restricted pages and spaces
  • Viewer, editor and reviewer roles
Search and answers Ask and get an answer with sources.5
  • Search by meaning, not just keywords
  • Answers that cite their source pages
  • The live infrastructure behind a page shown with it
  • Pages linked to assets, incidents, findings and tasks
  • A knowledge graph of documents and records
Runbooks Procedures that can run, not just be read.8
  • Steps for instructions, checks, approvals, inputs, rollback and evidence
  • Versioned publishing
  • Runs with approvals, pause, resume and retry
  • Automatic rollback
  • Preview of what a run will touch
  • Run evidence downloads
  • Daily, weekly or monthly schedules
  • Runbooks bound to alerts and finding types
Decisions and postmortems Why things are the way they are.3
  • Architecture decision records: proposed, accepted, superseded
  • What each decision governs
  • Postmortems published from resolved incidents
Service reports and QBRs Reports built from evidence, not claims.9
  • Monthly service reports, QBRs and board compliance reports
  • Executive summary, KPIs, wins, risks and actions
  • Review, approval and versioning
  • Report actions sent to Planner
  • Internal and customer-facing versions
  • PDF, HTML and evidence CSV exports
  • Secure links with expiry and view limits
  • Scheduled reports with automatic delivery
  • Versioned report templates and history
Publishing and imports Bring it in, put it out.4
  • Publish a space as a public docs site
  • Two-way git sync with conflicts named
  • Import from Confluence and Notion
  • Content pulled in from Deploy, Operations incidents and SharePoint
Health and analytics Know which docs to trust.5
  • Pages whose infrastructure changed since they were written
  • Freshness scores
  • Most-read and never-read pages
  • Searches that found nothing
  • Activity feed
AI writing AI drafts; people approve.5
  • AI drafts new pages for approval
  • AI proposes edits for approval
  • Summaries of a page or a whole space
  • Standard operating procedures generated
  • Stale or missing sections flagged

Connected today

Works with what you already run.

Every integration runs through the same approvals and audit trail, and new ones are added as data, so the list keeps growing. How integrations work →

Imports and sources

  • Confluence
  • Notion
  • SharePoint
  • Git

Shared by every service

Plus the whole Virtum platform.

Put Docs to work.

Design partners get early access and help shape what comes next. Or let Virtum run it for you as a managed service.

Become a design partner Prefer we run it for you?