Deploy a Flask app

1. Install the CLI and deploy

   From the folder with your Flask app:

   Copy

   curl -fsSL https://aft.page/install | sh
   aft deploy

   aft builds the app, starts it, checks that it answers, and prints the URL. If the build or start fails, it tries a fix up to three times, then tells you in one sentence what broke.

2. Keep it

   A deploy without an account lasts an hour. Claim it to keep the URL, update it with the next aft deploy, and share it.

What aft looks for

A requirements.txt that lists Flask, and app.py, wsgi.py or run.py. It installs your dependencies and starts the app with:

python3 -m flask run --host 0.0.0.0 --port 8080

If the app uses Flask-Migrate, aft runs flask db upgrade before it starts.

Limits

• One process on one port. No background workers, no second service.
• No managed database. Local files and SQLite are temporary and can reset.
• An idle app sleeps after 30 minutes and wakes on the next visit, which can take up to about 20 seconds.
• Beta: full-stack deploys fail more often than static sites. When one does, it says why.

When to use something else

If the app needs a managed database, background workers, several services, or steady production traffic, use Railway, Render or Fly.io. aft is for sharing a working app now.

Other ways in

• No terminal: zip the folder and drop it on aft.page/drop.
• Public GitHub repo: https://aft.page/run/owner/repo.
• From an agent: the remote MCP at https://mcp.aft.page/mcp.

For agents: /deploy/flask.md · all frameworks: /docs/frameworks