Feature maturity

Temps labels features by the compatibility promise attached to them. The label describes how much a feature may change between releases; it is not a claim that a feature can never have a bug.

Stable features do not carry a badge in the console. Beta and Experimental features remain fully visible and usable, with a badge beside their navigation item and page title. Features that haven't shipped yet are on the roadmap, not in this list.


Stable

This works, and its public surface will remain compatible within 0.1.x releases.

  • HTTP API shapes, CLI flags, and configuration keys remain compatible within 0.1.x.
  • Database migrations preserve your data across upgrades.
  • Regressions are treated as release-blocking.

Beta

This works and we test it, but the data model or API may still change between releases.

  • The feature is functional and covered by tests.
  • Upgrades preserve platform data, while feature-specific schemas may be reshaped or migrated lossily.
  • Breaking changes are documented in the changelog.

Experimental

This is under active development. It may change substantially or be removed, so do not build critical workflows on it yet.

Experimental features are not hidden or disabled. The badge exists so you can make an informed decision while still trying the feature and giving feedback.


Current labels

These are the labels in the registry shipped with v0.1.0-beta.57, the latest release. Nightly builds can differ, so check your own instance with the registry endpoint after an upgrade.

Stable: deployments, projects and environments, environment variables, managed services, backups, the proxy, domains, authentication, API keys and RBAC, logs, transactional email, uptime monitoring, blob storage, the KV store, feature flags, audit logs, the CLI and the core console.

FeatureLabelWhy it is not Stable yet
Web analyticsBetaThe analytics data model and query implementation are still being hardened.
Session replayBetaFunctional, but unit coverage is still growing.
Error trackingBetaEvent fidelity and ingest quota behaviour are still being hardened.
OpenTelemetry traces and metricsBetaVolume controls and storage behaviour may still change.
FunnelsBetaNo dedicated end-to-end coverage yet.
Performance monitoringBetaLimited coverage and no dedicated end-to-end scenario.
Dashboards and metrics explorerBetaNo dedicated end-to-end coverage yet.
Alert rules and metric alertsBetaNo dedicated end-to-end coverage yet.
Uptime monitors and status overviewBetaNo dedicated end-to-end coverage yet.
ScreenshotsBetaNo dedicated end-to-end coverage yet.
Notifications and webhooksBetaNo dedicated end-to-end coverage yet.
Email trackingBetaNo dedicated end-to-end coverage yet.
TeamsBetaPartial RBAC coverage, no dedicated end-to-end scenario.
Database browserBetaReads live service data; no end-to-end coverage yet.
Importers from other platformsBetaImporter compatibility may change.
Service templatesBetaNative curated service templates support one application container with Temps-managed service bindings; multi-container template workloads are not available yet.
Multi-node worker joinBetaWorker join is tested end to end; multi-node hardening is in progress.
IP access and geo controlsBetaNo dedicated end-to-end coverage yet.
AI chatExperimentalThe interaction model is still being designed.
AI agents and workflowsExperimentalThe agent execution model is in active development.
AI gatewayExperimentalRate limiting and cost attribution are not complete.
AI foundation and API toolsExperimentalThe tool contracts are not frozen.
Embeddings and memoryExperimentalMinimal coverage and an evolving contract.
Agent execution sandboxExperimentalMinimal coverage; may change substantially.
Sandboxes and preview workspacesExperimentalPersistent preview workspace semantics are not complete.
Database HA failoverExperimentalFailover semantics are not hardened.
Revenue trackingExperimentalNo dedicated end-to-end coverage.
Plugin systemExperimentalThe plugin SDK boundary is still moving.
Vulnerability scanningExperimentalMinimal coverage; may change substantially.
Attack-mode CAPTCHAExperimentalMinimal coverage.
Static file hostingExperimentalNo automated test coverage yet.

Features only in nightly builds

A feature can carry a maturity label before it reaches a beta or stable release. Its docs page says so, and the label describes the nightly build it is in, not a release you can install from the stable or beta channel.

FeatureRegistry keyLabelWhere it stands
Projects and Services: group Services that ship together under a Project so they share a repository, environment variables and path routesproject-groupsExperimentalMerged into upstream main on 14 October 2026 and available in nightly builds. Not in a beta or stable release, and not in the published CLI. Its registry reason reads: grouping services into projects is an experiment, and naming and inheritance may change or be removed.

Where the label comes from

Every release ships a build-time feature maturity registry. The console, the OpenAPI description, and the Temps CLI read the same registry so the promise is consistent across interfaces.

Because the registry is built into the binary, the labels always describe the version you are running rather than the latest release. To read the registry for your own instance:

curl -H "Authorization: Bearer YOUR_API_TOKEN" \
  "https://your-instance/api/v1/platform/feature-maturity"

Each entry carries the feature key, its maturity, and the reason for that label:

{
  "key": "session-replay",
  "maturity": "beta",
  "reason": "Session replay is functional but its unit coverage is still growing.",
  "docs_path": "https://temps.sh/docs/feature-maturity"
}

You will also see the same promise surface in three other places:

  • The console — a Beta or Experimental badge beside the sidebar entry and page title, with the reason in its tooltip.
  • The CLI — command groups backed by a non-stable feature print a one-time notice before running.
  • The OpenAPI description — non-stable operations carry an x-maturity extension, so generated clients can surface the same warning.

Stable features are intentionally unlabelled everywhere. The absence of a badge is the stable promise, not missing metadata.

Last updated

Was this page helpful?