Rewind your estate to any moment. Prove nothing else moved.
Time Machine keeps up to seven years of write-protected history, so you can reconstruct exactly what you ran on any date and diff any two moments down to the single changed attribute. When an auditor asks "what did production look like last March?", the answer is a query.
⚡ Premium add-on module · join the waitlist
History you can query, and trust.
The core platform already keeps a tamper-evident trail. Time Machine turns that trail into a time axis: retained longer, kept in hash-chained batches, and navigable by date.
Point-in-time queries
Traditional CMDB and ITAM tools keep history per asset, so rebuilding what the whole estate looked like on a past date means reverse-engineering the dependencies by hand: slow, error-prone, and rarely complete. Time Machine reconstructs any asset, or the entire estate with its relationships intact, exactly as it stood at a chosen date and time. Not a backup you restore; a view you open.
Time-diff comparison
Pick two moments and see every addition, removal, and attribute change between them, resource by resource. "What changed since the last audit?" answered in one screen.
Retrospective root-cause
Change management and release management records are rarely granular enough to capture the full blast radius or the side effects of a change. Time Machine is complementary: walk the timeline to the exact moment a value changed, see who changed it and everything that moved with it, and recover the data points a change ticket never recorded. Root-cause without guesswork or lost history.
Resource continuity & lineage
Cloud resources get replaced, not just edited: an instance is rebuilt, an auto-scaling group swaps a node, a database is re-created under a new ID. Time Machine links each successor to what it replaced, so a resource keeps one followable history across every recreation. Walk the lineage back to what a thing used to be, or forward through its succession, with dependencies and ownership carried across the break, not lost at it.
Suggested, never assumed
Some replacements are provable — a resource carries the same auto-scaling group or launch-template identity as the one it retired — and Time Machine links those automatically. The rest are only likely, so they are proposed for review, not assumed: you see the signals behind each match and how confident it is, then confirm, reject, or snooze it. A dismissed link stays dismissed. Confirming joins two records in history; it never merges them into one, so nothing is quietly rewritten.
Relationship / dependency
Dependencies are first-class and versioned: depends-on, runs-on, and member-of edges are captured with every state. A point-in-time view rebuilds the relationships between resources, not just the resources, so you can see what depended on what on any past date, and how the graph moved between two moments.
Write-protected retention, up to 7 years
Every captured state written to write-protected, tamper-evident storage and retained for the window you choose, up to seven years while you are a customer, with the Data retention add-on. It can't be changed in normal operation; personal data can still be erased on request.
Write-protected evidence storage
Evidence is kept in write-protected storage for up to seven years, and the audit trail is kept in hash-chained batches. A customer-verifiable evidence chain is planned.
Evidence export, any window
Export the reconstructed state, or the diff, for exactly the window an auditor names, in CSV, JSON, PDF, or XLSX. Defensible evidence, scoped to the request.
What it touches, and what it used to be.
Dependencies connect different things at one moment. Continuity connects the same thing across moments. Omnitam keeps both, side by side and deliberately separate, so a rebuild that scrambles one leaves the other intact.
| Relationships & dependenciesthe map — what is connected now | Continuity & lineagethe history — where a thing came from | |
|---|---|---|
| Question | What does this touch, right now? | What was this before? |
| The edge is | Between different resources — an instance and its network, storage, and identity. | Between the same resource across its rebuilds — each successor and the one it replaced. |
| True as of | The present — a live picture, redrawn on every scan. | All of time — added as resources are replaced, and never overwritten. |
| It answers | Blast radius — what else is affected if this changes or breaks. | Followable history — walk back to what a thing used to be, or forward through its succession. |
| Survives a rebuild? | No — the new resource is mapped again from scratch. | Yes — the link is what carries identity, ownership, and dependencies across the break. |
Two dates. Every change between them.
Select a baseline moment and a target moment; Time Machine replays the retained history and shows precisely what moved.
| resource | attribute | 2026-03-01 | 2026-06-01 | |
|---|---|---|---|---|
| + | waf-edge | present | absent | enabled |
| ≠ | orders-db | engine version | postgres 14.6 | postgres 15.3 |
| ≠ | orders-api | instance count | 2 | 3 |
| − | legacy-batch | present | enabled | decommissioned |
| ≠ | tls · api.acme.com | expiry | 2026-04-30 | 2027-04-30 |
The past, on the record.
Answer the retrospective ask
Audits, disputes, and incident reviews all ask the same question: what did it look like then? Time Machine answers with a reconstructed view of the whole estate and its dependencies, not a per-asset history you stitch back together by hand.
Show continuity of control
Retained, write-protected history and point-in-time state show how a control operated across the whole period, the difference between "we believe" and "here is the evidence" for SOX and SOC 2.
Retain longer than the source
Cloud APIs forget. Time Machine keeps up to seven years of state independent of what your accounts still hold, so history survives re-platforming, deletions, and account churn.
About Time Machine.
How is this different from the audit trail in the core?
The core keeps a tamper-evident audit trail of changes for up to seven years. Time Machine adds the time axis on top: point-in-time reconstruction of full state, date-to-date diffs, and export scoped to any historical window. A customer-verifiable evidence chain is planned.
Is it a premium add-on?
Yes. Time Machine is a premium add-on module, available on Essential and above. Module pricing is published when trials open; join the waitlist to hear first.
Can an auditor verify the evidence chain today?
Not yet. Today evidence is kept in write-protected storage and the audit trail is kept in hash-chained batches, so it can't be changed in normal operation. A customer-verifiable chain, which an auditor could check independently, is planned.
How far back can I query?
Up to seven years while you are a customer, from the point Time Machine is enabled. History accrues going forward; the further back you want to reconstruct, the earlier it pays to switch it on.
Start the clock today. Thank yourself at the next audit.
Turn on Time Machine when trials open and every captured state from then on is retained, queryable, and kept for up to seven years.