[opensourcedex]

Temps is a free, open source server & vm management project written in Rust and released under Apache-2.0. It has 756 GitHub stars, 59 forks and 14 open issues, and was last pushed 4 hours ago. On this registry it ranks #9 of 10 tracked projects in Server & VM Management, with 5 head-to-head comparisons available. It gained 8 stars over the last 6 tracked days.

What is Temps?

What it is

Temps is an Apache-2.0 licensed Rust binary that combines deployment, monitoring, analytics, error tracking, email, OpenTelemetry, sandboxes, and an AI gateway in one self-hosted system. It is positioned as an alternative to Vercel, Sentry, PostHog, Pingdom, Resend, and E2B.

It solves the problem of operating many separate services for web applications and AI agents. A team can run one binary that exposes deployment, uptime, session replay, error tracking, logs, email, and sandbox operations through a dashboard and a CLI. It lives in the Rust infrastructure ecosystem.

Key capabilities

  • Temps provides 440+ CLI operations across 69 groups, so users can list projects, deploy applications, query analytics, and run migrations from the command line or through agents.
  • It includes web analytics, funnels, visitor tracking, and rrweb session replay without sending data to external services.
  • It offers Sentry-compatible error tracking by pointing the official Sentry SDK at a Temps DSN to collect error groups, stack traces, source context, and alerts.
  • It runs an AI gateway with OpenAI-compatible access to OpenAI, Anthropic, xAI, and Google Gemini, while storing provider keys encrypted and recording tokens, latency, error rate, and estimated cost per model.
  • It provides uptime monitors, status timelines, and alerts for deploy failures, runtime crashes, certificate expiry, and backup health.
  • It runs workflow sandboxes on Firecracker microVMs, each with its own kernel, or on Docker as the default backend.
  • It supports transactional email through sender domains with DKIM records and can use AWS SES, Scaleway, or any SMTP relay.

Who uses it and how

  • Teams can use Temps as a self-hosted application platform by deploying projects, managing environments, and adding domains from the dashboard or CLI.
  • AI coding agents such as Claude Code, Codex, and OpenCode can use the shipped skills to deploy, inspect traces, run migrations, and add domains.
  • Developers can use workflow sandboxes to run agent tasks against a repository with platform-wide skills and MCP servers injected automatically.
  • Operators can centralize observability by sending OTLP traces, metrics, and logs to Temps, then use alerts and an AI chat grounded in project telemetry.

Getting started

Install Temps with curl -fsSL https://temps.sh/deploy.sh | bash, then use bunx @temps-sdk/cli for projects, deployments, and analytics. Firecracker sandboxes are enabled with temps firecracker setup.

When to use it — and when not to

Temps is useful when one self-hosted Rust binary should replace the separate products it lists as alternatives, such as Vercel, Sentry, PostHog, Pingdom, Resend, and E2B, and when the operator can run Docker, Let's Encrypt TLS, SMTP relays, and provider keys on their own infrastructure. The repository is new, with zero listed contributors and fourteen open issues, so teams needing a long support history may prefer established services.

project readme (upstream, from github) — read inline

Website · Docs · Discussions

curl -fsSL https://temps.sh/deploy.sh | bash

Features

AI-native — 440+ operations any agent can drive

Every operation in the dashboard is also a CLI command — 440+ of them across 69 groups — and Temps ships the skills that teach an agent how to use them. Drop them into Claude Code, Codex, OpenCode, or any harness that reads .claude/skills/, and your agent can deploy, inspect traces, run migrations, or add a domain without you writing the glue.

bunx @temps-sdk/cli projects list
bunx @temps-sdk/cli deploy my-app --environment production
bunx @temps-sdk/cli analytics ai-agents -p my-app --period 7d

Temps runs those agents for you too: workflow sandboxes execute Claude Code, Codex, or OpenCode against your repository, with platform-wide skills and MCP servers injected automatically.

AI Chat — grounded in your own telemetry

Ask about your project and the answer comes from your data — traces, metrics, alarms, deployments, and revenue — not from a generic model guess. It is read-only by default: write actions are opt-in, and even then the assistant proposes the change and waits for you to confirm.

AI Gateway — one endpoint, your own keys

Bring your own provider keys (OpenAI, Anthropic, xAI, Google Gemini) and call them all through one OpenAI-compatible endpoint — swap the base URL, keep the SDK you already use. Keys stay encrypted on your server, and every request is attributed: tokens, latency, error rate, and estimated cost per model.

Web Analytics & Session Replay

Web analytics with funnels, visitor tracking, and session replay (rrweb) built in — no external services, no data leaving your servers. This is what no other self-hosted PaaS has.

Uptime Monitoring & Alerts

Uptime monitors with status timelines, plus alerts for deploy failures, runtime crashes, certificate expiry, and backup health. Get notified before problems reach users.

Error Tracking — Sentry-compatible

Drop-in Sentry replacement: point the official Sentry SDK at your Temps DSN and get error groups, stack traces with source context, and alerts. No per-event pricing.

Request Logs & Proxy Visibility

Every HTTP request logged with method, path, status, response time, and routing metadata — including per-AI-crawler traffic (OpenAI, Anthropic, Perplexity, Google…). Runs on Cloudflare's Pingora engine with auto TLS via Let's Encrypt (HTTP-01 & DNS-01).

Transactional Email

Add sender domains with DKIM records through the UI and send via @temps-sdk/node-sdk — or plug in AWS SES, Scaleway, or any SMTP relay.

OpenTelemetry — traces, metrics, logs & alerts

Point any OTLP exporter at Temps and get distributed traces, metrics, and structured logs in the same place as everything else. Traces show per-span latency and errors across services; metrics keep your golden signals; alerts fire off those metrics and land in one queue you can acknowledge or resolve. No Grafana, Prometheus, Jaeger, or Loki to run.

AI Sandboxes — Firecracker microVMs, self-hosted

Real hardware-level isolation, not just containers. Sandboxes run on Firecracker microVMs — the same tech behind AWS Lambda — with a Docker backend as the default. Run temps firecracker setup and Temps routes sandboxes to microVMs automatically; each one gets its own kernel, so untrusted agent-generated code never shares a kernel with your host.

A drop-in SDK. @temps-sdk/sandbox is compatible with the @vercel/sandbox shape — switch providers by changing the import and base URL:

import { Sandbox } from '@temps-sdk/sandbox'

const sandbox = await Sandbox.create({
  source: { type: 'git', url: 'https://github.com/example/repo.git', revision: 'main' },
})

const { stdout } = await sandbox.exec(['npm', 'test'])
const url = sandbox.domain(3000) // live preview of a dev server inside the VM

Password-protected previews. Every sandbox port can be exposed on a public preview URL and locked behind a generated password:

bunx @temps-sdk/cli sandbox password sbx_abc123 --rotate --length 32
bunx @temps-sdk/cli sandbox password sbx_abc123 --clear   # open it back up

Share a running branch without shipping it to the world.

Also available via CLI and REST API. What you'd otherwise pay E2B, Daytona, or Vercel Sandbox for.

Each sandbox gets a shell, a preview URL template for any port it binds, and a timeline of everything that happened to it:

Everything in One Dashboard

Visitors, errors, deployment status, and monitoring health per project —

readme truncated — read the full docs on github

Frequently asked questions

Is Temps free to use?

Temps is open source under the Apache-2.0 licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does Temps do?

One self-hosted binary replaces Vercel, Sentry, and analytics tools

What is Temps written in?

Temps is primarily written in Rust. Its source is publicly available at https://github.com/gotempsh/temps, and it has 756 GitHub stars.