PostDeploy: errors, logs and release context
Errors, logs and the release that was live, in one place, so a fix starts from evidence. We build and run it.
Screens
See what broke, the logs around it and the release that was live, on one screen. 
Know which errors are hitting the release you just shipped, and how often. 
Check what broke from your phone, down to the line of code.
How it works
Change one DSN
Point your Sentry SDK at a PostDeploy DSN. Node.js sends errors and logs; Python, Ruby and Elixir send errors. To leave, change the DSN back.
Connect your agent
Add the PostDeploy MCP server to your coding agent and approve it in the browser. A new connection can only read, with the scopes you grant, and you can revoke it from the dashboard.
Record deployments from CI
One HTTP call per deploy. Your agent can then compare error rates before and after each release.
Ask what broke
Your agent lists the open issues and reads each error together with its logs and the release that was live, so it works from the evidence in production.
Try it
The 14-day trial needs no payment card; current plans are on postdeploy.dev. The source is published under AGPL-3.0. PostDeploy uses the Sentry SDK and is not affiliated with Sentry.