> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sevalla.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> These are the docs for Sevalla, a platform for deploying applications, databases, static sites, object storage and load balancers. The dashboard is at https://app.sevalla.com.
> Bold text in steps is an exact dashboard label.
> To act on a Sevalla account, prefer the Sevalla MCP server (https://mcp.sevalla.com/mcp, see https://docs.sevalla.com/ai-agents/overview.md), then the Sevalla CLI (https://docs.sevalla.com/developer-tools/cli.md), then the REST API (https://api-docs.sevalla.com, OpenAPI spec at https://api.sevalla.com/v3/openapi.json).
> Every page index is at https://docs.sevalla.com/llms.txt.

# Deploy SvelteKit

> Deploy a SvelteKit 3 application to Sevalla from a Git repository with adapter-node: configure the adapter in vite.config, start it with node build and pin Node.js 24.

A SvelteKit application runs on Sevalla as an application: with `@sveltejs/adapter-node`, Nixpacks runs `vite build` from your Git repository, which writes a Node.js server to `build/`, and the web process starts it on the port that Sevalla sets in the `PORT` environment variable.

## Before you begin

* A Sevalla company with a payment method, and a GitHub, GitLab or Bitbucket account for the repository. See [Git providers](/git/overview).
* Node.js 24 or later on your computer.

## Create the project

Create a project with the Svelte CLI, choosing the **SvelteKit minimal** template and npm when it asks:

```bash theme={null}
npx sv create storefront
cd storefront
```

New projects use `adapter-auto`, which doesn't build a server that Sevalla can run. Replace it with the Node.js adapter:

```bash theme={null}
npx sv add sveltekit-adapter="adapter:node"
```

In SvelteKit 3, the adapter is set in `vite.config.ts`, where the command switches the import to `@sveltejs/adapter-node`:

```ts vite.config.ts theme={null}
import adapter from "@sveltejs/adapter-node";
import { sveltekit } from "@sveltejs/kit/vite";
import { defineConfig } from "vite";

export default defineConfig({
  plugins: [
    sveltekit({
      adapter: adapter(),
    }),
  ],
});
```

## Prepare the project for Sevalla

Add the start script and pin the Node.js version:

```bash theme={null}
npm pkg set scripts.start="node build" engines.node="24.x"
```

| Field | Why Sevalla needs it |
| - | - |
| `scripts.start` | Nixpacks, the default [build strategy](/applications/builds/nixpacks), runs `npm run build` (`vite build`) and then starts the web process with `npm run start`. The adapter writes the server to `build/`. |
| `engines.node` | Nixpacks installs Node.js 24 instead of its default, Node.js 18, and SvelteKit 3 needs Node.js 22.17 or later. See [Pin the Node.js version](/guides/javascript/overview#pin-the-node-js-version). |

The server needs no other settings:

* It takes its port from [`PORT`](/guides/javascript/overview#listen-on-the-port-environment-variable), which Sevalla sets to the web process's port (`8080` by default), and listens on `0.0.0.0`, all network interfaces.
* It builds URLs from the request's `Host` header and assumes HTTPS, which matches how requests reach the application through Sevalla, so form actions pass SvelteKit's origin check without `PROTOCOL_HEADER` or `HOST_HEADER`.

Run `npm run build && npm start` and open `http://localhost:3000` to check the production build locally. Then commit everything and push it to your Git provider:

```bash theme={null}
git init
git add .
git commit -m "Prepare for Sevalla"
git branch -M main
git remote add origin https://github.com/acme/storefront.git
git push -u origin main
```

## Deploy to Sevalla

<Steps>
  <Step title="Create the application">
    In the sidebar, click **Applications**, then click **Create** > **Application**. Under **Source**, click **Private repository**, then choose the **Git provider**, the **Repository** and the **Branch**. Under **Location**, choose a **Data center**. Keep the **Size** at **H1** or choose a larger one, then click **Create application**. The application opens on its **Overview** tab with the status **Not deployed yet**: creating an application doesn't deploy it.
  </Step>

  <Step title="Deploy">
    Click the **Overview** tab, then click **Deploy now** under **Recent deployments**. Check the **Branch** and click **Deploy**.
  </Step>

  <Step title="Turn on auto-deploy">
    To deploy every push to the branch automatically, click the **Settings** tab, then click **Update auto-deploy** in the **Auto-deploy** section. Turn on **Auto-deploy** and click **Update auto-deploy**. See [Deployments](/applications/deployments#deploy-automatically-on-push).
  </Step>
</Steps>

## Verify the deployment

1. On the **Deployments** tab, wait for the deployment's status to change to **Deployed**. The application's status next to its name changes to **Running**.
2. Click the domain under the application's name, for example `storefront-x7k2m.sevalla.app`. The page shows `Welcome to SvelteKit`.

<Frame>
  <img className="block dark:hidden" src="https://assets.sevalla.com/screenshots/light/app-overview-address.png" alt="The application header with its name, Running status, repository, branch and the domain that opens the application" width="1192" />

  <img className="hidden dark:block" src="https://assets.sevalla.com/screenshots/dark/app-overview-address.png" alt="The application header with its name, Running status, repository, branch and the domain that opens the application" width="1192" />
</Frame>

If the deployment fails, open it on the **Deployments** tab and read its build log, then see [Troubleshoot builds and deployments](/applications/troubleshooting/builds-and-deployments). If the [runtime logs](/applications/logs) show that Node.js can't find the `build` folder, `vite.config.ts` still uses `adapter-auto`.

## Deploy changes

With **Auto-deploy** on, every push to the branch starts a deployment; otherwise, click **Deploy now** for each change. Each deployment builds the image, then replaces the web process's instances. See [Deployments](/applications/deployments).

## Use environment variables

Add configuration on the application's **Environment variables** tab. With `adapter-node`, `$env/dynamic/private` and `$env/dynamic/public` read variables when the server runs, while `$env/static/*` imports are replaced during `vite build`, so keep **Available during buildtime** selected for those. Variables apply at the next deployment. See [Environment variables](/applications/environment-variables).

## Add a custom domain

To serve the application from your own domain, such as `shop.example.com`, add the domain on the application's **Domains** tab and create the DNS records that Sevalla shows. Custom domains need a web process larger than **H1**, so [scale](/applications/scaling) the web process first. See [Custom domains](/domains/overview).

## Connect a database

Create a [database](/databases/create) in the same location as the application, then [connect the application to it](/databases/connect#connect-an-application) with **Add environment variables to the application** turned on. Sevalla adds `DB_URL`, `DB_HOST`, `DB_PORT`, `DB_DATABASE`, `DB_USERNAME` and `DB_PASSWORD` to the application ([what each one holds](/databases/connect#environment-variables-an-internal-connection-adds)), and they apply at the next deployment. Read them in server code with `env.DB_URL` from `$env/dynamic/private`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.