Deploy Astro to Your Own Server

How to deploy Astro 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

   SSR only: add the Node adapter

   Run npx astro add node, then set the adapter to standalone mode.

   astro.config.mjs

   import { defineConfig } from "astro/config";
   import node from "@astrojs/node";
   
   export default defineConfig({
     output: "server",
     adapter: node({ mode: "standalone" }),
   });

4. 4

   SSR only: start the standalone server

   Deploy with up --preset nixpacks-node and tell Temps to run the server entry with a Procfile web: line. The standalone server reads HOST and PORT, and Temps injects both (HOST is 0.0.0.0), so it's reachable by the health check without extra settings.

   Procfile

   web: node ./dist/server/entry.mjs

5. 5

   Deploy Astro

   From the project root, run up with the preset that matches your build, 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.

   # Static site
   bunx @temps-sdk/cli up --preset vite
   # On-demand rendering with @astrojs/node
   bunx @temps-sdk/cli up --preset nixpacks-node

How Temps builds and runs Astro

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 Astro on Temps

• Static output in dist/, served by the Temps proxy
• SSR with @astrojs/node in standalone mode
• Content collections bundled at build time
• Islands hydrate as in development
• Preview environments per branch (opt-in)
• Built-in web analytics

Environment variables for Astro

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

What it costs to self-host Astro

Temps is free to self-host under MIT / Apache 2.0, with no per-seat fee and nothing metered, so hosting Astro 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 Netlify, see Temps vs Netlify.

Astro 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 Astro app doesn't need separate subscriptions for them.

Related guides

• Every setting for this stack is in the Astro 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.
• Hosting on Netlify today? See Temps vs Netlify.
• Or compare with Temps vs Cloudflare Pages.

Deploy another framework