Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1,060 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation


curl -fsSL https://temps.sh/deploy.sh | bash
Importing a public repository in Temps — framework presets are auto-detected before deploy

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.

Temps AI chat diagnosing a checkout latency spike from the project's own traces, metrics and revenue data

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.

Temps AI Gateway — BYOK provider keys behind one OpenAI-compatible endpoint Temps AI Gateway usage analytics — requests, tokens, latency, error rate and estimated cost

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.

Temps web analytics — visitors, sessions, pages, funnels

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.

Temps uptime monitoring — status timeline, uptime percentage, response time

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.

Temps error tracking — error groups with events and timelines

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).

Temps proxy request logs with AI agent filtering

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.

Temps email providers — SMTP, Scaleway and AWS SES

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.

Temps distributed traces — per-request latency, span counts and errors across services Temps OpenTelemetry metrics — request rate, latency, database and cache signals Temps structured logs — severity, service and message, correlated with traces Temps alerts — firing, acknowledged and resolved alarms across metrics, containers, uptime and databases

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.

Temps sandboxes — running sandboxes with copy-paste CLI, REST and SDK snippets

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

Temps sandbox detail — Docker/Firecracker backend, in-browser command runner, preview URL template and password-protected previews

Everything in One Dashboard

Visitors, errors, deployment status, and monitoring health per project — one place instead of six browser tabs.

Temps projects dashboard — all projects with visitors and status

Git Push to Deploy & Managed Services

Push to Git and Temps builds, deploys, and creates preview URLs with zero-downtime rollouts — any language, auto-detected. Provision Postgres, Redis, S3 (MinIO), and MongoDB alongside your apps; creation, backups, and teardown are handled for you.

Works with your stack

Next.js Vite Go Python Rust Java .NET NestJS Docker

Any language, any framework. Auto-detected or bring your own Dockerfile.


Already running somewhere else?

Temps imports your existing setup instead of asking you to rebuild it. Point the wizard at your current platform and it brings over the whole thing — apps, databases with their data, domains, and environment variables.

Self-hosted platforms

Coolify Dokploy CapRover Portainer Kamal Kubernetes Docker

Hosted platforms

Vercel Netlify Railway Render Fly.io

Import runs from the dashboard — the platform tiles sit right in your projects page header.


Quick Start

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

Tested on: Ubuntu 24.04 / 22.04  |  Also works on macOS

Prefer not to manage a server? Temps Cloud runs Temps for you on managed infrastructure.


What Temps replaces

What you get Instead of paying for
Git deployments + preview URLs Vercel / Netlify / Railway ($20+/mo)
Web analytics + funnels PostHog / Plausible ($0-450/mo)
Session replay PostHog / FullStory ($0-2000/mo)
Error tracking Sentry ($26+/mo)
Traces, metrics & logs (OpenTelemetry) Grafana Cloud / Datadog ($0-500+/mo)
Uptime monitoring Better Uptime / Pingdom ($20+/mo)
Managed Postgres/Redis/S3 AWS RDS / ElastiCache ($50+/mo)
Transactional email + DKIM Resend / SendGrid ($20-100/mo)
AI code-execution sandboxes E2B / Daytona / Vercel Sandbox ($150+/mo + usage)
AI gateway + usage/cost tracking OpenRouter / Helicone / LangSmith ($0-200+/mo)
Request logs + proxy Cloudflare ($0-200/mo)
Total with Temps $0 (self-hosted)

Temps vs. Alternatives

