state.observer: A Git-Backed Time Machine for Your Project Portfolio

Git DevOps Preview Snapshot Portfolio Time Machine

What if you could spin up any commit, in any repo, in a live preview container — without touching your working branch?

state.observer is a git-aware snapshot and time-machine service. Cross-project commit search. Live preview from any commit hash. Selective file restore. And a forensic sync audit trail for every push, pull, and fetch your fleet performs.

Explore state.observer →

state.observer

  1. Portfolio overview — activity calendar, top projects, run status across every repo
    Portfolio overview — activity calendar, top projects, run status across every repo
  2. Simulations — sandbox commits and deploys against your project graph before they touch real state
    Simulations — sandbox commits and deploys against your project graph before they touch real state
  3. Snapshot pipelines — define what gets captured, when, and on which trigger
    Snapshot pipelines — define what gets captured, when, and on which trigger
  4. Cron-triggered snapshot runs with per-project history and trigger metadata
    Cron-triggered snapshot runs with per-project history and trigger metadata
  5. Built-in SQL workbench against the snapshot store — read-only, schema-aware
    Built-in SQL workbench against the snapshot store — read-only, schema-aware
  6. Environments grid — per-project deploy status across every target
    Environments grid — per-project deploy status across every target
  7. Fleet specs — apply snapshots, commits, or shell commands across many projects at once
    Fleet specs — apply snapshots, commits, or shell commands across many projects at once

The Problem with Multi-Repo Git History

When an AI agent (or a human) makes a sequence of changes across a multi-repo project portfolio, “what state was this 3 hours ago, before everything broke?” is a question with no good answer.

  • Git history is per-repo. Hard to query across projects.
  • There’s no way to see a previous commit running.
  • Code review against an old version means checking it out, building it, running it — destroying your current branch.
  • Auditing what changed during an AI session means scrubbing terminal logs.

You need a time machine.

What state.observer Does

A git-aware snapshot and time-machine service.

  • Registers your projects and indexes commit history into a SQLite database for cross-project search
  • Spins up ephemeral preview containers from any commit hash with TTL cleanup
  • REST API + React dashboard for browsing, querying, snapshotting, restoring
  • Selective file restore or full hard reset to any commit
  • Sync event audit trail for every git push / pull / fetch with classified errors

Three Reasons Engineering Teams Choose It

1. Live Preview from Any Commit

Spin up a containerized preview at any commit hash with automatic TTL cleanup. Code review against a previous version in a browser — not in a checkout dance that destroys your branch.

Reviewer opens the URL. Sees the old behavior. Compares. Closes the tab. Container reaps itself.

SQLite-backed history lets you query across the whole portfolio:

  • “What changed across all repos last Tuesday?”
  • “Find every commit that touched auth.js in any project.”
  • “Which repo broke when we deployed Friday afternoon?”

Answers in seconds. Not in five git log tabs.

3. Sync Forensics

Every git push, pull, and fetch is logged with commit counts, timestamps, and classified errors — auth failures, conflicts, non-fast-forward, permission denied.

When a deploy goes wrong because of a non-fast-forward push, the audit trail tells you exactly when and why.

How It Compares

Capability state.observer GitHub GitLab Bitbucket
Cross-repo commit search Yes Per-repo Per-repo Per-repo
Live preview from any commit Yes PR only PR only No
Sync audit + error classification Yes No No No
Embeddable widget Yes (UMD) No No No
Self-hosted Yes Server only Yes Yes

Who Buys It

Engineering Managers

Portfolio view of git activity across many repos. One dashboard. One commit timeline. One place to spot the change that broke production.

Code Reviewers & Staff Engineers

See old versions running. Not just diffs. Preview containers make “does this still work?” answerable in 30 seconds.

Platform / SRE Teams

Sync-operation forensics for deploy incidents. The audit trail is the post-mortem.

Better Together: The Observer Suite

state.observer is the portfolio history layer:

  • tasks.observer task IDs reference the commits that satisfied them; state.observer cross-indexes them
  • transmission.observer spawns preview containers via state.observer when AI sessions ask for them
  • tests.observer can run against a preview container at any commit for regression testing
  • logging.observer receives sync event telemetry

Run it standalone for any set of git repositories. The dashboard, commit history, snapshot API, restore operations, and sync audit trail all function with zero Observer dependency. The embeddable TimeMachine widget (UMD bundle) drops into any internal tool.

SQLite storage. No external database required.

Getting Started

  1. POST /api/projects to register your repos
  2. Browse the dashboard at http://localhost:3400
  3. Generate a preview container at any commit
  4. Wire the TimeMachine widget into your internal tools

TL;DR

state.observer = a time machine for your code portfolio.

Snapshot any state. Restore any commit. Preview any commit live. Cross-project commit search. Sync forensics. Embeddable widget.

📞 Contact us to bring state.observer to your fleet.

Written on February 5, 2026