Render and orkestr look alike: connect a repo, get containers, Postgres and previews. The differences are how you pay and whose jurisdiction your data sits under.
Last updated
| orkestr | Render | |
|---|---|---|
| Company | EU company (Romania), EU sub-processors only | Render Services, Inc. (San Francisco, US) |
| EU regions | Germany, Finland, France | Frankfurt |
| Free tier | Yes: 1 app + Postgres or Redis, sleeps after 30 min idle | Yes: web services spin down after 15 min, free Postgres expires after 30 days |
| Pricing model | €15/seat/mo, flat. Compute, 2 add-ons and 1 TB bandwidth included | Workspace fee ($0 Hobby / $25 Pro) + per instance + usage |
| Always-on 1 GB app | Included in Pro | No 1 GB size: $7 (512 MB) or $25 (2 GB) |
| Postgres | Included in Pro (512 MB RAM) | From $6/mo (256 MB), $19/mo for 1 GB |
| Redis | Included in Pro (256 MB RAM) | Key Value from $10/mo (256 MB) |
| Bandwidth | 1 TB on Pro, then €0.10/GB | 5 GB (Hobby) or 25 GB (Pro), then $0.15/GB |
| Build minutes | 2,000 build min on Pro, Dockerfile or auto-detected | 500 (Hobby) / 1,000 (Pro), then $5 per 1,000 |
| PR previews | PR preview deploys on every plan | Single-service on Hobby, full-stack on Pro |
| Background workers | Jobs and crons, no always-on worker service | Yes, billed as instances |
Render prices from their public pricing pages, last checked . All prices exclude VAT.
Render is a good platform and the closest thing to orkestr on this list. Both build your repo into containers, attach managed Postgres and Redis, and give you preview environments. If you are happy there, the case for switching is about two things: the bill and the jurisdiction.
On the bill: Render charges per instance, per database, per GB over a small bandwidth allowance and per extra build minute. Egress is where it creeps up: the Hobby workspace includes 5 GB, then it is $0.15/GB. orkestr Pro includes 1 TB in the €15 seat.
Render's Frankfurt region keeps your servers in Germany, which covers a lot of requirements. What it does not change is that Render is a US company. orkestr is an EU company, and every sub-processor we use (compute, CDN, payments, email) is EU-based too. If a customer's DPA review asks about the provider, not the data center, that is the difference.
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.
Render in USD, orkestr in EUR, both excl. VAT. To be fair to Render, its $25 instance has more RAM than ours (2 GB vs 1 GB). Drop to the 512 MB instance and the total is $50.25. On the Pro workspace ($25/mo, 25 GB egress included) the 2 GB stack is $90.25.
We'd rather you pick the right tool than churn in a month. Stay on Render if:
Spotted something out of date? Tell us at /contact and we'll fix it.
Free to start, no credit card. Keep Render running while you test, flip DNS when you're happy.