StackCircuit365
For developers

Under the hood.

From the Vercel webhook to a verified rollback, here is the exact path a release runs through. A deterministic policy engine controls every write. The AI only reads evidence and drafts the report.

$ npm i -g stackcircuit365
$ stackcircuit watch --repo you/app --prod https://app.example.dev
baseline healthy // known-good locked: dpl_9f21c
01

Ingest the deploy event

Vercel fires deployment.succeeded. We verify the signature, persist the event, and resolve it to a GitHub SHA.

POST /webhooks/vercel 200
dpl_7c33a -> e9f14a2
02

Tighten the health window

For ten to fifteen minutes after promotion, polls drop to every few seconds against your URL and optional /health.

GET /api/health 200 210ms
GET /api/health 500 3.2s x4
03

Correlate and score

Failure onset is diffed against deploy time and checked against dependency status before any verdict is reached.

onset delta 1m54s
deps ok confidence 0.93
04

Recover to known-good

The last verified deployment is the target. Your policy decides recommend or execute, then we re-poll to confirm.

rollback -> dpl_6b0f9
verify 10/10 70s
05

Emit a replayable record

A signed incident timeline with the commit, deploy, checks, cause, action, and recovery, ready to audit.

incident inc_20260904
status closed signed

New to shipping to production? See the simple version.

Install from npm