Frequently asked questions

Short answers to the questions people ask before and after installing Temps: which server to buy, what it costs, which frameworks deploy, how databases, domains, backups and upgrades work, and how to move over from Vercel. New to Temps? Start with What is Temps? and the Quickstart; step-by-step task guides are in How-to guides.

Getting started

Which server should I use?

A Hetzner CX33 (4 vCPU, 8 GB RAM, €8.49/month excluding VAT, verified 8 October 2026) is the best starting point for a solo developer running production apps. CX plans are sold only in Germany and Finland; in the US, a 4 vCPU / 8 GB DigitalOcean or Linode server costs about $48/month. See Choosing a server for sizes and prices.

Do I need a domain name?

No, not to get started. The installer's QuickStart mode gives your server an instant <dashed-ip>.sslip.io address (for example console.203-0-113-1.sslip.io for the dashboard and my-app.203-0-113-1.sslip.io for an app) with automatic Let's Encrypt HTTPS. For production, add your own domain — it costs about €10–15/year. See Add a custom domain.

Does Temps require Docker?

Yes. Temps runs your apps, and its own TimescaleDB database, in Docker containers. The installer installs Docker for you if it is missing. The Temps control plane itself is a single binary that runs as a systemd service.

What operating systems does Temps support?

• Ubuntu 22.04 LTS or newer (recommended)
• Debian 11+
• RHEL/CentOS 8+ (Docker may need manual installation steps)
• macOS (Intel and Apple Silicon) for local development

These match the requirements in Choosing a server.

Does Temps run on ARM?

Yes. Temps ships native ARM64 binaries. Hetzner CAX instances (Ampere-based) and AWS Graviton are both supported. The installer detects your architecture automatically.

Is Temps production-ready?

Temps is in public beta: every release so far is a v0.1.0 prerelease (the newest beta is v0.1.0-beta.56), and v0.1.0 GA has not shipped yet. Features in the console carry Stable, Beta or Experimental labels — see Feature maturity for what each label means. Run through the production checklist before sending real traffic.

Cost and pricing

Is Temps free?

Temps Community is free and open-source (MIT/Apache 2.0). You pay for the VPS you run it on, not for Temps itself.

Temps Premium ($399 per organisation per month, unlimited users and servers) is a license for the self-hosted Enterprise Edition binary. It adds per-project firewall and IP access rules, SAML SSO with password login turned off, SCIM, custom roles, deployment approval gates, a tamper-evident audit log and compliance reports. Teams, project roles, OIDC login and the searchable audit log stay free in Community. For an SLA, invoicing or custom terms, talk to us.

See Premium pricing for the full feature list, and the pricing page for Temps Cloud.

What does it actually cost to run?

A solo developer running 2–3 production apps:

Compare this to the hosted tools Temps replaces: Vercel Pro is $20/month, and Plausible ($9) + Sentry Team ($26) + LogRocket (from $176) add $211/month (verified 7 October 2026).

What is the difference between Community and Premium?

Deploying apps

How many apps can I run on one server?

It depends on how memory-hungry your apps are. Rough guidelines:

• 4 GB RAM server → 3–5 small apps
• 8 GB RAM server → 6–10 small apps
• 16 GB RAM server → 12–20 small apps

Each Next.js or Node.js app typically uses 256–512 MB of RAM, and managed databases (Postgres, Redis) add 256 MB–1 GB each. Check actual usage in Server → Metrics after deploying.

What frameworks does Temps support?

Anything that runs in a Docker container or builds with Autopack, Temps' built-in builder. Temps auto-detects Next.js, Vite, Rsbuild, Docusaurus, Python (Django, FastAPI and Flask), Go, Rust, Java, a Dockerfile and Docker Compose from your repository files. Create React App, Express, NestJS, Angular, Astro, Nuxt, Remix, SvelteKit (with SSR), Laravel, Rails, Elixir and .NET deploy with a preset you pick (Create React App, or Autopack for Node.js, PHP, Ruby, Elixir or .NET). If your repo has a Dockerfile, Temps uses it, which covers anything else.

See Supported platforms for the full list.

How do I deploy a Next.js app on Temps?

Connect your repository under Projects → New Project. Temps detects Next.js, runs your build script and starts the app with next start; you don't need output: 'standalone'. The app goes live with HTTPS once its health check passes. See Deploy Next.js.

Can I deploy a Docker image directly?

Yes. If your repo has a Dockerfile, Temps uses it automatically. You can also point to an image from a registry.

Can I deploy a monorepo?

Yes. Set the App Directory field in project settings to the subdirectory containing your app. See Deploy a Project for a walkthrough.

Does it support preview deployments for pull requests?