Feature Temps Coolify Dokploy Kamal Railway Render Vercel
Self-hosted & open source Yes Yes Yes Yes No No No
Single binary install Yes No No CLI tool -- -- --
Git push deploy Yes Yes Yes No Yes Yes Yes
Preview deployments Yes Yes Yes No Yes Yes Yes
Auto TLS (HTTP-01 + DNS-01) Yes Yes Yes Yes Yes Yes Yes
Docker Compose support Yes Yes Yes No -- -- --
One-click template library No 280+ Yes No Yes Yes Yes
Web analytics Yes No No No No No Paid add-on
Session replay Yes No No No No No No
Error tracking (Sentry-compatible) Yes No No No No No No
OpenTelemetry traces + metrics + logs Yes No No No No No Traces (paid)
Uptime monitoring Yes No No No No No No
Transactional email + DKIM Yes No No No No No No
Code-execution sandboxes (API) Yes No No No No No Sandbox (usage-based)
AI gateway (BYOK) + assistant Yes No No No No No AI Gateway (paid)
Managed Postgres / Redis Yes Yes Yes No Yes Yes Partner add-ons
S3-compatible storage Yes No No No No No Blob (paid)
Multi-node / clustering Yes Yes Swarm Yes Managed Managed Managed
Edge functions / global edge network No No No No No No Yes
Per-seat fees No No No No $20/user (Pro) Per-user $20/seat (Pro)

Where the alternatives win. Coolify and Dokploy have one-click template libraries (280+ apps on Coolify) that Temps doesn't have yet, and both have far larger communities — Coolify alone has 56k+ GitHub stars, while Temps is the newest project on this list. Kamal is the simpler choice if all you want is zero-downtime Docker deploys driven from a CLI. Vercel and the other managed platforms give you a global edge network, edge functions, and DDoS absorption that a single VPS can't match — and they run the infrastructure for you, which is real value if you never want to think about a server.

Detailed, regularly updated comparisons: temps.sh/compare


Tech Stack

  • Backend: Rust, Axum, Sea-ORM, Pingora (Cloudflare's proxy engine), Bollard (Docker API)
  • Frontend: React 19, TypeScript, Tailwind CSS, shadcn/ui
  • Database: PostgreSQL + TimescaleDB
  • Architecture: 30+ workspace crates, three-layer service architecture

SDKs

Package Description
@temps-sdk/node-sdk Platform API client + Sentry-compatible error tracking
@temps-sdk/react-analytics React analytics, session replay, Web Vitals, engagement tracking
@temps-sdk/kv Serverless key-value store
@temps-sdk/blob File storage (S3-compatible)
@temps-sdk/cli Command-line interface
Quick examples

Analytics -- wrap your React app, everything else is automatic:

import { TempsAnalyticsProvider } from '@temps-sdk/react-analytics';

export default function App({ children }) {
  return <TempsAnalyticsProvider>{children}</TempsAnalyticsProvider>;
}

Error tracking -- Sentry-compatible, drop-in replacement:

import { ErrorTracking } from '@temps-sdk/node-sdk';

ErrorTracking.init({ dsn: 'https://key@your-instance.temps.dev/1' });

try {
  riskyOperation();
} catch (error) {
  ErrorTracking.captureException(error);
}

KV store -- Redis-like API, zero config:

import { kv } from '@temps-sdk/kv';

await kv.set('user:123', { name: 'Alice', plan: 'pro' }, { ex: 3600 });
const user = await kv.get('user:123');

Blob storage -- upload and serve files:

import { blob } from '@temps-sdk/blob';

const { url } = await blob.put('avatars/user-123.png', fileBuffer);
const files = await blob.list({ prefix: 'avatars/' });

Community

If Temps saves you a SaaS bill, a star helps other people find it.


Star History

Star History Chart

Contributing

We welcome contributions. See CONTRIBUTING.md for guidelines.

git clone https://github.com/gotempsh/temps.git
cd temps
cargo build --release

License

Dual-licensed under MIT or Apache 2.0.

License GitHub Release Rust GitHub Stars


About

AI-native open-source alternative to Vercel + Sentry + PostHog + Pingdom + Resend + E2B. 440+ CLI operations with drop-in skills for Claude Code, Codex & OpenCode — deployments, analytics, session replay, error tracking, OpenTelemetry, email, sandboxes & AI gateway in one self-hosted Rust binary.

Topics

Resources

Contributing

Security policy

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages