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

DeployAngel Beta

Verify every Flask deploy in production

DeployAngel compares each Flask release with your last healthy one, using real production traffic: error rate, p95 latency, exceptions, and Celery or RQ jobs, app-wide and per route and task. Then it clears the release or fails it, with the evidence, and tells you, your CI, or your coding agent when it's safe to stop watching. Setup is one package, one line of code, and one environment variable.

Requires Python 3.10 or later and Flask 2.3 or later. The package has no dependencies of its own.

1. Install the agent

Create an account and an app, then create its app token from the setup checklist. Then add the agent:

Add the package to your requirements:

pip install deployangel

and call init_app where the app is created, in your app factory if you use one:

import deployangel.flask
from flask import Flask

app = Flask(__name__)
deployangel.flask.init_app(app)

It reports when app.debug is off, or set DEPLOYANGEL_ENVIRONMENT to name the environment yourself.

2. Set the token

Set the app token as DEPLOYANGEL_TOKEN in production, on every process: web servers and job workers alike. On Heroku, the DeployAngel add-on sets it for you.

The agent finds the release it's running by itself on Heroku (with dyno metadata enabled), Kamal, Render, Fly.io, Railway, Coolify, Dokku, ECS, and servers deployed from a git checkout. In other Docker deploys, bake the commit into the image: deployangel install docker adds ARG GIT_SHA and ENV DEPLOYANGEL_REVISION=$GIT_SHA to your Dockerfile, and you build with --build-arg GIT_SHA=$(git rev-parse HEAD). Set it up for how you deploy has the steps for each host.

3. Check the setup

Once it's deployed, run:

deployangel doctor

It checks your checkout and what DeployAngel has seen so far: which processes report and the release each runs, the routes, jobs, and scheduled jobs the agent found, and any setup problem, such as a worker that isn't running the agent, with what to do about it.

The first day is a warm-up. For an app's first 24 hours of telemetry, DeployAngel learns what's normal for it. Deploys during that time are still checked, and you'll hear right away if one fails, but they can't be cleared. Installing the agent a day before a deploy you care about means that deploy can be cleared.

What the Flask agent records

The privacy policy lists exactly what's collected. If DeployAngel is ever unreachable, your app keeps running normally, and the agent sends up to an hour of telemetry once it's back.

4. Wait for the verdict in CI or a coding agent

Each release is compared with your last healthy one for at least 15 minutes. A busy app usually clears in about that time; a quiet one can take longer, or run a smoke test after each deploy. With a "CI deploys" or "CLI & coding agents" token in DEPLOYANGEL_API_TOKEN, the CLI waits for the verdict and exits with a code a pipeline can act on:

deployangel verify --wait --until=initial

To give Claude Code, Cursor, and Codex the same verdicts through DeployAngel's read-only MCP server, run this in the project:

deployangel install agents

The CLI reference lists every command and exit code, and set up your coding agent covers the MCP server.

Flask troubleshooting

Start with deployangel doctor: it names most setup problems and what to do about each.

The app page says "Agent hasn't reported yet"

Check that deployangel.flask.init_app(app) runs where the app is created, that DEPLOYANGEL_TOKEN is set on every process, including Celery and RQ workers, and that the app can reach https://api.deployangel.com. The agent doesn't report when app.debug is on; DEPLOYANGEL_ENABLED=true forces it on.

My health check is somewhere else

List its route the way the dashboard shows it, before init_app, and HEAD requests to it are left out too:

import deployangel

deployangel.configure(ignored_routes=["GET /status"])

Under uWSGI, nothing reports

The agent sends from a background thread, and uWSGI doesn't run threads unless you ask. Set enable-threads = true.

Exceptions point at the wrong files

File paths are relative to the working directory, which on Heroku and in most containers is the repository's root. If your processes start somewhere else, set DEPLOYANGEL_ROOT to the repository's root.

RQ jobs don't show up

RQ runs each job in a forked process that exits as soon as the job ends, so DeployAngel's worker class records each job after it finishes. Start workers with rq worker -w deployangel.rq.Worker (or deployangel.rq.SimpleWorker).

"Not cleared: this release never reported"

No process reported the registered release within 15 minutes. If another release kept running, the rollout failed or was rolled back. Otherwise the new version may never have started (check the boot logs, for example for a failed migration), or CI registered a different commit from the one the app runs. Register the commit that was built and deployed, after the deploy finishes.

More

Still stuck? Contact us.