AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
AI 기반 오픈소스, Vercel·Sentry·PostHog·Pingdom·Resend·E2B 대체 솔루션
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 rep
개발 도구Rust · TypeScriptGitHub @gotempsh직접 설치운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
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.
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Website · Docs · Discussions
Temps is one self-hosted binary that deploys your apps and runs everything around them: databases, analytics, error tracking, traces, logs, uptime, email, AI sandboxes and an AI gateway. Open source, on your own server.
curl -fsSL https://temps.sh/deploy.sh | bash
Run it on a fresh Ubuntu 24.04 or 22.04 server. It installs Docker if it is missing, runs PostgreSQL, sets Temps up as a service with automatic HTTPS, and prints your console URL and admin password. No domain yet? Pick quick mode and you get https://console.<server-ip>.sslip.io.
Quickstart · Choosing a server · Rather not run a server? Temps Cloud
Temps ships skills that teach coding agents (Claude Code, Codex, Cursor, OpenCode and others) to install Temps on a server, connect to it and run every console operation through the CLI. Add them to your agent:
bunx skills add gotempsh/temps --skill temps temps-platform-setup
No server yet? Give your agent a fresh Ubuntu server it can reach over SSH and ask:
Use the Temps skills to install Temps on [email protected] in quick mode, connect the CLI to it, then deploy this repository and tell me its URL when it is live.
It runs the official installer over SSH, leaves the generated admin password and API key on the server, and gives you a browser link to approve the CLI login, so no credential ever passes through the chat.
Already running Temps? Connect the CLI to it, then ask your agent:
bunx @temps-sdk/[email protected] login https://console.your-server.example
Use the Temps skill to verify my connection and list the services on this instance. Do not make any changes.
Use the Temps skill to deploy this repository to Temps and tell me its URL when it is live.
For an agent that runs unattended, open Connect your coding agent in the console (/setup/ai): it creates a dedicated API key and checks that the agent's first request arrives.
Skills · CLI · MCP servers
Everything else is in the docs at temps.sh/docs:
Temps sends anonymous usage events (a random instance ID, event names such as deploy_succeeded, and counts) so the maintainers can see whether self-hosted installs work. It never sends emails, IPs, repository names, domains or anything you typed, and your application data never leaves your server. Turn it off in Settings › Telemetry, or for a whole host with TEMPS_TELEMETRY=0. Details
Questions and ideas in Discussions, bugs in Issues. Contributions are welcome: see CONTRIBUTING.md.
Dual-licensed under MIT or Apache 2.0. Forks and derivative works are welcome, including rebranded and commercial distributions, as long as they keep the copyright, license and attribution notices the chosen license requires. See NOTICE.
temps.sh | Documentation | GitHub
English | 简体中文 | Español | Français | Deutsch | 日本語 | Português