# SvelteKit hosting in 2026: adapter-node, adapter-static or adapter-auto

> In SvelteKit the adapter decides the hosting: adapter-static makes files any static host serves, adapter-node makes a Node server, and adapter-auto picks a serverless platform's own adapter. On Livops an adapter-static build is a free site, and an adapter-node build runs as a web app for 39 credits a month (39,000 so'm); adapter-auto is swapped for adapter-node in the build. Here is which to choose, and how Vercel, Netlify, Cloudflare and Render compare.

Source: https://livops.dev/en/hosting/sveltekit-hosting

By Livops team, the people who build and run Livops. Updated 20 November 2026.

A SvelteKit app does not choose its host in a settings screen; it chooses it in `svelte.config.js`. The adapter turns the built app into what a host can run, so picking one is picking a kind of hosting: files, a Node server, or a serverless platform's functions. This page explains the three adapters you will meet, compares Vercel, Netlify, Cloudflare and Render with each provider's own numbers, and ends with which adapter to use on Livops, and why.

## What does a SvelteKit app need in production?

### An adapter

Adapters are small plugins that take the built app and generate output for one kind of deployment; the official ones are for Cloudflare Workers, Netlify, Node servers, static sites, Vercel and Bun[1]. `npx sv create` installs `adapter-auto`, which picks the right adapter at deploy time on the platforms it knows: Cloudflare Workers, Netlify, Vercel, Azure Static Web Apps, AWS via SST, and adapter-node for Google Cloud Run and Render[2]. Once you know where you deploy, SvelteKit recommends installing that adapter yourself[2].

### adapter-static: every page prerendered

`adapter-static` writes prerendered pages to `build`, and asks for `export const prerender = true` in the root layout[4]. By default the build fails unless every page and endpoint was prerendered or a `fallback` page is set[4]. A fallback — commonly `200.html` — makes a single-page app, with large negative effects on performance and SEO by SvelteKit's own account[4]. Pages with form actions cannot be prerendered, because a server has to answer their `POST`[5]. To prerender some pages and render others per request, you need a different adapter[4].

### adapter-node: a Node server

`adapter-node` writes a server to `build`, started with `node build`, which listens on `0.0.0.0` and port 3000 unless `HOST` and `PORT` say otherwise[3]. At run time it needs the `build` folder, `package.json` and the production dependencies in `node_modules`: dev dependencies are bundled into the app, packages in `dependencies` are not[3]. On `SIGTERM` it stops accepting requests, lets those in flight finish, and closes what is left after `SHUTDOWN_TIMEOUT`, 30 seconds by default[3]. Request bodies are limited by `BODY_SIZE_LIMIT`, 512 KB by default[3].

### The public address, behind a proxy

Behind a proxy, adapter-node cannot see the address visitors used, and form actions then fail with "Cross-site POST form submissions are forbidden": the origin is what CSRF checks on forms and remote functions trust[3]. Set `ORIGIN`, or have it read `PROTOCOL_HEADER` and `HOST_HEADER` (such as `x-forwarded-proto` and `x-forwarded-host`), only behind a proxy you trust[3]. The client's IP comes from `ADDRESS_HEADER` with `XFF_DEPTH` set to the number of trusted proxies[3].

## The options at a glance

