Know which deploy broke your client's site, before they call you.
deployhealth checks every pull request for config your code needs but nobody declared, watches your sites, and ties each outage to the deploy that caused it. Monthly reports your clients can read.

What an alert looks like (live from the demo)
Acme API started failing 4m after deploy b52952e, which introduced 2 missing env vars: REDIS_URL, STRIPE_KEY
Alerts like this go to Slack or Discord.Who it's for
Freelancers and agencies
One page for every client project you maintain.
- A monthly report per client (uptime, incidents, deploys, config issues fixed), with a share link you can send them.
- A handoff doc when the project ends: env vars, endpoints and how to deploy, printable or as Markdown.
Small dev teams
Like Dependabot, but for your .env.example.
- A comment and a check on every pull request that reads an env var nobody declared.
- Strict mode fails the check, so branch protection can block the merge.
- Alerts that name the deploy just before an outage and what it changed.
How it works
- 1
Install the GitHub App
Pull request checks on the repositories you add as projects: a comment and a check, no token or workflow.
- 2
Add your sites
Uptime checks as often as every minute, with alerts to Slack or Discord.
- 3
Optional: add the Action
One workflow step and a repository secret give you deploy history and alerts that name the deploy.
Pricing
Free during the beta: everything you see in the demo.
Planned after the beta
Freelancer
$15/month
Studio
$29/month
Beta users get advance notice and an early-user price.
Questions
Do you see my secrets?
No. deployhealth records variable names and file:line, never values: the Action's scanner runs in your CI and sends names only, and the pull request check keeps names and file:line only. Uptime checks never read response bodies. What we store
Do I have to change my code?
No. deployhealth reads the code and env files you already have. The App and uptime checks need no change to your repository; the optional Action is one workflow step.
What if my stack isn't supported?
Uptime checks, monthly reports and handoffs work for any site, including WordPress. On Rust, C# and other languages we don't read yet, the PR check and CLI report "can't check" instead of passing. Supported today: JS/TS, Python, Go, Ruby, PHP, Java/Kotlin.
What does it cost after the beta?
Free during the beta: everything you see in the demo. After the beta, the planned plans are Freelancer at $15/month and Studio at $29/month. Beta users get advance notice and an early-user price. Pricing
- Your env values never leave your CI: we only see names and file:line. Response bodies are never read. What we store
- Scanner is MIT, 40 KB, zero dependencies. Read it
- Self-hostable. Source on GitHub