Connect unlimited self-hosted instances. Get managed backups, longer telemetry history, AI credits and one place to see health and usage.
Launch terms
14 days free · no card required
No per-seat pricing. No per-instance pricing. PAYG starts off.
Self-hosting is free forever and available today. Temps Cloud is one subscription per account with unlimited connected instances — choose by the data and history your fleet actually needs.
Self-hosted
For running Temps your way
Available now
Starter
For one production stack
Coming soon
Team
Best for teamsFor growing engineering teams
Coming soon
Business
For high-volume platforms
Coming soon
Enterprise
Custom
For regulated and large fleets
Telemetry overage: Starter $0.50 / GB, Team $0.40 / GB, Business $0.30 / GB, only after you enable a hard cap. Backup allowances use compressed GB-month, not source database size. Backup PAYG will remain off until its own hard-cap and reconciliation controls ship. Every managed backup includes one engine-level restore test; manual re-verification is fair-use limited. Included AI credits reset monthly and do not roll over.
Local-first by design
Deploy the open-source binary on your server. It keeps serving applications and storing primary telemetry locally.
Generate an enrollment code in Cloud, paste it into Temps, then connect. Cloud never enters your request path.
Your plan includes telemetry, backups and AI credits. Overage remains explicit, visible and hard-capped.
The fine print, plainly
Yes. Temps remains MIT / Apache 2.0 and free to run on your own infrastructure. Temps Cloud adds fleet visibility, managed backups, usage billing and AI access without entering your application request path.
No. Instances are unlimited on every managed plan. Pricing follows the genuinely variable resources—telemetry ingest, backup storage and AI credits—not the number of servers you connect.
Every new managed account starts with 14 days of Starter access. No card is required, and pay-as-you-go remains disabled unless you explicitly enable it and choose a hard monthly cap.
Credits describe useful product actions rather than provider tokens or dollars. A standard analysis uses one credit and a deep report uses five. Included credits expire monthly; bring-your-own-key calls do not consume them.
Backup allowances measure compressed data stored for one month, not the source database size. Every managed backup includes one engine-level restore test. PostgreSQL supports WAL-based point-in-time recovery; snapshot-based engines such as MongoDB and Redis are restored to a captured backup point. Manual re-verification is available on a fair-use basis so repeated tests cannot create an unbounded infrastructure bill.
Your self-hosted Temps instance remains the data plane. Local ingest and primary telemetry storage stay on your infrastructure; Cloud receives only the managed signals and data you explicitly enable.
Nothing you build locally becomes obsolete. Managed Cloud extends the same open-source Temps instance.
