Deploy Remix on Your Own Server
Deploy Remix applications with full server-side rendering, loaders, actions, and progressive enhancement. Runs on Node.js with no cold starts.
Quickstart
From your project root, deploy with your preferred package manager:
npx @temps-sdk/cli up
Temps detects your remix.config.js or Vite-based Remix setup, runs npm run build, and starts the Node.js server.
What Temps Handles Automatically
| Feature | How Temps handles it |
|---|---|
| Build | npm run build |
| Start | node ./build/server/index.js |
| HTTPS | Let's Encrypt, auto-renewed |
| Port | PORT env var injected, defaults to 3000 |
| Loaders and actions | Fully supported via Node.js runtime |
| No cold starts | Persistent Node.js process |
| Preview deployments | Every PR gets its own URL |
Managed PostgreSQL
Remix apps typically need a database. Add PostgreSQL from Project → Services → Add Service, then use it with Prisma or Drizzle:
npx @temps-sdk/cli environments vars set DATABASE_URL "postgres://..." -e production
For Prisma, add a deploy hook to run migrations:
npx prisma migrate deploy
Environment Variables
npx @temps-sdk/cli environments vars set SESSION_SECRET "your-secret" -e production npx @temps-sdk/cli environments vars set DATABASE_URL "postgres://..." -e production
Platform behavior
These rules apply to every app deployed on Temps, regardless of framework.
The one requirement: your app must listen on the port in the PORT environment variable and bind to 0.0.0.0 — not localhost or 127.0.0.1. Temps runs your app in a container and routes traffic from the host, so an app bound to localhost only accepts connections from inside the container and will fail its health check.
Health checks
After your container starts, Temps sends HTTP GET requests to verify it is healthy before routing traffic to it.
- Path:
/(the root of your application) - Success: 2 consecutive responses with a 2xx or 3xx status code
- Timeout: 300 seconds (5 minutes) for the app to become healthy
- Retry interval: every 5 seconds
Connection errors while the app is still starting are retried without penalty. If the app returns 4xx or 5xx errors for 60 consecutive seconds, the deployment fails. Customize the check by adding a .temps.yaml to your repository root:
health:
path: /health
status: 200
interval: 30
timeout: 5
retries: 3/health endpoint that returns a simple 200. This avoids issues where / requires authentication or returns a redirect.Auto-injected environment variables
Temps injects these variables into every deployment automatically:
| Variable | Value | Description |
|---|---|---|
PORT | Resolved port | The port your app must listen on |
HOST | 0.0.0.0 | Bind address |
SENTRY_DSN | Auto-generated | Error tracking endpoint |
TEMPS_API_URL | Your Temps URL | Platform API endpoint |
TEMPS_API_TOKEN | Deployment token | Authentication for Temps SDKs |
OTEL_EXPORTER_OTLP_ENDPOINT | Your Temps OTLP URL | OpenTelemetry trace collection |
OTEL_SERVICE_NAME | Project name | Service identifier for traces |
You do not need to configure these manually. They are available in process.env (Node.js), os.environ (Python), os.Getenv (Go), and the equivalent in other languages.