Both names show up in the same infrastructure search, but one of them bills you for requests and the other bills you for seconds.
TL;DR
Cloudflare sells a network with compute attached: DNS, CDN, WAF, Workers and Containers on plans priced at $0, $20 and $200 a month billed annually, plus per-request charges for Functions. Railway sells compute with a visual canvas: a $5 Hobby floor and a $20 Pro floor, then per-second billing for CPU, memory and volumes and $0.05 per GB of egress. Buy Cloudflare when the audience is the internet at large and latency, caching and protection matter; buy Railway when you want a service or database running without touching network plumbing.
Cloudflare's pricing page runs a Free plan at $0 for personal or hobby projects, Pro at $20 per month billed annually ($25 paid monthly), Business at $200 per month billed annually ($250 monthly), and a Contract tier for mission-critical applications. The compute layer is priced underneath that: Functions charge $0.30 per million requests above a free allowance of 100,000 requests a day, with CPU time at $0.02 per million CPU-milliseconds. Containers charge for what runs: memory at $0.0000025 per GiB-second, CPU at $0.000020 per vCPU-second, disk at $0.00000007 per GB-second, and egress in North America and Europe with the first terabyte included and $0.025 per GB after it. The security side has its own meter, with the SSE product free for teams under 50 users and $7 per user per month above that.
Railway has no plan ladder in the usual sense. Its pricing page lists Free at $0, introduced with a 30-day trial carrying $5 of credits, Hobby at a $5 minimum that includes $5 of monthly usage credits, and Pro at a $20 minimum that includes $20 of credits. Everything above the floor is metered: memory at $0.00000386 per GB-second, CPU at $0.00000772 per vCPU-second, volumes at $0.00000006 per GB-second and egress at $0.05 per GB for services, with object storage at $0.015 per GB-month and free egress. Isolated Linux machines for agents carry their own rates, about $50 per GB-month and about $50 per vCPU-month while running, and a service can scale to 50 replicas at up to 48 vCPU and 48 GB each before sales gets involved.
| Feature | Cloudflare | Railway |
|---|---|---|
| Free tier | Free: $0, hobby projects, 100,000 Function requests a day | Free: $0, with a 30-day trial carrying $5 of usage credits |
| Entry paid plan | Pro: $20/month billed annually, $25 paid monthly | Hobby: $5 minimum usage, including $5 of monthly credits |
| Mid tier | Business: $200/month billed annually, $250 paid monthly | Pro: $20 minimum usage, including $20 of monthly credits |
| Enterprise | Contract tier quoted for mission-critical applications | Contact sales above 50 replicas per service at 48 vCPU and 48 GB |
| Compute pricing | Functions: $0.30 per million requests, $0.02 per million CPU-ms; Containers: $0.0000025 per GiB-second memory, $0.000020 per vCPU-second | Memory $0.00000386 per GB-second, CPU $0.00000772 per vCPU-second, volumes $0.00000006 per GB-second |
| Egress | 1 TB included in North America and Europe on Containers, then $0.025 per GB | $0.05 per GB for services; object storage $0.015 per GB-month with free egress |
| Storage | Object and KV products billed as separate line items | Volumes billed per GB-second, object storage billed per GB-month |
| Network services | DNS, CDN, WAF and certificate handling included in the plan | Managed networking, private services and previews built into the platform |
| Platform | Edge network with dashboards, API and Terraform support | Web console with a visual canvas, CLI, API and GitHub deploys |
| Offline mode | Not a concept for a hosted network service | Not a concept for a hosted compute service |
| Billing note | Plan fee plus metered usage on compute | Usage floor plus metered seconds, no plan fee above the floor |
Pick Cloudflare if
Sites and APIs that face the open internet get caching, WAF rules, DNS and certificate handling wrapped around the code for $20 a month billed annually on Pro, with Functions priced at $0.30 per million requests. It is the choice when traffic is public, spiky and geographically spread, and when protection is part of the requirement rather than an add-on.
Pick Railway if
Backends, workers, staging environments and agent sandboxes run on per-second billing with a $20 floor that includes matching credits, and the canvas replaces a lot of configuration. It is the choice when you want to deploy a container or a database tonight and do not need a content network in front of it.
We collected no independent reviews for this pairing: every number here comes from cloudflare.com and railway.app pricing pages, and the cards hold vendor-published statements rather than measured user opinion.
Railway will run the service and expose it publicly, but it does not ship a CDN, a WAF or a DNS network. Teams that need edge caching and bot protection still buy those from Cloudflare or an equivalent, even when the application itself runs on Railway.
Cloudflare's Functions and Containers can run code and containerised workloads, priced per request and per second of CPU. What it does not hand you is Railway's one-canvas view of services, volumes, private networking and managed databases, which is where Railway's floor of $20 a month with matching credits is aimed.
At the bottom, Cloudflare's Free plan costs $0 and includes 100,000 Function requests a day, while Railway opens with a 30-day trial carrying $5 of credits and then a $5 Hobby floor. For a small static site with light compute, the free network tier usually wins; for a small container or database, Railway's floor is the cheaper path.
Railway charges $0.05 per GB of egress for services and $0.015 per GB-month for object storage with free egress. Cloudflare's Containers include the first terabyte in North America and Europe at $0.025 per GB after it, while the CDN and caching products are covered by the plan fee.
Not for Railway: services, volumes and private links are drawn on a canvas and the platform handles certificates and routing. Cloudflare assumes you are configuring zones, rules and caches, which is powerful but means the DNS and security setup is your job.
Spot an outdated price or feature? Let us know and we'll verify it.