Frequently Asked Questions

Quick answers to the questions that come up most often.

Getting Started

Which server should I use?

See Choosing a server for concrete recommendations. The short answer: Hetzner CX32 (4 vCPU, 8 GB RAM, ~€9/month) is the best starting point for a solo developer running production apps.

Do I need a domain name?

No, not to get started. Temps assigns a *.temps.sh subdomain for free so you can test without a domain. For production use, you will want your own domain — it costs about €10–15/year.

Does Temps require Docker?

The one-command installer installs Docker for you. If you run the manual installation, Docker is required for running application containers. Temps itself runs as a single binary and does not require Docker to start.

What operating systems does Temps support?

• Ubuntu 20.04+, Ubuntu 22.04 LTS (recommended)
• Debian 11+
• RHEL/CentOS 8+, Amazon Linux 2
• macOS (Intel and Apple Silicon) for local development

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.

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 flat, lifetime) adds team SSO, audit logs, HA databases, and enterprise support. Temps Enterprise (€4,000+) is for large organizations with custom SLAs.

See the pricing page for the full feature comparison.

What does it actually cost to run?

A solo developer running 2–3 production apps:

Compare this to Vercel Pro + Sentry Team + Plausible + FullStory, which can easily be $150–500/month.

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. Check actual usage in Server → Metrics after deploying.

What frameworks does Temps support?

Any framework that runs in a Docker container or via Nixpacks. Auto-detected frameworks include: Next.js, Nuxt, Remix, Astro, SvelteKit, Vite, Create React App, Node.js, Bun, Python (Django, FastAPI, Flask), Go, Ruby on Rails, Laravel, Rust, Java Spring Boot, .NET.

See Supported Frameworks for the full list.

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 the Monorepos guide.

Does it support preview deployments for pull requests?

Yes. Every pull request gets its own preview URL automatically. See Set up preview deployments.

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 apps (running in Docker containers) also restart automatically with the --restart=unless-stopped policy. 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 Postgres, MySQL, Redis, or MongoDB instance 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. Temps creates and configures the container for you.

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. Go to Settings → Team → Invite Member to add teammates. You can set roles (admin, developer, viewer) per member.

Is there SSO / OIDC support?

SSO and OIDC are available in 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?

Application data (container volumes), managed databases, and Temps configuration. 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:

temps deployments rollback --project my-app

See the Rollbacks guide for details.

Updating Temps

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

temps upgrade

Always take a backup first. See the Upgrade guide for the full process including 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

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

Roll back to the previous version:

temps upgrade --rollback

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.