Temps is not quietly polishing a settled hosting product. ToolVitals sees 18 release events in 30 days and 30 GitHub releases in 90 days, while the recent GitHub release pages are still marked pre-release. That is the signal: an OSI-approved OSS deployment platform trying to turn a Vercel-style pitch into a broader self-hosted control plane before the API settles.

The official site sells a sharp idea: one self-hosted binary for deployments, analytics, error tracking, monitoring, session replay, and managed databases. The GitHub README uses similar language, calling Temps an open-source, self-hosted deployment platform for deploying, observing, and scaling from a single binary.

That breadth makes the release stream more interesting than a plain version counter. v0.1.0-beta.21 added OIDC SSO, console extension points, and an admin gate, then fixed workflow trigger behavior and patched an OIDC account-takeover path tied to unverified email linking. v0.1.0-beta.19 added manual non-git project creation and fixed AI gateway auth, static deployment routing, and analytics bot noise. v0.1.0-beta.18 focused on backup scope, S3 lifecycle retention, and splitting public ingest from the admin console listener.

This is not just dependency churn. Temps is pushing into the dull control-plane work that matters once a self-hosted tool leaves the demo box: SSO, role mapping, admin access controls, backup retention, listener separation, deployment routing, and analytics correctness.

The bet is clear. Temps is not only replacing a deployment host. It wants to replace the pile of SaaS tabs around deployment: Sentry, analytics, replay, uptime checks, transactional email, and managed services.

What ToolVitals can and cannot infer

ToolVitals gives Temps a hot score of 202.0, a health score of 77, a shipping score of 95, and a ToolVitals score of 87. It also records 456 GitHub stars and 90 data confidence. The license signal in the payload is Apache-2.0, and the openness class is OSI-approved OSS.

Those metrics do not prove the platform works well in production. ToolVitals can see releases, stars, SSL, uptime, and related public activity signals. It cannot see code quality, upgrade safety, support quality, user satisfaction, revenue, install success rate, or whether managed databases and session replay behave well under real load.

There is also a missing signal here: github_commits_30d is null in the payload. That means the release cadence is strong, but ToolVitals is not making a 30-day commit-count claim for this run.

The hosting comparison

Temps is tiny next to the bigger hosting peers in the related-tools data. Coolify has 55,951 stars and Nextcloud has 35,517. Temps has 456.

But the release pattern flips the comparison. Temps shows 18 release events in 30 days. Nextcloud shows 7. Coolify shows 1.

That does not make Temps healthier than Coolify or Nextcloud. It means Temps is in a much earlier, noisier phase where rapid beta shipping is the story. Mature tools can be quiet because they are stable. Beta tools are loud because they are still deciding what they are.

Recommendation

If your team wants self-hosted deployment plus observability, and you can tolerate beta software, evaluate Temps against one non-critical service. The recent release work targets the right boring problems: SSO, admin isolation, backups, routing, and auth correctness.

If you need a calm production hosting layer today, compare Temps against more mature hosting tools first. Treat Temps as a fast-moving candidate to test, not the default platform for critical workloads yet.

Sources