Skip to content
OrbixPanel OrbixPanel Tutorials

Deploy a SvelteKit app on OrbixPanel

How SvelteKit deploys depends on the adapter you use — static files or a Node server. OrbixPanel supports both; the difference is one script.

Static (adapter-static)

With @sveltejs/adapter-static, npm run build produces static files. OrbixPanel builds and serves them with nginx — the static site path. Great for content sites and fully pre-rendered apps.

Just deploy: Apps → Deploy from Git → repo + branch → Deploy.

SSR (adapter-node)

With @sveltejs/adapter-node, the build produces a Node server (build/index.js). OrbixPanel treats a project as a server app only when it has a start script — so add one:

{
  "scripts": {
    "build": "vite build",
    "start": "node build"
  }
}

With a start script present, OrbixPanel runs it as a managed Node process behind the reverse proxy. adapter-node reads the PORT environment variable (which OrbixPanel sets) and binds 0.0.0.0 — so SSR, form actions, and server endpoints all work with no extra config.

The rule: adapter-static = no start script (served as files). adapter-node = add a start script (served as a Node app). This is the same pattern as Astro and Nuxt — see how deploys work.

Which adapter?

  • Content / fully static → adapter-static (fastest, cheapest).
  • Server routes, form actions, per-request data → adapter-node.

Config & data

Secrets go in environment variables; connect any database on localhost.

Running OrbixPanel? SvelteKit deploys static or SSR, straight from Git. OrbixPanel.com → — the free, self-hosted, AI-powered hosting control panel.