SvelteKit made the hosting decision explicit in a way most frameworks don't: you choose an adapter, and the adapter decides what your app can do. Pick adapter-static and server-side rendering, form actions, and API routes stop existing. Pick an edge adapter and Node APIs stop existing. Pick adapter-node and everything works but the CDN and scaling are now yours.
So the honest version of a SvelteKit hosting comparison is an adapter comparison with platform names attached. I build PandaStack, which sits in the adapter-node camp — noted where it matters.
The adapters, and what each costs you
adapter-static — a folder of files
Prerenders every route at build time and emits HTML, CSS, and JS. Deploy it to any static host or object store, and it's essentially free and impossible to break. What you give up is everything that runs per-request: form actions, +page.server.ts load functions that read cookies or a database, API routes, and hooks.server.ts.
Right for docs, marketing sites, blogs, and any app whose data comes from a separate API and is fetched in the browser. Wrong the moment you want a session.
Edge adapters — Cloudflare, Vercel edge, Netlify edge
Your server code runs in a V8 isolate close to the user. Latency is excellent and the pricing is often the cheapest of the three. The constraint is the runtime: it isn't Node. No filesystem, no native modules, no Node-only libraries, and database drivers need to be the HTTP or WebSocket-based variety rather than a classic TCP client.
This is a great fit for an app that talks to an HTTP API or a serverless database and does modest work per request. It's a rewrite for anything with a conventional Postgres driver, an image pipeline, or a native dependency.
adapter-node — a real server
Builds a plain Node server you start with node build. Every SvelteKit feature works because nothing is being translated: hooks, form actions, streaming, server-only modules, long-lived connections, in-memory caches. You can add a WebSocket server in the same process.
What you take on: a CDN in front for static assets (usually Cloudflare, ten minutes of work), your own scaling decisions, and a process to keep alive. For an app with real server-side logic, this is the option with no asterisks, and it runs on any container PaaS, VPS, or microVM platform.
// svelte.config.js — the single most consequential file for hosting
import adapter from "@sveltejs/adapter-node";
export default {
kit: {
adapter: adapter({ out: "build" }),
// Trust the platform's proxy headers, or every request looks like
// it came from 127.0.0.1 and Origin checks on form actions fail.
csrf: { checkOrigin: true },
},
};Which platform, given an adapter
- adapter-static: any static host — Cloudflare Pages, Netlify, GitHub Pages, an object store behind a CDN. Cost is approximately zero. Nothing to operate.
- Edge adapters: Cloudflare Workers, Vercel, Netlify. Fast and cheap when your dependencies fit the isolate runtime. Verify your database driver first — that's the usual blocker.
- adapter-node on a container PaaS: Render, Railway, Fly.io, Koyeb, Northflank. The default for an app with server-side logic. Put a CDN in front for assets.
- adapter-node on a microVM platform: Fly Machines, PandaStack (mine). Same deploy shape with a hardware-isolated VM and its own kernel. Relevant when the app runs code it didn't write, when per-tenant isolation must survive a security review, or when the app provisions environments at runtime — a fresh microVM via snapshot-restore is about 179ms at p50.
- adapter-node on a VPS: still fine. systemd, a reverse proxy, and a deploy script.
Deploying adapter-node without a Dockerfile
# Pin Node in the repo
echo "22.11.0" > .nvmrc
# Build produces ./build; start it with node
pandastack apps create --name dashboard \
--git-url https://github.com/acme/dashboard \
--build-cmd 'npm ci && npm run build' \
--start-cmd 'node build'
# adapter-node reads PORT, HOST and ORIGIN from the environment
# ORIGIN must be the public URL or form actions 403Four checks before you commit
- Submit a form action from the deployed URL. A 403 here is proxy header configuration, and it's better to find it now.
- If you chose an edge adapter, deploy with your real database driver early. Driver incompatibility is the usual dealbreaker and it surfaces at request time, not build time.
- Check that static assets are served with sensible cache headers. adapter-node serves them from the Node process by default, which works and wastes your CPU at any real traffic level.
- Confirm which env namespace each secret comes from before wondering why it's undefined.
The short version
Content site with no sessions: adapter-static on any static host, for free. Server logic with dependencies that fit an isolate: an edge adapter, and check your database driver first. Real server-side app: adapter-node on a container PaaS or microVM platform with a CDN in front — no feature asterisks, and portable between platforms because it's just a Node server. The adapter choice is the hosting choice; make it deliberately rather than by copying a template.