Home › Blog › Railway vs Render vs Fly.io drei echte Rechnungen

Railway vs Render vs Fly.io: Three Real Hosting Bills, Oktober 2026

14. Oktober 2026 · Cloud & Hosting · 5 Minuten Lesezeit

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.

Szenario 1: ein Solo-Nebenprojekt

Ein Dienst, 1 kontinuierlich laufende vCPU, 1 GB RAM, 20 GB ausgehende Bandbreite pro Monat - das ist die Art von Dingen, die viele Leute aufdrehen, um zu sehen, ob eine Idee Beine hat.

PlattformMonatliche KostenWarum
Fly.io$8.16Günstigste Rate pro Sekunde, aber keine freie Bandbreite für ein neues 2026-Konto
Machen$9.25$ 7 Flat Starter Plan + $ 3,25 Bandbreitenüberschreitung über den 5 GB Freibetrag hinaus
Eisenbahn$30.02$ 20,01 Compute + $ 10,00 RAM, beide sekundengenau dosiert, noch keine Bandbreitenüberschreitung

Szenario 2: eine typische Zwei-Service-API (Standard unseres Rechners)

Zwei Dienste, 2 GB RAM pro Workload kombiniert, 720 vCPU-Stunden (eine vCPU läuft rund um die Uhr für den Monat), 50 GB Bandbreite.

PlattformMonatliche KostenWarum
Fly.io$14.76$ 1.76 Compute + $ 12.01 RAM + $ 1.00 Bandbreite (50GB × $ 0.02)
Machen$20.75$ 14 Flat (2 Services × $ 7) + $ 6,75 Bandbreitenüberschreitung
Eisenbahn$40.02$ 20,01 Compute + $ 20,01 RAM, immer noch unter der 100 GB freien Bandbreitenleitung

Szenario 3: ein schwererer Drei-Service-Stack

Drei Dienste, 4 kontinuierlich kombinierte vCPUs, 8 GB RAM, 300 GB Bandbreite - näher an einer kleinen Produktions-App mit echtem Datenverkehr.

PlattformMonatliche KostenWarum
Fly.io$61.05$ 7,03 Compute + $ 48,02 RAM + $ 6,00 Bandbreite (300 GB × $ 0,02)
Machen$65.25$ 21 Flat (3 Services × $ 7) + $ 44,25 Bandbreitenüberschreitung (295 GB × $ 0,15)
Eisenbahn$170.08$ 80.03 Compute + $ 80.03 RAM + $ 10.00 Bandbreitenüberschreitung (200GB × $ 0,05)

Das Muster, das für alle drei gilt

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.

Die Free-Tier-Reputationslücke

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.

Was ich eigentlich wählen würde

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.

Neu bei nutzungsbasierten Hosting-Preisen? Beginnen Sie mit der kostenlose API-Kostenleitfäden.

Stellen Sie es selbst bereit: DigitalOcean – 200 $ kostenloses Guthaben ↗ - Hostinger VPS ↗

Die Preise stammen direkt von railway.com/pricing, render.com/pricing und docs.fly.io/about/pricing, verifiziert 2026-10-10. Referenzzahlen, keine Live-Angebote — genaue Nutzungsmuster und Regionsauswahl verschieben die reale Rechnung; aktuelle Konditionen direkt mit jedem Anbieter vor der Budgetierung bestätigen.