January 31, 2026 (5mo ago)
Written by Temps Team
Last updated January 31, 2026 (5mo ago)
You can deploy a Next.js application to your own server in under 5 minutes using Temps — the self-hosted platform that gives you Vercel-grade developer experience without per-seat pricing or bandwidth bills. This guide covers the full path from zero to production, including preview environments, custom domains, and environment variables.
TL;DR: Install Temps on any VPS, run
bunx @temps-sdk/cli projects create+projects git+deploy, and your Next.js app is live with automatic HTTPS. Temps Cloud costs ~$6/mo (Hetzner + 30% margin); self-hosting is free, Apache 2.0.
| Feature | Temps | Vercel | Coolify |
|---|---|---|---|
| Git-push deployments | Yes | Yes | Yes |
| Preview environments | Yes | Yes | Yes (v4+) |
| Automatic HTTPS | Yes (Let's Encrypt) | Yes | Yes |
| Built-in analytics | Yes (included) | $10+/mo add-on | No |
| Built-in error tracking | Yes (included) | Not included | No |
| Session replay | Yes (included) | Not included | No |
| Per-seat pricing | None | $20/seat/mo | None |
| Bandwidth fees | None | $0.15/GB over 1 TB | None |
| Self-host license | Apache 2.0 | Closed source | Apache 2.0 |
| Managed cloud pricing | ~$6/mo | From $20/mo | From $5/mo (management only) |
The fastest self-hosted path is a single-binary install + CLI deploy — no Docker Compose files, no Nginx configuration, no manual SSL setup. Temps handles the proxy layer (built on Pingora, Cloudflare's open-source proxy engine written in Rust), automatic Let's Encrypt certificates, and health-checked rollouts.
The fastest path from local code to production.
# macOS / Linux (installs the Temps server + CLI)
curl -fsSL https://temps.sh/deploy.sh | bash
# Or via npm / bun (CLI only)
npm install -g @temps-sdk/cli
bunx @temps-sdk/cli login
This opens a browser window for authentication. Sign in with GitHub, GitLab, or email.
# Create a new project
bunx @temps-sdk/cli projects create -n "my-nextjs-app" -d "Next.js application"
# Connect your Git repository (--preset nextjs configures build defaults)
bunx @temps-sdk/cli projects git -p my-nextjs-app \
--owner your-org --repo your-nextjs-app --branch main --preset nextjs -y
Temps automatically detects your Next.js configuration and sets build commands to npm run build with .next as the output directory.
bunx @temps-sdk/cli deploy my-nextjs-app -b main -e production -y
Temps builds your application and deploys it. You receive a URL within seconds. Health checks run every 5 seconds — two consecutive successes promote the deployment, and any failure within the 60-second error window triggers automatic rollback to the previous version.
Connect your repository once and get automatic deployments on every push.
Temps auto-detects Next.js projects. Default settings work for most apps:
| Setting | Default Value |
|---|---|
| Build command | npm run build |
| Output directory | .next |
| Node version | 20 |
Push to your main branch. Temps handles:
# Add a single variable to production
bunx @temps-sdk/cli environments vars set DATABASE_URL "postgresql://..." \
-p my-nextjs-app -e production
# Import multiple variables from a .env file
bunx @temps-sdk/cli environments vars import .env.production \
-p my-nextjs-app -e production
# List all variables
bunx @temps-sdk/cli environments vars list -p my-nextjs-app
Environment variables are encrypted at rest and securely injected at build and runtime. No variable value is ever stored or displayed in plaintext after initial entry.
Every pull request automatically receives an isolated preview deployment.
pr-123-my-nextjs-app.temps.sh
Share these links with stakeholders or QA before merging to production.
Add an A record pointing to your server:
| Type | Name | Value |
|---|---|---|
| A | yourdomain.com | YOUR_SERVER_IP |
| A | www | YOUR_SERVER_IP |
# HTTP challenge (default, works for standard domains)
bunx @temps-sdk/cli domains add -d yourdomain.com
# Wildcard — requires DNS challenge
bunx @temps-sdk/cli domains add -d "*.yourdomain.com" --challenge=dns-01
For wildcard domains, the CLI shows a TXT record to add to your DNS provider. Once propagated, Temps completes ACME validation and issues the certificate. Standard domains use the http-01 challenge automatically.
Temps runs your application in a container — all Next.js features work without configuration:
app/page.tsx and nested layoutsapp/api/[route]/route.ts handlers"use server" functionsexport const revalidate = 60middleware.ts runs on Pingora's edge layerAdd this to next.config.js for smaller, faster deployments:
/** @type {import('next').NextConfig} */
const nextConfig = {
output: "standalone",
};
module.exports = nextConfig;
This reduces container image size by excluding development dependencies from the production bundle.
Temps includes analytics, error tracking, and session replay without any additional setup or third-party accounts.
After your first deployment, the Temps dashboard shows:
Privacy-friendly and GDPR-compliant. No Google Analytics, no cookie banners required.
Temps captures frontend and backend errors automatically:
No Sentry subscription needed.
Record and replay user sessions to understand exactly what happened when something went wrong. Sessions are stored on your infrastructure — no data leaves your servers.
No. Temps uses Docker containers orchestrated by the Temps binary itself — there is no Kubernetes, no Helm charts, and no cluster management. A single VPS running the Temps server handles build, deploy, proxy, certificates, and monitoring in one process.
For multi-server deployments, Temps uses a WireGuard mesh to connect worker nodes, each running Docker. The control plane routes traffic via Pingora. This scales to hundreds of containers without Kubernetes overhead.
bunx @temps-sdk/cli deployments rollback -p my-nextjs-app -e production
Temps promotes the previous healthy deployment and updates routing immediately. Health checks (5-second interval, 2 consecutive successes required) verify the rollback before traffic is fully shifted.
# Stream live runtime logs
bunx @temps-sdk/cli runtime-logs -p my-nextjs-app -f
Check your build logs in the dashboard. Common causes:
tsc --noEmit)bunx @temps-sdk/cli runtime-logs -p my-nextjs-app -f# Install CLI
curl -fsSL https://temps.sh/deploy.sh | bash
# Login
bunx @temps-sdk/cli login
# Create project and connect repository
bunx @temps-sdk/cli projects create -n "my-nextjs-app" -d "Next.js app"
bunx @temps-sdk/cli projects git -p my-nextjs-app \
--owner myorg --repo my-nextjs-app --branch main --preset nextjs -y
# Deploy to production
bunx @temps-sdk/cli deploy my-nextjs-app -b main -e production -y
# Set environment variable
bunx @temps-sdk/cli environments vars set DATABASE_URL "postgresql://..." \
-p my-nextjs-app -e production
# Stream live logs
bunx @temps-sdk/cli runtime-logs -p my-nextjs-app -f
# Add custom domain (HTTP challenge by default; use --challenge=dns-01 for wildcards)
bunx @temps-sdk/cli domains add -d yourdomain.com
# Rollback to previous deployment
bunx @temps-sdk/cli deployments rollback -p my-nextjs-app -e production
Ready to deploy? Get started at temps.sh — self-hosting is free (Apache 2.0), or use Temps Cloud at ~$6/mo.