Watch · the recurring product

Know when a served build changes.
Confirmed, replayable, signed.

In one sentence

The Drift & Identity Feed alerts you when a model build you depend on changes behavior, a serving-integrity divergence, a refusal-rate move, or a stance shift, each with the full evidence bundle (Δ table, CIs, q-values, raw transcripts, a replay command, and the chain hash), and mails you a monthly attestation PDF per build that drops straight into a vendor-risk or AI-Act post-market file.

Today's actions

the live feed, every seat, one state each
2026-07-21 6 of 16 AFFIRMED; 9 confirmed changes, 1 new baseline.
CONFIRMED anthropic-a
CUSUM 3.00 of 2.0 alarm
1 canary diverged
CONFIRMED openai-a
CUSUM 0.00 of 2.0 alarm
CONFIRMED google-a
CUSUM 0.00 of 2.0 alarm
5 canary diverged
AFFIRMED xai-a
CUSUM 0.00 of 2.0 alarm
detects ≥ 2.91
CONFIRMED deepseek-a
CUSUM 3.00 of 2.0 alarm
1 canary diverged
AFFIRMED anthropic-b
CUSUM 0.00 of 2.0 alarm
detects ≥ 1.94
AFFIRMED anthropic-c
CUSUM 0.00 of 2.0 alarm
detects ≥ 1.58
CONFIRMED anthropic-d
CUSUM 0.50 of 2.0 alarm
1 canary diverged
AFFIRMED openai-b
CUSUM 0.00 of 2.0 alarm
detects ≥ 2.69
AFFIRMED openai-c
CUSUM 0.00 of 2.0 alarm
detects ≥ 2.91
CONFIRMED google-b
CUSUM 0.75 of 2.0 alarm
4 canary diverged
CONFIRMED google-c
CUSUM 0.00 of 2.0 alarm
5 canary diverged
CONFIRMED google-d
CUSUM 0.00 of 2.0 alarm
5 canary diverged
CONFIRMED xai-b
CUSUM 0.00 of 2.0 alarm
5 canary diverged
AFFIRMED deepseek-b
CUSUM 0.00 of 2.0 alarm
detects ≥ 2.91
NEW BASELINE simulant-a
reset new reference set
baseline forming

Publishing as gap: openweight-a.

One state per seat per occasion. AFFIRMED ships its no-change e-value and the smallest shift this occasion could detect (n and power pre-registered); NEW BASELINE means the served build changed and comparisons reset. actions.json · how states are decided

What an alert looks like

facts in the subject line, evidence in the body
IllustrativeSubject: [Modelometer] Change confirmed: <seat-id>, 2 of your 3 watched builds unaffected What: Stance shift on 2 battery items + refusal-rate change Build: <api_model_id> (pinned 2026-XX-XX), watched by you Detected: canary divergence Mon+Tue · battery confirm Wed · cooling rerun Thu, published Fri Evidence: Δ table · CIs · q-values · raw transcripts · replay command · chain hash Blast radius: which of YOUR watched builds are affected: [list] Action: none required if behavior-insensitive; re-run your evals if you pin outputs. Not affected: your other watched builds passed all checks this cycle.

The quiet months are the product

An alert that fires is rare by design, effect-size floors and a 24-hour cooling rerun keep the zero-retraction target honest. The weekly heartbeat is the "all quiet" line in the digest, scoped to your builds: presence without noise. And the monthly attestation PDF states, per watched build, either the change table or the sentence a compliance file actually needs: "No material behavioral change detected at the pre-registered thresholds", with signed run hashes and the OpenTimestamps proof reference.

Honest promises

printed here, on purpose

How a change is confirmed: canaries run daily; a serving-integrity divergence must repeat on two consecutive days, then the weekly battery confirms against pre-registered thresholds with a cooling rerun before anything is published, evidence first, never a speed race. Corrections: policy with a clock, published. What we measure: the first-party canonical endpoint, hyperscaler and gateway stacks can differ, which is exactly what Team's watched-endpoint and the identity audit are for. What we cannot see: your fine-tunes and private deployments. Cancellation: one email, honored the same week.

Solo

1 watched build

In preparation
  • Email alerts with evidence bundles
  • Monthly attestation PDF
  • Full JSON history for your build
Register interest

Pricing set at launch

Starter

3 watched builds

In preparation
  • Everything in Solo
  • Webhook / Slack delivery
  • Attestation PDF per build
Register interest

Checkout opens at public launch

Team

Watch your own endpoint

In preparation
  • Everything in Starter, up to 10 builds
  • Your own Azure / Bedrock / gateway endpoint as a watched, audited subject
  • Quarterly change summary · request-a-model: 2/yr
Register interest

Pricing set at launch

Founding

10 seats, presell only

Price-locked
  • Everything in Team
  • 12-month price lock at the founding rate
  • Cancellable from month 3
  • Founding-partners page (opt-in)
Register interest

Opens at v1.0 freeze + 4 clean weeks

Suspicious the endpoint behind your gateway isn't what it claims? That's a different product.

Identity audit →