# Understand what must be ready before a service launches

Canonical: https://savrn.com/cloud/roadmap

SAVRN Cloud · Coming soon. Public documentation and a browser simulation are available; connected services are not yet available.

SAVRN Cloud’s roadmap describes a direction for connected research services, not an announcement that every screen represents an available product. The public interactive preview is available now with browser-local simulation. Inference, compute, training and other connected capabilities are Coming soon, with availability and terms to be announced separately.


## Use the preview to examine the whole journey

The console brings together discovery, projects, scoped work, execution examples and review. This makes dependencies visible before a connected release. A team can inspect how a deployment leads to a request receipt or how an evaluation supports candidate promotion. Completing those local paths demonstrates the interface and state transitions, not the availability of backend services.

## Release bounded capabilities

A useful first connected service needs a supported configuration, clear limits and an operational owner. Additional features should be qualified individually. Text generation does not establish tool execution or streaming; a trusted worker does not establish general customer-code sandboxing. The planned progression favors explicit capability boundaries that customers can understand and developers can test.

## Make expansion depend on evidence

The path toward evaluations, adaptation and broader workflow execution requires more than adding endpoints. It needs reproducible inputs, durable artifacts, measured behavior, enforceable authorization and resource reconciliation. The same principle applies to new providers and owned infrastructure: each placement must establish the controls and operating responsibilities needed by its intended workload.

## Keep release information distinct

A documentation revision, a preview improvement, a qualified capability and a customer launch are different events. Future release notes should identify which behavior changed and whether existing integrations need action. Availability should describe current service access rather than a planned date inferred from a roadmap. No launch schedule, capacity commitment or customer price is established by this preview.

## What you can explore today

Review the intended capability progression and explore its simulated workflows.

## Before this service launches

Connected releases will need service-specific qualification and explicit availability, limits, support and commercial terms.

## The customer outcome

The intended outcome is a clear basis for evaluating readiness without confusing an interactive concept, a tested capability and an available service.

## Related documentation

- [What is available](https://savrn.com/cloud/docs/start-service-status)
- [Changelog and operational status](https://savrn.com/cloud/docs/resources-changelog-status)
- [Deployment and trust matrix](https://savrn.com/cloud/docs/trust-deployment-matrix)
- [Explore the roadmap](https://savrn.com/cloud/console/#/roadmap): Review intended capability stages in the public preview.