Skip to content
env-sync-viewer
Menu

Reference

The viewer

One page behind the access gate: a targets table and the recent collector runs. It reads; it never writes.

What it shows

Targets

Service
The service from its manifest
Env
The env, such as prod
Platform
caprover or vercel
Target
The target descriptor
Status
match, drift or error, a stale badge, and the error if any
Last synced
Last ok snapshot, with last seen under it
Keys
Each key name with its key state

Recent collector runs

Completed
When it finished
Started
When the run started
Outcome
success, partial or failed
Error
The run’s error summary, if any
svc-a   prod   vercel   example.com project   drift
  ENV_VAR_ONE    match
  ENV_VAR_TWO    drift
  ENV_VAR_THREE  missing

What it never shows

  • A secret value: none is stored anywhere in the database.
  • A fingerprint: the server compares them and sends only the key state.
  • A way to change anything: the viewer’s database role can only select.

Know which secrets drifted, without seeing them

env-sync-viewer is self-hosted: you run the collector and the viewer in your own infrastructure. Access to the repository is by request.