Try a Python web app on a free instance with a public URL, custom domains, and managed TLS. Choose a production server for your framework, then connect your repo.
Each instance has a fixed monthly price, prorated by the second.
Capability | Render | |||
|---|---|---|---|---|
How Python runs | Native Python 3 web service or Docker | Long-running container | Web dyno | Fly Machine built from a Dockerfile |
Free tier | 750 free hours/month. Spins down after 15 min idle | $5 trial for 30 days, then $1/month credit | None. Eco: $5/month for 1,000 hours | No free tier. Personal bills under $5 waived |
Always-on, 2 GB | $25/month (1 CPU) | Up to $40/month at full use (1 vCPU) | $250/month (Performance-M, 2.5 GB dedicated) | $13.39/month shared CPU, $33 dedicated |
Managed Postgres and Redis | Postgres from $6 with PITR, plus Key Value | Maintained databases. HA and Postgres PITR opt-in | Postgres and Key-Value. No rollback on Essential | Managed Postgres from $38, HA included. Upstash Redis |
Background workers | Workers and cron jobs | Workers and cron jobs | Worker dynos and Scheduler | Process groups. Cron via Supercronic |
Stack as code | One render.yaml, auto-synced on push | Project file, applied with CLI or CI | app.json per app, read only at creation | fly.toml per app. No database definitions |
Autoscaling | Scales on CPU or memory, Pro plan and up | Manual replicas. Vertical up to plan limits | Performance, Private and Shield dynos only | Proxy autostart, or a self-run autoscaler |
Competitor details as of November 2026. Instance prices are compute only. Fly.io prices are for US East.
Run Python on the native runtime or in Docker. Define your services and databases in one render.yaml Blueprint.
Set the Python version and dependency versions your app expects. Choose Docker if you need to control the operating system or additional packages.
Connect your app to Render Postgres using its internal URL. Keep the web service and database in the same workspace and region.
Run Celery or another queue consumer as a background worker. Give long-running work its own compute instead of keeping an HTTP request open.
Configure an HTTP health check so Render can check application readiness. Stateless web services support zero-downtime deploys.
Set API keys and database credentials as environment variables or secret files. Keep local development values out of source control.
Scale stateless services across instances as demand grows. Autoscaling is available on Pro and up, and each instance is billed separately.
Pick a GitHub, GitLab, or Bitbucket repo and branch.


Choose Python 3, set dependency installation and start commands, and add your environment variables. Bind the web server to 0.0.0.0 and use the port in PORT.
Render builds your app and publishes its URL. Every later commit to your branch deploys automatically, or only after CI checks pass.

