Move analytics and OpenTelemetry history off your VPS without changing the Temps dashboard or API. Every plan includes managed telemetry, query compute, integrity-checked backups and scheduled engine restore tests.
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 telemetry, history and query compute 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 backup receives integrity verification; engine-level restore tests follow the bounded schedule shown above. A compute hour is one vCPU-hour of actual query work—not a reserved CPU or an hour spent in the dashboard. Cached results and precomputed rollups are free.
Transparent by design
Your apps and dashboard keep using the same endpoints. Moving telemetry to Cloud does not require SDK or query changes.
Generate an enrollment code in Cloud, paste it into Temps, then connect. Cloud never blocks application traffic or local telemetry acceptance. Managed telemetry is uploaded asynchronously, and its queries depend on Cloud.
The writer uploads analytics and OpenTelemetry data, and existing APIs query Cloud transparently. The local pending queue stays bounded.
The fine print, plainly
Yes. Temps remains MIT / Apache 2.0 and free to run on your own infrastructure. Temps Cloud adds a managed telemetry datastore, fleet visibility, managed backups and usage billing without entering your application request path.
No. Instances are unlimited on every managed plan. Pricing follows the genuinely variable resources—telemetry ingest, retention, backup storage and query compute—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.
A compute hour is one vCPU doing query work for one hour, or the equivalent work spread across several cores. It measures the CPU actually consumed by analytics and OpenTelemetry queries—not reserved hardware or time spent viewing the dashboard. Cached results and precomputed rollups do not consume the allowance. Pay-as-you-go remains disabled until you explicitly set a hard monthly cap.
Backup allowances measure compressed data stored for one month, not the source database size. Every backup receives checksum, manifest and object-integrity verification. Plans include bounded engine-level restore tests against disposable databases; additional tests can be enabled on demand with a hard spend cap.
Your applications and databases remain on your infrastructure. When you activate Temps Cloud, the Cloud writer sends analytics and OpenTelemetry data to the managed datastore and the existing Temps APIs query it transparently. The local instance keeps only a bounded pending-upload queue instead of the full telemetry history.
Nothing you build locally becomes obsolete. Managed Cloud extends the same open-source Temps instance.
