Determinism agent

Deterministic, or
it doesn't ship.

guard replays production agent runs bit-for-bit against a sealed baseline and flags any drift. If an output cannot be reproduced, it does not deploy.

See pricing →
Priced after a short conversation
RIG guard agent visual

guard · replay verification · sealed baselines

Why teams install

What guard earns back

Catches silent model drift

Provider-side changes surface as replay deltas the same day they ship.

‹2ab9e71›

Bit-exact baselines

Seeded, pinned, sandboxed reruns — hash-matched or blocked.

‹c08d3b5›

Audit-ready trails

Every production answer links back to its reproducible proof.

‹84f6d29›

How it works

Three steps. No faith required.

01

Pin

Freeze model, seed, tools, and context into a baseline manifest.

02

Replay

guard reruns sampled production calls inside the sealed environment.

03

Quarantine

Drift beyond tolerance rolls the release back. No meeting required.

Proof band

One packet. Every claim accounted for.

proofpacket · rig/guard · sealed
packet    rig/guard · replay batch 2ab9e71
manifest  model pinned · seed 42 · tools frozen
replays   512/512 matched · drift 0.000
baseline  sha ‹84f6d29› · bit-exact
pauli     PASS — no state collision across runs
themis    SEALED — release may proceed
SEALED

Every guard run emits a packet like this — hash-chained, verifier-signed, and queryable from your own dashboard. How ProofPackets work →

Buyers

Who runs guard

CO

Compliance Officer

healthtech, HIPAA scope

SE

Staff Engineer

trading systems

C

CTO

enterprise AI vendor

Before you install

The obvious objections

Q Isn't bit-exact replay overkill — can't I just diff outputs?

A text diff catches wording drift; it says nothing about whether the model, seed, tools, and context that produced the output are still the same. guard pins the entire manifest and replays inside a sandboxed baseline, so drift shows up in the pauli check before it reaches a customer.

Q How do I know 99.98% replay match isn't measured on easy cases?

The suite reruns 512 sampled production calls per batch against the frozen baseline, not a curated demo set. Flip the manifest pin off and drift shows up on every workload, not a hand-picked one — that's the planted-failure regression in the gate.

Q What happens when a release actually drifts?

gate_replay_match goes RED, themis marks the release REFUTED, and the rollout is quarantined automatically — no meeting, no manual sign-off required. The full replay diff stays attached to the refuted run.

Pricing

Start free. Pay when it pays.

Generalist
Priced after a short conversation — ships today
Domain Expert
Priced after a short conversation · vertical memory + priors
Custom
Priced after a short conversation · scoped

Generalist ships today. Domain Expert adds vertical memory + priors. Custom is built to your stack.

Free

Priced after a short conversation

1K replays a month. One sealed baseline.

Team

Priced after a short conversation

Unlimited baselines, auto-rollback, drift alerts.

Pro

Priced after a short conversation

Air-gapped runners, SOC 2 evidence bundle.

Early installs keep the terms they sign; later slots are priced after a short conversation.