Beta DeployAngel is in beta. Every feature is free while it lasts, with no credit card. What beta means →

DeployAngel Beta

Demo

A release fails without a single error, and its fix clears

A shop app, sending synthetic traffic, judged by DeployAngel's real engine. Each step links to the release page the engine produced, saved as it looked a day later.

  1. 1

    v182 ships, and nothing looks wrong

    v182 changes app/models/order.rb and upgrades dependencies. Every request keeps succeeding, nothing new is raised, and the job that sends receipts keeps running without a failure. An error tracker would have nothing to show.

    HTTP 5xx rate
    0.13% → 0.00%
    New exceptions
    None
    SendReceiptJob
    33 runs, 0 failures
  2. 2

    DeployAngel fails it 5 minutes after rollout

    The shop calls DeployAngel.checkpoint("receipt.sent") each time a receipt goes out. From the releases before, about 36 were expected in v182's first minutes. None came, while order.created held at 36, so people were still placing orders.

    The evidence, from fixed rules

    ✕ Failed v182 failed: receipt.sent events dropped

    SignalBeforeAfter
    receipt.sent~36 expected0Failing
    order.created~36 expected36Pass

    20 signals compared with v181: 1 failing, 17 passing, and 2 without enough data yet.

    Your coding agent's reading

    An inference from the evidence. It never decides the verdict.

    Nothing errored, but receipts stopped. SendReceiptJob still runs and succeeds, so it's likely returning before it sends. order.rb changed in v182, and the job reads the order's state, so I'll start there. Roll back to v181 first?

    Open v182's release page →
  3. 3

    v183 fixes it, and DeployAngel confirms it from production

    The release after a failure checks each earlier problem against its own traffic, so the fix is confirmed by receipts actually going out, not by a passing test. v183 sent 180 against about 180 expected, and cleared 17 minutes after rollout.

    v183 fixes the problem from v182: it's healthy again

    ✓ Checkpoint on receipt.sent: 0 in v182, 180 in v183

    The clearance still says what it didn't see. The password_reset critical flow hadn't run since the deploy, so the report lists it rather than counting it as covered.

    Open v183's release page →

See it on your own app, without waiting for a bad deploy

After about an hour of your app's traffic, a fire drill stages a failed release on it, judged by the same rules against your real baseline, so you see the page and the alert a real failure gets. Nothing is deployed, and no traffic is sent to your app.

Checks like the 5xx rate, latency, exceptions, and scheduled jobs work as soon as the agent reports. A checkpoint like receipt.sent is one line, wherever your app does something that should keep happening.