Hosting for Ruby on Rails: what 8 makers' products chose
Among 8 makers' products built with Ruby on Rails that we know the hosting of, Netlify leads: 2 of them (25%). Next come Heroku (2) and Vercel (1).
What shape is your app? A frontend or serverless app fits a frontend cloud. Long-running servers, background workers and databases fit a PaaS or container platform. A hyperscaler cloud has every building block but leaves you to assemble them; a platform or framework that deploys into your own cloud account sits between, with platform-style deploys and the resources on your own cloud bill.
What makers on Ruby on Rails chose
| Option | Ruby on Rails products | All makers | Free for | Team of 5, 10,000 users |
|---|---|---|---|---|
| 2 (25%) | 7% | None | $30/moPro 3,000 credits | |
| 2 (25%) | 1% | — | — | |
| 1 (13%) | 57% | None | $120/moPro + Flat Rate CDN 10M | |
| 1 (13%) | 3% | None | $45/moPro | |
| 1 (13%) | 4% | None | $61/moPro | |
| 1 (13%) | 4% | — | — | |
| 1 (13%) | 3% | None | $13/moCPX12 |
Live makers' products with a source for both: that they're built with Ruby on Rails, and what they use for hosting. A product using two options counts in both; not market share. "All makers" is the option's share among every maker's product that made this decision.
Costs are the cheapest plan that fits, from each vendor's pricing page, at the usage our stack planner assumes for a product with that many users. Free for: the users its cheapest plan a business can use stays free for; plans for personal use only, like a non-commercial hobby tier, don't count.
Which to pick, by situation
- You built a Next.js or other frontend-heavy app and want preview URLs on every pull request
Vercel 1 here
Netlify 2 here - You have a long-running server, a background worker and a database to deploy together
Railway 1 here
Render 1 here - You want a flat monthly bill and full control, and don't mind running one server
Hetzner Cloud 1 here
Netlify
Frontend cloud2 Ruby on Rails products here (25%). About $30 a month for a team of 5 with 10,000 users (Pro 3,000 credits).
llms.txtIn BoltBest forStatic sites and JAMstack apps on any framework.
Trade-offServer-side features run as functions with time limits; long-running work needs another host.
- Connecting a GitHub repo gives automatic builds and deploys on every commit. 3 sources
- The free tier covers low-traffic static sites. 3 sources
- Free-tier sites get paused at usage limits, and large surprise bills have happened. 3 sources
- Price increases and weak bot-traffic protection push small customers to look elsewhere. 2 sources
Status page: 15 incidents in the last 90 days, 4 major (its own page, 2026-10-19).
Heroku
PaaS2 Ruby on Rails products here (25%).
llms.txtCLIBest forA long-established git-push platform with managed Postgres, Redis and a large add-on marketplace.
Trade-offNo free tier, and since March 2026 Heroku runs as a sustaining-engineering platform focused on stability rather than new features.
“The site is hosted on Heroku , as it takes the headache of server configuration and scaling, so I can focus on developing and running the business.”
“The site is hosted on Heroku , as it takes the headache of server configuration and scaling, so I can focus on developing and running the business.”
HostingMaker says so · source ↗“Heroku has made our build and deploy process really simple.”
HostingMaker says so · source ↗Also chosen, and not seen yet
Fewer Ruby on Rails products here: Vercel (1), Railway (1), Render (1), DigitalOcean (1), Hetzner Cloud (1).
Real options for hosting not seen among these Ruby on Rails products yet: Cloudflare, Fly.io, Amazon Web Services, Coolify.
Who switches, and to what
Public GitHub pull requests whose title says "X to Y", by developers in general, not only on Ruby on Rails.
- Vercel → Render 123 pull requests · how they moved
- Netlify → Vercel 117 pull requests · how they moved
- Vercel → Railway 94 pull requests · how they moved
- Vercel → Netlify 65 pull requests · how they moved
- Render → Vercel 61 pull requests · how they moved
- Railway → Render 57 pull requests · how they moved
Getting hosting right
Connect the repo so every push deploys and every pull request gets a preview URL. Put secrets in the platform's environment variables, never in the repo.
- Leaving a paid platform on its default autoscaling and spend limits, so one viral day or a bot crawl turns into a surprise invoice.
- Putting a long-running job, websocket or large upload behind a serverless function and hitting its time or size limit in production.
- Keeping the database on a different provider or region from the app, so every query crosses the internet and pages get slow.
The rest of the Ruby on Rails stack
What makers' Ruby on Rails products chose for their other decisions, the most common pick for each:
- Transactional Email: Postmark 6 of 11
Questions
What do most Ruby on Rails apps use for hosting?
Among 8 makers' products built with Ruby on Rails that we know the hosting of, Netlify leads: 2 of them (25%). Next come Heroku (2) and Vercel (1).
What does hosting cost for a Ruby on Rails app with 10,000 users?
On our usage model for a team of 5 with 10,000 users, Netlify comes to about $30 a month (Pro 3,000 credits); Vercel comes to about $120 a month (Pro + Flat Rate CDN 10M); Railway comes to about $45 a month (Pro); Render comes to about $61 a month (Pro). Prices are from each vendor's pricing page.
How this is counted: a product is on Ruby on Rails when a live-product source says so (the maker, its website, a customer story or a subprocessor list), and the same for its hosting. How evidence is collected.