Next.js hosting on European infrastructure.

SSR without the American cloud

Most European hosting alternatives only take the static export of a Next.js app — the moment you need server components rendered at request time, API routes, or dynamic pages, they point you back at Vercel. slew runs Next.js in standalone output mode as a long-running server on Hetzner (Germany), so SSR, API routes and middleware running in your Node process all work, with EU jurisdiction over the whole request path.

Deploying

Connect the repository through the GitHub App and every push builds and deploys. slew builds your app and runs the standalone server; a static-only Next.js export deploys as plain files. Every pull request gets its own preview URL that updates on each push and expires after 7 days.

Environment variables are set per project — scoped to builds, to the running server, or both — and slew logs tails the live server.

Deploys never drop traffic

A new deploy boots beside the version serving traffic and must pass a health check before the cutover. A version that crashes on boot never receives a request; rollback to any earlier deployment takes seconds, no rebuild.

ISR and revalidation

Pages that opt in with ordinary Cache-Control — s-maxage plus stale-while-revalidate, exactly what Next.js emits for ISR — are served from the platform cache: fresh copies answer without waking the instance, stale ones answer immediately while the refresh and any cold start run in the background. And there's a platform revalidation endpoint — the counterpart of revalidatePath() — that evicts a path from every cache layer, callable from a CMS webhook with a deploy token.

Honest limitations

• No edge runtime: middleware and rendering run in your Node server in the EU, not in 30 PoPs. If you need edge middleware, Vercel is more mature — that trade is the point.
• Image optimization runs in your server process by default — or on the platform, with a one-line custom loader that serves resized WebP from the CDN edge without waking your instance.
• One region: EU. Static assets and stale-while-revalidate pages are cached at the edge; server rendering happens in Germany.

Frequently asked

Does the App Router work?

Yes — anything that runs under `next start` runs here, App Router and Pages Router alike. The build produces standalone output and slew runs it as the server it is.

What about data residency for server rendering?

Rendering happens on servers in Germany; traffic passes Bunny (Slovenia) at the edge. Source, builds, logs and analytics stay under EU jurisdiction, and there is no US parent company.

How does pricing compare to Vercel?

Flat euros with no per-seat fees: €9 runs two server apps kept ready, €24 runs five with your whole team included. Vercel bills per member in dollars, plus usage. The comparison page has the full table.

Can I try it next to my current setup?

Yes — point one project at slew and change nothing else. Your DNS decides when anything real changes; until then it is one extra live URL.

Will you migrate it for me?

Email hello@slew.sh — I migrate your first project for you, free.