Deploy Remix to Your Own Server

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

   Check the start script

   Temps starts the app with your start script. On React Router v7 the default template's scripts already work: react-router build and react-router-serve ./build/server/index.js.

   package.json

   "scripts": {
     "build": "remix vite:build",
     "start": "remix-serve ./build/server/index.js"
   }

4. 4

   Read the database URL Temps injects

   Linked PostgreSQL arrives as POSTGRES_URL, not DATABASE_URL.

   schema.prisma

   datasource db {
     provider = "postgresql"
     url      = env("POSTGRES_URL")
   }

5. 5

   Deploy Remix

   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

6. 6

   Create and link a PostgreSQL database

   Temps doesn't create a database for you. Create one, then link it to the project (or use Databases → Create database in the dashboard). Linking injects POSTGRES_URL plus POSTGRES_HOST, POSTGRES_PORT, POSTGRES_DB, POSTGRES_USER and POSTGRES_PASSWORD into the next deployment. It doesn't inject DATABASE_URL.

   bunx @temps-sdk/cli services create -t postgres -n my-remix-app-db
   bunx @temps-sdk/cli services link --id <service-id> -p my-remix-app

7. 7

   Run migrations yourself

   Temps doesn't run them. Run prisma migrate deploy (or your tool's equivalent) after deploys that change the schema, from CI or in the running container.

How Temps builds and runs Remix

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

• SSR with loaders and actions
• React Router v7 framework mode, deployed the same way
• Persistent Node.js process, no cold starts
• Managed PostgreSQL you link
• Health check before each cutover
• Preview environments per branch (opt-in)

Managed services for Remix

Temps runs these services on your server. Create one, link it to the project, and its connection variables reach the next deployment. Set up managed services.

Environment variables for Remix

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

What it costs to self-host Remix

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

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

Related guides

• Every setting for this stack is in the Remix 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.
• The React Router v7 scripts and settings are in React Router v7 (framework mode).
• Leaving Vercel? See Temps vs Vercel.
• Coming from Fly.io? See Temps vs Fly.io.

Deploy another framework