Deploy SvelteKit to Your Own Server

How to deploy SvelteKit with Temps

Commands run on your machine unless they say otherwise. The CLI runs with bunx or npx.

1. 1

   Install Temps on a Linux server

   On a VPS with at least 2 CPU cores and 4 GB of RAM, download the installer, read it, then run it. It installs Docker if needed, the Temps binary and its database, and asks how the console is reached: an sslip.io address or your own domain.

   curl -fsSL https://temps.sh/deploy.sh -o deploy.sh
   less deploy.sh
   bash deploy.sh

2. 2

   Log in from your machine

   Point the CLI at your Temps console. It opens a browser to approve the login.

   bunx @temps-sdk/cli login https://console.example.com

3. 3

   Switch to the Node adapter

   Install @sveltejs/adapter-node as a dev dependency and use it in svelte.config.js.

   svelte.config.js

   import adapter from "@sveltejs/adapter-node";
   
   export default {
     kit: { adapter: adapter() },
   };

4. 4

   Set ORIGIN for form actions

   Behind a proxy, adapter-node needs to know the public URL, or form actions fail with "Cross-site POST form submissions are forbidden".

   bunx @temps-sdk/cli environments vars set ORIGIN "https://app.example.com" -e production

5. 5

   Deploy SvelteKit

   From the project root, run up with the preset, or set it under Project → Settings → Build & deploy → Build → Framework. If the directory isn't linked to a project yet, up walks you through creating one first. For a project created from a Git repository, pushes to the tracked branch deploy automatically.

   bunx @temps-sdk/cli up --preset nixpacks-node

How Temps builds and runs SvelteKit

Every app runs in a Docker container on your server, behind the Temps proxy. Before traffic switches to a new deployment, Temps health-checks it; if the check fails, the deployment is marked failed and the current version keeps serving.

What works with SvelteKit on Temps

• SSR, API endpoints and form actions via adapter-node
• Prerendered pages served by the Node server
• Start falls back to node build/index.js
• Persistent Node.js process, no cold starts
• Health check before each cutover
• Preview environments per branch (opt-in)

Environment variables for SvelteKit

Set your own with environments vars set or in the project settings; values are encrypted at rest.

What it costs to self-host SvelteKit

Temps is free to self-host under MIT / Apache 2.0, with no per-seat fee and nothing metered, so hosting SvelteKit costs what the server costs. A Hetzner CX23 (2 shared vCPU, 4 GB RAM, 40 GB NVMe, 20 TB traffic) meets the minimum Temps needs and is €5.49/month excluding VAT, plus €0.50/month for an IPv4 address; Hetzner sells it in Germany and Finland only. Prices checked October 10, 2026.

For one to three production apps, the server guide recommends 4 vCPU and 8 GB RAM: a Hetzner CX33 is €8.49/month excluding VAT. Any Linux VPS that meets the minimum works; sizes and other providers are in Choosing a server. For what the same app costs on Vercel, see Temps vs Vercel.

SvelteKit on Temps: frequently asked questions

Included with every Temps project

Deployments, analytics, error tracking, session replay and uptime monitoring run in the same self-hosted platform, so your SvelteKit app doesn't need separate subscriptions for them.

Related guides

• Every setting for this stack is in the SvelteKit deployment reference.
• Which stacks are detected and which need a preset is listed in supported languages and frameworks.
• How health checks, cutover and rollbacks work is covered in Deployments.
• Leaving Vercel? See Temps vs Vercel.

Deploy another framework