| Option | What it is | Adapter | A static SvelteKit site | Smallest paid plan for server rendering |
| --- | --- | --- | --- | --- |
| Livops | A platform; servers in Uzbekistan | adapter-static or adapter-node (adapter-auto is swapped) | Free | 39 credits (39,000 so'm) a month for one always-on server |
| Vercel | Functions and a global CDN | adapter-vercel, or adapter-auto[6] | Free on Hobby[7] | Pro: $20 a month per developer seat, with $20 of included credit[7] |
| Netlify | Functions and a CDN, billed in credits | adapter-netlify[9] | Free plan: 300 credits a month, a hard limit[11] | Personal: $9 a month for 1,000 credits; Pro: $20 for 3,000[10] |
| Cloudflare Workers | Code at Cloudflare's edge | adapter-cloudflare[13] | Static asset requests free and unlimited[14] | Workers Paid: from $5 a month per account[14] |
| Render | A platform with a native Node runtime | adapter-node[2] | Static sites free[16] | $7 a month: 0.5 CPU, 512 MB[16] |

Other providers' prices are from each provider's own page, read on 20 November 2026; the dates are in Sources below. Livops prices are the ones the cabinet bills today.

## Each option

### Livops

A SvelteKit repository is recognised from `@sveltejs/kit` in `package.json`, built with `npm run build`, and published as a free site or started with `node build`, depending on what the build left (details below). Every `git push` ships a new version. Payment is in so'm through Payme or Click, with no card, and the servers are in Uzbekistan — close to users there, farther from users elsewhere. There is no global CDN of edge locations in front of it, and no root.

### Vercel

Where Vercel is better: SvelteKit deploys with no configuration, and `adapter-auto` installs `adapter-vercel` at build time; installing it yourself is Vercel's recommendation[6]. Routes are bundled into one function by default, on the Node.js runtime, with Edge per route, ISR and skew protection available[6]. Functions run in Washington, D.C. (`iad1`) unless you choose a region[6]. Hobby is free with 100 GB of fast data transfer and 4 hours of Active CPU a month, and a function runs for at most 300 seconds[8]; Pro is $20 a month per developer seat with $20 of included credit[7].

### Netlify

`adapter-netlify` deploys SvelteKit's server rendering as one Netlify Function called `render`, or one per route with `split`; with `edge: true` it renders in a Deno-based edge function instead[9]. `adapter-static` works on Netlify too[9]. A synchronous function may run for 60 seconds[12]. Every production deploy costs 15 credits, bandwidth 20 credits per GB and web requests 2 credits per 10,000[11]; Personal is $9 a month for 1,000 credits and Pro $20 for 3,000[10].

### Cloudflare Workers

With `adapter-cloudflare`, Wrangler detects SvelteKit, writes the configuration — the Worker at `.svelte-kit/cloudflare/_worker.js`, the assets beside it — and deploys[13]. Static asset requests are free and unlimited; the Free plan allows 100,000 requests a day and 10 ms of CPU per request, and Workers Paid starts at $5 a month for 10 million requests[14]. Each isolate has 128 MB of memory[15]. For a SvelteKit site whose visitors are spread across continents, this is the cheapest way to render close to all of them, as long as the work fits those limits.

### Render

`adapter-auto` already knows Render and uses `adapter-node` for it[2]. Node is a native runtime there, static sites are free, and a web service starts at $7 a month for 512 MB[16]. Render takes credit and debit cards[16].

## Which adapter, and why

- **Every page can be built ahead of time** — a marketing site, docs, a blog: `adapter-static`. Any static host serves it, and on Livops it is free.
- **Form actions, `+server` endpoints that run per request, sessions, a database**: `adapter-node` on a server, or a platform's own adapter on its functions. On Livops it is `adapter-node`.
- **`adapter-auto`** is a starting point, not a choice: it builds for the platform it detects[2], and on a host it does not know, `node build` finds no server to start. Replace it once you know where the app runs.

## Functions or a server: what changes?

On Vercel, Netlify and Cloudflare, a server-rendered SvelteKit app becomes functions that start for a request and stop after it: you pay per request and per unit of compute, and the limits are a function's duration and memory. With `adapter-node` it is one long-running `node build`, paid by the month, whose limit is the machine's memory. Websockets beside the app, a long request, an in-memory cache and a file on disk are ordinary on a server; rendering on every continent and paying nothing while nobody visits are what functions are for.

## Where can you host SvelteKit for free?

- **Livops** publishes an `adapter-static` build for free, with HTTPS and a livops.app address; the Free plan holds 30 sites and 40 builds a month. An `adapter-node` app has no free tier; on an account that has not paid yet, the first bot or app runs for 15 minutes on a zero balance, once.
- **Vercel** Hobby is free, with 100 GB of fast data transfer, 4 hours of Active CPU and 100 deployments a day[8].
- **Netlify** Free has 300 credits a month as a hard limit; when they are used up, every project shows "Site not available" until the next cycle[11].
- **Cloudflare Workers** Free allows 100,000 requests a day with 10 ms of CPU each; static asset requests are free[14].
- **Render** serves static sites for free; a free web service spins down after 15 minutes without inbound traffic and takes about a minute to start again, within 750 free instance hours a month per workspace[17].

## SvelteKit on Livops

1. Install the adapter you mean: `npm i -D @sveltejs/adapter-static` or `@sveltejs/adapter-node`, and import it in `svelte.config.js`.
2. Push the repository. In the cabinet, click **New project** and choose it, or upload the folder as a `.zip`. **How it runs** shows **Site or application**: the build decides.
3. Put variables under **Variables**. For `adapter-node`, add `ORIGIN` with the app's address, or the two header variables below.
4. Deploy. The log shows the install, the build and, for a server, the start.

What Livops runs, with pnpm, Yarn or Bun instead of npm when `packageManager` in `package.json` names one, and the Node version from `.nvmrc` or `.node-version`:

```sh
npm install
npm run build
node build
```

- **adapter-auto, and other hosts' adapters.** When the project has `adapter-auto`, `adapter-vercel`, `adapter-netlify` or `adapter-cloudflare` and neither `adapter-node` nor `adapter-static`, the build's own copy installs `adapter-node` — version 1 for SvelteKit 1, version 5 for SvelteKit 2, the current one otherwise — and puts it in `svelte.config`. The repository is not changed.
- **Site or application.** If the build leaves an `index.html` in `build`, as `adapter-static` does, the folder is published as a free static site, where `_redirects` and `_headers` from `static/` work; see [Redirects and headers](https://livops.dev/en/docs/redirects-headers). If it does not, as with `adapter-node`, the project becomes a web app started with `node build`; the log says "no finished pages were produced — running this as an application", and what it costs is said in the log, in the cabinet's notifications and in Telegram if your account is linked.
- **SPA fallback.** With `adapter-static` and `fallback: '200.html'`, add `static/_redirects` with the line `/* /200.html 200`, so a deep link opens the app instead of a 404.
- **The address.** `PORT` is set, 3000 unless you change it, and adapter-node reads it; it listens on every interface by default. The proxy sends `X-Forwarded-Proto: https` and `X-Forwarded-Host`, so instead of `ORIGIN` you can set `PROTOCOL_HEADER=x-forwarded-proto` and `HOST_HEADER=x-forwarded-host`, which also covers custom domains.
- **Dependencies.** The whole build, `node_modules` included, ships with the app, so packages in `dependencies` are there when `node build` imports them.
- **Variables read while building** (`$env/static`): when one is missing, the log ends with a Tip naming it. Add it under **Variables** and deploy again; see [Build failed](https://livops.dev/en/docs/error-build#svelte-env).
- **If the new version does not answer** within a minute, the deploy fails and the version that worked keeps serving; if the build fails, the running version is left alone. Recent versions stay in **Deploys** for a one-click rollback.
- **Memory** for `node build` is the service's tier: 256, 512, 1024 or 2048 MiB, set with `memory` in `livops.json` when the project is created and in the settings afterwards.

For an `adapter-node` app you can set the type and the size before the project is created, in `livops.json` at the repository root:

```json
{
  "kind": "web",
  "healthPath": "/",
  "memory": 512
}
```

An `adapter-static` SvelteKit site is **free**; an `adapter-node` app is **39 credits a month (39,000 so'm)**. One credit is 1,000 so'm, and bought credits never expire. See [Pricing](https://livops.dev/en/docs/pricing) and [Frameworks](https://livops.dev/en/docs/frameworks) for everything `livops.json` accepts.

## Questions

**Which SvelteKit adapter should I use on Livops?**

adapter-static when every page can be prerendered, which makes the project a free static site. adapter-node when it has form actions, server endpoints or pages rendered per request, which makes it a web app. adapter-auto also works, because the build swaps in adapter-node, but installing adapter-node yourself keeps local builds and Livops builds the same.

**What does Livops do with adapter-auto?**

When the project has adapter-auto, adapter-vercel, adapter-netlify or adapter-cloudflare and neither adapter-node nor adapter-static, the build's own copy installs adapter-node of the version that fits your SvelteKit and puts it in svelte.config. The repository is not changed.

**Is my SvelteKit project a site or an application?**

The build decides. If it leaves an index.html in the build folder, it is published as a free static site. If not, as with adapter-node, it is started with node build as a web app, and the log, the bell and Telegram say what that costs.

**Why do my form actions fail with Cross-site POST form submissions are forbidden?**

adapter-node cannot tell its public address behind a proxy. Set ORIGIN to the app's address under Variables, for example https://myapp.livops.app, or set PROTOCOL_HEADER=x-forwarded-proto and HOST_HEADER=x-forwarded-host, which the Livops proxy sends.

**My build fails on a variable from $env/static. What now?**

Those are read while the app is built. Add the variable the log names under Variables, then deploy again.

**How much does SvelteKit hosting cost on Livops?**

An adapter-static site is free. An adapter-node app is 39 credits a month, which is 39,000 so'm at 1,000 so'm a credit. There is no free tier for apps; on an account that has not paid yet, the first app runs for 15 minutes on a zero balance, once. Credits are bought in so'm through Payme or Click, with no card.

**Who wrote this comparison?**

The Livops team. Every price and limit of another provider on this page links to that provider's own page, with the day we read it.

## Sources

1. [SvelteKit — Adapters](https://svelte.dev/docs/kit/adapters). Checked 20 November 2026.
2. [SvelteKit — Zero-config deployments (adapter-auto)](https://svelte.dev/docs/kit/adapter-auto). Checked 20 November 2026.
3. [SvelteKit — Node servers (adapter-node)](https://svelte.dev/docs/kit/adapter-node). Checked 20 November 2026.
4. [SvelteKit — Static site generation (adapter-static)](https://svelte.dev/docs/kit/adapter-static). Checked 20 November 2026.
5. [SvelteKit — Page options](https://svelte.dev/docs/kit/page-options). Checked 20 November 2026.
6. [Vercel — SvelteKit on Vercel](https://vercel.com/docs/frameworks/full-stack/sveltekit). Checked 20 November 2026.
7. [Vercel — Pricing](https://vercel.com/pricing). Checked 20 November 2026.
8. [Vercel — Hobby plan](https://vercel.com/docs/plans/hobby). Checked 20 November 2026.
9. [Netlify — SvelteKit on Netlify](https://docs.netlify.com/build/frameworks/framework-setup-guides/sveltekit/). Checked 20 November 2026.
10. [Netlify — Pricing](https://www.netlify.com/pricing/). Checked 20 November 2026.
11. [Netlify — How credits work](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/how-credits-work/). Checked 20 November 2026.
12. [Netlify — Configuration for functions](https://docs.netlify.com/build/functions/configuration/). Checked 20 November 2026.
13. [Cloudflare — SvelteKit on Workers](https://developers.cloudflare.com/workers/framework-guides/web-apps/sveltekit/). Checked 20 November 2026.
14. [Cloudflare — Workers pricing](https://developers.cloudflare.com/workers/platform/pricing/). Checked 20 November 2026.
15. [Cloudflare — Workers limits](https://developers.cloudflare.com/workers/platform/limits/). Checked 20 November 2026.
16. [Render — Pricing](https://render.com/pricing). Checked 20 November 2026.
17. [Render — Deploy for free](https://render.com/docs/free). Checked 20 November 2026.
