Netlify alternative

orkestr vs Netlify

Netlify is excellent at static sites and serverless functions. When your app needs a long-running server, Redis or a predictable bandwidth bill, orkestr runs it as a real container in the EU.

Last updated

The short version

  • Netlify has no long-running containers: functions time out after 60 seconds, background functions after 15 minutes. orkestr runs your app as a normal always-on container.
  • Netlify bills in credits. Bandwidth is 20 credits per GB, so the free plan runs out around 15 GB. orkestr free includes 100 GB.
  • No managed Redis on Netlify. orkestr has Postgres and Redis add-ons.
  • Netlify still wins for pure static and Jamstack sites with lots of deploy previews.

Quick comparison

orkestrNetlify
CompanyEU company (Romania), EU sub-processors onlyNetlify, Inc. (San Francisco, US)
EU regionsGermany, Finland, FranceFunctions: Dublin, Frankfurt, London on Pro (default is Ohio)
Free tierYes: 1 app + Postgres or Redis, sleeps after 30 min idle300 credits/mo, hard limit: projects pause at 0
Paid plan€15/seat/mo, flat. Compute, 2 add-ons and 1 TB bandwidth included$9 (Personal, 1,000 credits) or $20 (Pro, 3,000 credits)
Long-running serverYes, always-on container on ProNo. Functions: 60 s, background functions: 15 min
PostgresIncluded in Pro (512 MB RAM)Netlify Database, billed in credits per compute-hour
RedisIncluded in Pro (256 MB RAM)None (Blobs is a key/value store, not Redis)
Bandwidth100 GB free, 1 TB on Pro20 credits/GB (~15 GB on free)
Deploy previewsPR preview deploys on every planUnlimited, free
RollbacksInstant rollbacks on ProFree rollbacks to a previous deploy

Netlify prices from their public pricing pages, last checked . All prices exclude VAT.

When a static host is not enough

Netlify is built around static files on a CDN plus short-lived functions. That covers a lot of sites. It stops covering them when you need a process that stays up: a WebSocket server, a queue consumer, an SSR app with in-memory state, a Django or Rails backend.

orkestr runs your repo as a regular container that stays on. Next.js, Nuxt, SvelteKit and Astro SSR run on Node like they do locally. Your API, your database and your cache live next to each other on a private network.

Credits vs a flat seat

Netlify's plans are credit pools. Bandwidth, compute, database hours and production deploys all draw from the same balance, and the free plan stops your sites when it hits zero. orkestr Pro is €15 per seat with 1 TB of bandwidth, compute and two add-ons included, and the free tier includes 100 GB of bandwidth.

What a small production app costs

A server-rendered app (Next.js, Nuxt, SvelteKit or similar) with Postgres, ~100 GB of bandwidth a month, about 40 production deploys, one developer.

orkestr

  • Pro seat (compute, 1 TB bandwidth)€15
  • SSR app as an always-on containerincluded
  • Postgres add-on (512 MB RAM)included
  • 100 GB bandwidthincluded
  • 40 production deploysincluded
Total / month€15

Netlify

  • Pro plan (3,000 credits)$20
  • 100 GB bandwidth (2,000 credits)from credits
  • 40 production deploys (600 credits)from credits
  • SSR function computefrom credits
  • Netlify Database compute-hoursextra credits
Total / month$20+

Netlify in USD, orkestr in EUR, both excl. VAT. Bandwidth and deploys alone use 2,600 of the 3,000 Pro credits, so function and database usage will usually push you into extra credit packs ($10 per 1,500). An always-on database on Netlify is 10 credits per compute-hour, about 7,300 credits a month on its own. Redis has no Netlify equivalent.

When Netlify is the better pick

We'd rather you pick the right tool than churn in a month. Stay on Netlify if:

  • Your site is static or Jamstack with light serverless functions.
  • You want unlimited free deploy previews and a global CDN with zero servers.
  • You use Netlify Forms, Identity or edge functions and do not need a long-running process.

Common questions

Can orkestr host a static site too?
Yes. Vite, Astro and other static builds deploy and are served behind our CDN. But if your site is purely static, Netlify is a perfectly good home for it.
Will my Netlify Functions work?
Framework API routes (Next.js, Nuxt, SvelteKit) run inside your app container. Standalone Node or Python functions map to orkestr Functions: paste the handler, get a URL, scale to zero.
What happens on orkestr when I go over the free bandwidth?
Free includes 100 GB a month. Pro includes 1 TB and is never paused for bandwidth: extra usage is billed at €0.10/GB.
Do I need a Dockerfile?
No. We detect the framework and generate a production build. If you have a Dockerfile, we use it instead.

Try it with the repo you already have.

Free to start, no credit card. Keep Netlify running while you test, flip DNS when you're happy.

Start free