14 octobre 2026 · Cloud et hébergement · 5 min de lecture
Our Railway vs Render vs Fly.io calculator is one of the more-visited pages on this site, and a few days ago I found out why that mattered more than I'd assumed: it had real pricing bugs. Railway's per-second compute rate was off by 60x, Fly.io's RAM price was tagged per-megabyte instead of per-gigabyte (a roughly 1000x error), and neither Render's April bandwidth repricing nor Fly.io's 2026 free-tier changes for new accounts were reflected anywhere. All three are now corrected against each vendor's own current pricing page, verified October 10. Here's what that correction actually means in dollars, across three workloads I picked to span small, typical, and heavier usage.
Un service, 1 vCPU fonctionnant en continu, 1 Go de RAM, 20 Go de bande passante sortante par mois - le genre de chose que beaucoup de gens tournent pour voir si une idée a des jambes.
| Plate-forme | Coût mensuel | Pourquoi |
|---|---|---|
| Fly.io | $8.16 | Taux par seconde le moins cher, mais bande passante gratuite nulle pour un nouveau compte 2026 |
| Rendre | $9.25 | Forfait de démarrage à plat de 7 $ + dépassement de bande passante de 3,25 $ au-delà de l'allocation gratuite de 5 Go |
| Chemin de fer | $30.02 | $ 20,01 calcul + $ 10,00 RAM, tous deux mesurés à la seconde, pas encore de dépassement de bande passante |
Deux services, 2 Go de RAM chaque charge de travail combinée, 720 vCPU-heures (un vCPU fonctionnant 24 heures sur 24 pour le mois), 50 Go de bande passante.
| Plate-forme | Coût mensuel | Pourquoi |
|---|---|---|
| Fly.io | $14.76 | $ 1,76 calcul + $ 12,01 RAM + $ 1,00 bande passante (50 Go × $ 0,02) |
| Rendre | $20.75 | $ 14 flat (2 services × $ 7) + $ 6.75 dépassement de bande passante |
| Chemin de fer | $40.02 | $ 20.01 calcul + $ 20.01 RAM, toujours sous la ligne de bande passante libre de 100 Go |
Trois services, 4 vCPU fonctionnant en continu combinés, 8 Go de RAM, 300 Go de bande passante - plus proche d'une petite application de production avec un trafic réel.
| Plate-forme | Coût mensuel | Pourquoi |
|---|---|---|
| Fly.io | $61.05 | $ 7,03 calcul + $ 48,02 RAM + $ 6,00 bande passante (300 Go × $ 0,02) |
| Rendre | $65.25 | $ 21 flat (3 services × $ 7) + $ 44,25 dépassement de bande passante (295 Go × $ 0,15) |
| Chemin de fer | $170.08 | $ 80,03 calcul + $ 80,03 RAM + $ 10,00 dépassement de bande passante (200 Go × $ 0,05) |
Fly.io wins on raw unit economics every single time I ran the numbers, and the gap widens with scale -- it's barely ahead of Render at the solo-project size and more than $4/mo cheaper by the heavier scenario, mostly because its RAM rate is roughly a third of Railway's. Railway is consistently the most expensive of the three because it charges the highest per-second rate for both compute and RAM, with no flat-rate ceiling the way Render has. Render sits in the middle in every scenario, and its appeal isn't the number itself -- it's that the number is a flat $7/service regardless of how efficiently your code runs, which matters if you'd rather budget in advance than get a usage-dependent bill.
This is the part that actually changes a decision, not just a bill. Fly.io built its reputation on a genuinely generous free allowance -- roughly 160GB/mo of bandwidth, among other things -- and that reputation still shows up constantly in forum threads and "best free hosting" lists. It no longer applies to anyone signing up today. That allowance is legacy-accounts-only, grandfathered in for organizations created before October 2024; a new account in 2026 gets a short trial and then pays from the first gigabyte. Meanwhile Render, after cutting its own free bandwidth 20x in the April 2026 repricing (100GB down to 5GB), is now the only one of the three that still gives a brand-new account an ongoing free tier at all -- 750 instance-hours a month, enough to run one service continuously for free. Railway never had an ongoing free tier in the way people mean it; it's a one-time $5 trial credit, and once that's spent, billing starts regardless of how light the usage is.
If I were starting something today with no revenue yet, I'd put it on Render for the free 750 hours and not think about billing until it matters. Once a project is actually running with any real traffic, the per-second platforms pull ahead, and between those two Fly.io's lower RAM rate makes it the one worth pricing first -- just budget for bandwidth and compute from day one, since the "it's free" assumption about Fly no longer holds for a new signup. Run your own numbers through the calculator rather than trusting any of these three scenarios directly; service count, RAM per service, and bandwidth are the three inputs that move the ranking the most.
Vous débutez dans la tarification de l'accueil de voyageurs basée sur l'utilisation ? Commencez guides gratuits sur les coûts des API.
Déployez-le vous-même : DigitalOcean — 200 $ de crédit gratuit ↗ · VPS Hostinger ↗
Tarifs provenant directement de railway.com/pricing, render.com/pricing et docs.fly.io/about/pricing, vérifiés en 2026-10-10. Chiffres de référence, pas de devis en direct — les modèles d'utilisation exacts et la sélection de la région déplacent la facture réelle ; confirmez les conditions actuelles directement avec chaque fournisseur avant de budgétiser.