Railway bills compute by the second, which is great until your monthly bill is a guess. orkestr is a flat seat price with the resources included, on EU infrastructure.
Last updated
| orkestr | Railway | |
|---|---|---|
| Company | EU company (Romania), EU sub-processors only | Railway Corporation (San Francisco, US) |
| EU regions | Germany, Finland, France | Amsterdam |
| Free tier | Yes: 1 app + Postgres or Redis, sleeps after 30 min idle | $5 one-time trial credit, then Free plan with $1/mo credit (0.5 GB per service) |
| Pricing model | €15/seat/mo, flat. Compute, 2 add-ons and 1 TB bandwidth included | $5 (Hobby) or $20 (Pro) plan fee, includes that much usage, then metered |
| Compute | Included in Pro (up to 0.5 vCPU / 1 GB) | ~$10 per GB RAM and ~$20 per vCPU per month |
| Postgres / Redis | Managed add-ons, included in Pro | Templates, billed as usage (RAM, CPU, volume) |
| Bandwidth | 1 TB on Pro, then €0.10/GB | $0.05/GB egress |
| PR previews | PR preview deploys on every plan | PR environments |
| Crons | Crons + one-off jobs on Pro | Cron jobs |
| Rollbacks | Instant rollbacks on Pro | One-click rollback |
Railway prices from their public pricing pages, last checked . All prices exclude VAT.
Railway prices compute like a utility: per second of RAM and CPU, plus storage and egress. If your services idle near zero, that is genuinely cheap. If they are always on, you pay for the memory every second of the month, and the bill moves with traffic, memory leaks and that one runaway job.
orkestr goes the other way. Pro is €15 per seat and includes the container, two managed add-ons, crons and 1 TB of egress. The number on the invoice is the number on the pricing page, plus clearly listed overages for projects past five, build minutes past 2,000, and bandwidth past 1 TB.
On Railway, Postgres and Redis are templates: containers you deploy and pay for like any other service. On orkestr they are managed add-ons with the connection string injected into your app, private to your project, with backups one toggle away.
Being straight about one gap: orkestr does not have an always-on background worker service today. Queue consumers run inside your web process, or as scheduled and one-off jobs. If your app needs a separate long-running worker, factor that in.
One web app with ~1 GB of RAM, always on. A small managed Postgres, a small managed Redis, a few scheduled jobs, ~100 GB of egress a month, one developer.
Railway in USD, orkestr in EUR, both excl. VAT. Railway's side is our estimate from its published per-unit rates, assuming the services hold their memory all month and use little CPU. Your real Railway bill depends on actual usage: lower if things idle, higher under load. Railway Pro, with unlimited seats, is $20/mo.
We'd rather you pick the right tool than churn in a month. Stay on Railway if:
Spotted something out of date? Tell us at /contact and we'll fix it.
Free to start, no credit card. Keep Railway running while you test, flip DNS when you're happy.