Heroku made git push deploys normal. orkestr keeps that workflow, drops the per-dyno and per-add-on pricing, and runs everything in the EU.
Last updated
| orkestr | Heroku | |
|---|---|---|
| Company | EU company (Romania), EU sub-processors only | Salesforce, Inc. (San Francisco, US) |
| EU regions | Germany, Finland, France | "Europe" on Common Runtime; Dublin, Frankfurt, London on Private Spaces |
| Free tier | Yes: 1 app + Postgres or Redis, sleeps after 30 min idle | None. Eco is $5/mo for a shared 1,000-hour pool, sleeps after 30 min |
| Pricing model | €15/seat/mo, flat. Compute, 2 add-ons and 1 TB bandwidth included | Per dyno + per add-on |
| Always-on 1 GB app | Included in Pro | $50/mo (Standard-2X) |
| Postgres | Included in Pro (512 MB RAM) | From $5/mo (Essential-0, 1 GB storage) |
| Redis | Included in Pro (256 MB RAM) | From $3/mo (mini, 25 MB, no persistence) |
| Docker | Dockerfile or auto-detected framework | Buildpacks by default, Docker via Container Registry or heroku.yml |
| PR previews | PR preview deploys on every plan | Review apps, billed like normal apps |
| Rollbacks | Instant rollbacks on Pro | heroku rollback to recent releases |
| Biggest instance | 1 GB on Pro (more on Enterprise) | Up to 14 GB (Performance-L, $500/mo) |
Heroku prices from their public pricing pages, last checked . All prices exclude VAT.
Heroku prices every piece separately. The always-on Basic dyno is $7/mo for 512 MB. The moment you need 1 GB you jump to Standard-2X at $50/mo. Postgres, Redis and the scheduler are add-ons, each with their own line.
None of that is unreasonable on its own. It just adds up: a modest app with a database and a cache lands around $60 to $120 a month depending on which add-on tiers you need. On orkestr Pro, the same app, its Postgres, its Redis and its crons are covered by one €15 seat.
If your app runs on a Heroku buildpack, it almost always runs on orkestr unchanged: connect the repo, we detect Rails, Django, Node, Go, Spring Boot and friends, and build a container. Got a Dockerfile already? We use it as-is.
Config vars become environment variables. Your Procfile web process becomes the start command. DATABASE_URL and REDIS_URL are injected when you add the add-ons. Restore your data with pg_dump and pg_restore, test on the orkestr URL, then flip DNS. Heroku keeps running until you turn it off.
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.
Heroku in USD, orkestr in EUR, both excl. VAT. On Heroku you can drop to a 512 MB Basic dyno ($7) for a $19 total. With production database and cache tiers (Standard-0 Postgres $50, premium-0 Key-Value $15) the same Heroku stack is $115.
We'd rather you pick the right tool than churn in a month. Stay on Heroku if:
Spotted something out of date? Tell us at /contact and we'll fix it.
Free to start, no credit card. Keep Heroku running while you test, flip DNS when you're happy.