Test a Rails web app on a free instance with a public URL and managed TLS. Connect free Postgres for a temporary development database.
Each instance has a fixed monthly price, prorated by the second.
Capability | Render | |||
|---|---|---|---|---|
How Ruby on Rails runs | Native Ruby 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 |
Sidekiq workers and cron | Workers and cron jobs | Workers and cron jobs | Worker dynos and Scheduler | Process groups. Cron via Supercronic |
Migrations before deploy | Pre-deploy command on paid instances | Pre-deploy command | Release phase | release_command in fly.toml |
WebSockets | Yes, no maximum duration | Yes, no maximum duration | Yes, closes after 55s idle | Yes, through Fly Proxy |
Competitor details as of November 2026. Instance prices are compute only. Fly.io prices are for US East.
Run Rails on the native Ruby runtime or in Docker. Define your services and databases in one render.yaml Blueprint.
Set the Ruby version your app and gems support. Commit your dependency lockfile so builds use the dependencies you tested.
Connect Rails to Render Postgres over the private network. Choose database capacity and recovery settings separately from web compute.
Run Sidekiq or your chosen job processor as a background worker. Keep the web process focused on requests, with worker compute billed separately.
Configure health checks for web readiness and plan compatible database migrations. Disk-backed services have a few seconds of deploy downtime.
Use external object storage for Active Storage uploads, or a paid disk for a single-instance service. A code rollback does not restore database or uploaded-file state.
Add instances for stateless Rails web traffic 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 Ruby and configure your build script, server command, database connection, and Rails secrets. Follow the Rails guide for asset compilation and database setup.
Render builds your app and publishes its URL. Every later commit to your branch deploys automatically, or only after CI checks pass.

