Release visibility
Every environment. One grid.
Envgrid shows which commit is running in every environment of every service you ship — and exactly what would go out if you deployed right now.
Two services free, no card. Envgrid is strictly read-only — it observes deployments and never triggers one.
| dev | qa | staging | prod | |
|---|---|---|---|---|
| checkout-api | 2.14.0 a3f9c21 | 2.14.0 a3f9c21 | 2.14.0 a3f9c21 | 2.14.0 a3f9c21 |
| payments | 1.8.2 7c1de04 | 1.8.2 7c1de04 | 1.8.2 7c1de04 +12 | 1.8.0 9b2aa51 |
| notifications | 4.0.1 e17b3d9 | 4.0.1 e17b3d9 | 3.9.4 1d05f7c | 3.7.0 c40f8a2 stale |
| search-index | 0.9.6 2fd8b10 | — | 0.9.5 5ae3c88 | 0.9.5 5ae3c88 |
Cells are coloured by commit, never by version label — two environments showing v2.14.0 are only the same colour if they are the same commit. A row of one colour is a finished rollout; anything else is a version still on its way.
Three questions, one screen each
What would ship if I deploy now?
A live diff between any two environments, with commits grouped under the Jira tickets they mention. Ten thousand commits are often three hundred tickets — and three hundred tickets is readable.
What did we ship, and when?
An immutable timeline of production deploys, each carrying the changelog frozen at the moment it went out — commits, tickets, who, and when. Exportable as Markdown.
Will we ship what we planned?
Compare a release plan against the pending diff before you deploy: what is ready, what is planned but missing, and what is about to ship that nobody planned.
It never touches your cluster
Envgrid holds no runtime credentials and needs no access into your infrastructure. Kubernetes, ECS, Nomad, bare metal — where you deploy is irrelevant to it. Something just has to tell it that a commit reached an environment, and the pipeline that deployed it already knows the one thing a running container does not: the git SHA.
at the end of the job that already deploys
curl -X POST https://envgrid.dev/api/ingest/deploy \
-H "X-Webhook-Secret: $ENVGRID_SECRET" \
-d "{\"service\":\"payments\",
\"environment\":\"prod\",
\"sha\":\"$(git rev-parse HEAD)\"}"Works from GitHub Actions, GitLab CI, Jenkins, Tekton, ArgoCD or a terminal. Envgrid generates the snippet for your CI system with the success guard already in it.
What that actually proves
A webhook is an assertion by whoever holds the secret: this commit reached this environment at this time. It does not prove the deploy succeeded, or that it is still running now.
So Envgrid puts the timestamp beside the version everywhere, and flags an environment nobody has deployed to in weeks as stale. An old claim should invite suspicion — prod · v2.14.0 · 6 weeks ago tells you something a bare version label hides.
Pricing
Billed per organization, by the number of services you track. Everyone on your team reads the grid — you are never charged per seat.
Free
$0
Up to 2 services
Unlimited members
Basic
$15 /mo + tax
Up to 10 services
Unlimited members
Advanced
$35 /mo + tax
Up to 30 services
Unlimited members
Downgrading archives the services past your limit rather than deleting them — the deployment history stays intact underneath and returns whenever you reactivate. Payments and invoicing are handled by Paddle, who act as the merchant of record.
Put every environment on one board
Connect a repository, declare your environments, and point your pipeline at one URL.
Start free