Run a containerized app or API on a free web service. Use your onrender.com URL or your own domain, with TLS included. No credit card required.
Each instance has a fixed monthly price, prorated by the second.
Capability | Render | |||
|---|---|---|---|---|
How containers run | Long-running services from Dockerfiles or images | Long-running containers | Container images on dynos | Fly Machines from Dockerfiles or images |
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 | $1 trial credit for 7 days. No ongoing free tier |
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 |
Persistent storage | SSD disks that grow without downtime. Single instance | Volumes. Hobby limit: 5 GB | Ephemeral filesystem. Use external storage | Local volumes. Replication is your responsibility |
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 |
Autoscaling | CPU or memory, Pro and up. No attached disk | Manual replicas. Vertical up to plan limits | Cedar Performance, Private and Shield web dynos | Proxy autostart, or a self-run autoscaler |
Competitor details as of November 2026. Instance prices are compute only. CPU types and memory allocations differ. Fly.io prices are for US East and 30 days.
Render runs your containers. You maintain the image and its dependencies. Define every service and database in one render.yaml Blueprint.
Traffic moves once the new container is ready, and failed builds leave the live one running. Roll back to an available image. Services with a persistent disk see a few seconds of downtime.
Services and databases in the same workspace and region talk over a private network. Run internal APIs as private services with no public URL.
Connection pooling and point-in-time recovery on paid instances. Read replicas and high availability on larger ones.
Redis-compatible storage for caching, sessions, and job queues.
Process queues in background workers. Run scheduled container tasks as cron jobs, billed by the second.
Scale out automatically on CPU or memory. Pro and up. Not available for services with a persistent disk.
Pick a GitHub, GitLab, or Bitbucket repo with a Dockerfile, and a branch.


Select Docker, set the Dockerfile path, and add environment variables.
Every commit to your branch builds and deploys automatically, or only after CI checks pass.

