Stack detection
Deployxa reads your repository and picks the runtime, build and start commands. Override any of them in project settings.
Deploy Flask microservices and REST APIs with production Gunicorn process management, HTTPS, and health checks.
01 / Quickstart
Install the CLI and deploy the Flask project in your current directory, or connect the repository in the console for push-to-deploy.
$ npm install -g @deployxa/cli$ deployxa login$ deployxa deploy
02 / Guide
Deployxa detects requirements.txt or pyproject.toml and provisions an isolated Python runtime.
Specify your Gunicorn command (e.g. gunicorn -w 4 -b 0.0.0.0:5000 app:app) in Deployxa settings.
Connect managed PostgreSQL; DATABASE_URL is injected into environment.
Health-checked and served over global edge proxy with automated TLS.
03 / Configuration
Set these in project settings. Values are never written to build logs.
| Variable | Purpose | Example |
|---|---|---|
FLASK_ENV | Application runtime environment | production |
SECRET_KEY | Cryptographic session signing secret | sec_... |
DATABASE_URL | PostgreSQL connection string | postgresql://... |
04 / Included
Deployxa reads your repository and picks the runtime, build and start commands. Override any of them in project settings.
Every push builds in its own sandbox with cached dependencies and layers.
Attach PostgreSQL, MySQL or Redis and the connection details are injected as environment variables.
Every deploy gets a deployxa.online URL with a Let's Encrypt certificate; custom domains too.
Traffic only switches to a release that passes its health check, and earlier releases stay available for rollback.
Connect GitHub, GitLab or Bitbucket and each push to your branch ships a new release.
05 / FAQ
WhiteNoise can serve static files directly, or the edge proxy caches them automatically.
Yes, Celery workers can be configured as background worker services.