Deploy an Astro site on OrbixPanel

Astro deploys beautifully on OrbixPanel. How it’s served depends on whether you use Astro’s default static output or server-side rendering (SSR).

Static Astro (the default)

With no SSR adapter, astro build produces a static dist/ folder. OrbixPanel runs npm ci → npm run build and serves dist/ with nginx — fast and cheap.

1. Push to Git → Apps → Deploy from Git → repo + branch → Deploy.
2. Add your domain + SSL.

Nothing else needed — this is the static site path.

SSR Astro (Node adapter)

If you use @astrojs/node for server rendering, Astro builds a Node server instead of static files. OrbixPanel treats a project as a server app only when it has a start script — so add one:

{
  "scripts": {
    "build": "astro build",
    "start": "node ./dist/server/entry.mjs"
  }
}

With a start script present, OrbixPanel runs it as a managed Node process behind the reverse proxy. Astro’s node adapter listens on the HOST/PORT environment — OrbixPanel sets PORT for you, so bind host: '0.0.0.0' in your adapter config.

Rule of thumb: static Astro = no start script (served as files). SSR Astro = add a start script (served as a Node app). See how deploys work.

Content & assets

Images and other assets in your build are served directly. For a blog/content site, static output is almost always the right (and fastest) choice.

---

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