It shipped. Someone is watching.

Every deploy of your project is recorded, and the alerts your monitoring sends land on one list. An incident lists the changes most likely behind it, ranked. Turn on the project’s automations and an incident files a task to fix it; set a revert policy and a release that made things worse gets a task to undo it, reviewed like any other change.

From the deploy to the fix for what it broke.

Every deploy, with the changes it shipped.

A project’s Deployments tab shows what is waiting on Dev and what is live on Production: press Deploy to ship the merged changes now, or Schedule… to pick the time. A freeze holds every deploy until it ends, a deploy that needs approval waits for someone else to approve it. You hear when changes are ready to deploy, need approval, go live or fail. Connect the project’s deploys once, from GitHub, GitLab, Bitbucket Pipelines or Azure DevOps, and each run lands on the Deployments page as your pipeline reports it: queued, deploying, succeeded or failed, with the changes it shipped. After each production deploy Jaah runs your health checks from one of your machines, and a failed check opens an incident.

  • Deploy now or on a schedule, with freezes and approvals
  • GitHub, GitLab, Bitbucket and Azure DevOps
  • Health checks after every production deploy
A project’s Production QA tab, switched on: the production environment and deploy workflow, the revert policy set to Draft, the regression window and thresholds, and the health address and smoke command run after each production deploy.

What happened to every change after it merged.

Each change is followed past the merge. The Outcome on the task’s Details tab says how it went, beside what it cost and the security findings it carried.

  • Merged, deployed, still standing, undone or fixed by a later change
  • An incident linked back to the change behind it
  • Tokens and time beside the cost
  • Compared per agent, model and setup in the command center, with agent performance on your plan
  • A setup ranked once its record is long enough to trust

Every incident, with its suspects named.

Start free, connect your deploys and your monitoring, and switch on the incident automations, so the next incident comes with a fix task filed.