Yes, per branch. With preview environments turned on, every pushed branch other than production gets its own preview environment and URL (for example https://my-app-feature-login.yourdomain.com), and later pushes redeploy to the same environment. See Set up preview deployments.

Can I migrate from Vercel to Temps?

Yes. Export your environment variables from Vercel, create the project in Temps from the same repository, deploy and check the app on its Temps URL, then move DNS. Vercel-specific storage needs a replacement, for example Temps-managed PostgreSQL, Redis or S3-compatible storage. See Migrate from Vercel.

What happens to running apps if Temps crashes or my server restarts?

The installer creates a systemd service that restarts Temps automatically on crash or reboot. Your app containers run with Docker's always restart policy, so they come back when Docker starts. See the upgrade guide and troubleshooting for recovery scenarios.

Databases

Does Temps come with a database?

Temps uses PostgreSQL with TimescaleDB internally for its own data. For your apps, you can:

• Use Temps Managed Services — provision a PostgreSQL, MariaDB, Redis, MongoDB or S3-compatible service on the same server
• Connect an external database — Neon, Supabase, PlanetScale, or any hosted database
• Run your own — point DATABASE_URL to any reachable Postgres instance

Do I need to set up the database myself?

For Temps's own database (TimescaleDB): the one-command installer does this automatically.

For your app's database: use Managed Services → New Service in the Temps dashboard, then link the service to your project. Temps creates the container and injects connection variables (for PostgreSQL, POSTGRES_URL). See Set up managed services.

How do I migrate my existing database into Temps?

Use pg_dump and pg_restore. The migration guides for Vercel, Railway, Render, and Fly.io all include step-by-step database migration instructions.

Domains and SSL

Do I need a wildcard domain?

A wildcard DNS record (*.yourdomain.com) lets Temps assign a unique subdomain to each project automatically. Without it, you can still add custom domains manually to each project — Temps provisions individual SSL certificates via HTTP-01 challenge.

How does SSL work?

Temps provisions SSL certificates from Let's Encrypt automatically. Certificates renew before they expire — you never need to manage this manually. Port 80 must be open on your server for HTTP-01 challenges. For wildcard certificates, you need a DNS provider configured (Cloudflare, Route53, DigitalOcean DNS).

Can I use a custom domain for each app?

Yes. In Project → Settings → Domains, add any domain or subdomain. Temps handles the certificate.

Teams and access

Can multiple people use the same Temps instance?

Yes, with unlimited users and no per-seat fees. An admin creates each user account under Settings → Users; there are no email invitations. Instance roles are Admin and User. Group users into teams to give them a project role: Owner, Admin, Deployer or Viewer. See Manage team access.

Is there SSO / OIDC support?

Yes. OIDC login (Google Workspace, Okta, Auth0, Keycloak and other OpenID Connect providers) is free in Community. SAML 2.0, requiring SSO for every user with password login turned off, and SCIM provisioning are part of Temps Premium. See the SSO guide.

Backups and recovery

How do I back up my apps?

Temps has a built-in backup system that works with any S3-compatible storage (Cloudflare R2, Backblaze B2, AWS S3, MinIO). See Set up backups and monitoring for a step-by-step guide.

What gets backed up?

Managed PostgreSQL, MariaDB, Redis, MongoDB and S3/MinIO services, plus Temps' own control-plane database, always to an S3-compatible target. App containers have no persistent volumes, so there are no app files to back up; keep state in a managed service. See the Backups reference for a full breakdown.

How do I roll back a deployment?

Click Redeploy next to any previous deployment in the dashboard, or use the CLI with the ID of the deployment to return to:

bunx @temps-sdk/cli deployments rollback --project my-app --to 456

See the Rollbacks guide for details.

Updating Temps

How do I update Temps when a new version comes out?

Until v0.1.0 ships, every Temps release is a prerelease, so a bare temps upgrade (which looks for a stable release) fails with "No stable releases found". Pin the release you want instead:

temps upgrade --version v0.1.0-beta.56

Always take a backup first. See the Upgrade guide for release channels, pre-upgrade checks and rollback steps.

How do I know when a new version is available?

temps --version          # Current version
temps upgrade --check    # Check for available updates

On current releases temps upgrade --check has the same channel limitation as temps upgrade, so also watch the releases page. Subscribe to the GitHub releases page for notifications.

Troubleshooting

My deployment failed — where do I look?

1. Open the failed deployment in the Temps dashboard
2. Click Logs to see the build and runtime output
3. Check the debug a failed deployment guide

Something broke after a Temps upgrade

Temps does not support an automatic rollback flag. To downgrade, reinstall a specific version:

temps upgrade --version v0.1.0-beta.55

Replace v0.1.0-beta.55 with the version you were running before. Then restore from your pre-upgrade backup if needed. See Upgrade guide.

I can't reach my app after deploying

Common causes in order of frequency:

1. Health check failing — your app is not listening on the expected port. Check deployment logs.
2. DNS not propagated — wait up to 48 hours, or verify with dig yourdomain.com
3. Port 80 or 443 blocked — check your server firewall rules
4. SSL certificate not issued — port 80 must be open for Let's Encrypt

See the Troubleshooting guide for detailed steps.