Vigie
Features

Releases

Mark each deploy, and Vigie tells you whether it made things worse.

Declare a release from CI, after the deploy:

bunx vigie deploy --url https://vigie.acme.dev --token vd_… --service acme-api --version $GIT_SHA --env production

Create the deploy token on Settings, Tokens. Without it, Vigie still notices a new service.version on incoming data and marks it as detected.

The Releases screen gives each release a verdict: error rate and p95 latency in the hour after, against the hour before, plus issues that came back with it. A release is a regression, changed or clean, or unknown when there were too few requests to judge.

Agents read it with get_release_verdict, and can declare one with declare_deployment.

With VIGIE_SOURCE_REPO set (acme/shop), Vigie reads the source behind stack frames from GitHub. Add VIGIE_GITHUB_TOKEN for a private repository.

Copyright © 2026