Deploy Flask on Deployxa.

Deploy Flask microservices and REST APIs with production Gunicorn process management, HTTPS, and health checks.

All frameworks

01 / Quickstart

Deploy from your terminal.

Install the CLI and deploy the Flask project in your current directory, or connect the repository in the console for push-to-deploy.

  • Typical database: PostgreSQL with SQLAlchemy
  • Build and start commands can be overridden
  • Secrets stay out of build logs
deploy · flask
$ npm install -g @deployxa/cli$ deployxa login$ deployxa deploy

02 / Guide

How Flask goes to production.

  1. 01 /

    Connect the repository

    Deployxa detects requirements.txt or pyproject.toml and provisions an isolated Python runtime.

  2. 02 /

    Configure WSGI entrypoint

    Specify your Gunicorn command (e.g. gunicorn -w 4 -b 0.0.0.0:5000 app:app) in Deployxa settings.

  3. 03 /

    Attach database

    Connect managed PostgreSQL; DATABASE_URL is injected into environment.

  4. 04 /

    Promote

    Health-checked and served over global edge proxy with automated TLS.

03 / Configuration

Environment variables.

Set these in project settings. Values are never written to build logs.

Recommended environment variables for Flask
VariablePurposeExample
FLASK_ENVApplication runtime environmentproduction
SECRET_KEYCryptographic session signing secretsec_...
DATABASE_URLPostgreSQL connection stringpostgresql://...

04 / Included

What every deploy gets.

  • Stack detection

    Deployxa reads your repository and picks the runtime, build and start commands. Override any of them in project settings.

  • Isolated builds

    Every push builds in its own sandbox with cached dependencies and layers.

  • Managed databases

    Attach PostgreSQL, MySQL or Redis and the connection details are injected as environment variables.

  • HTTPS by default

    Every deploy gets a deployxa.online URL with a Let's Encrypt certificate; custom domains too.

  • Health-checked releases

    Traffic only switches to a release that passes its health check, and earlier releases stay available for rollback.

  • Push to deploy

    Connect GitHub, GitLab or Bitbucket and each push to your branch ships a new release.

05 / FAQ

Flask questions.

How is static content served?

WhiteNoise can serve static files directly, or the edge proxy caches them automatically.

Can I run background Celery tasks?

Yes, Celery workers can be configured as background worker services.

Ready when you are

Ship your Flask app.

Connect a repository and get a live HTTPS URL.

See pricing