Changelog and operational status

SAVRN Cloud · Coming soon · Public preview · Browser-local simulation · No live compute or payments

Read the public preview boundary

This documentation describes the public SAVRN Cloud interactive preview. Connected services are Coming soon. Models, people, resources, metrics and results are synthetic. Preview actions make no model or cloud API calls, create no paid compute and process no payments. Workspace state remains in this browser profile.

Use Roadmap to review intended stages and Operations to inspect local activity. A simulated deployment transition or completed sample is an event in the demonstration, not a production incident update.

Manage your preview workspace

Settings provides workspace name, proposed retention and preferred placement. Save local preferences stores those choices. Export demo session preserves labeled state. Reset demonstration, followed by Reset local state, restores the starting fixtures. This is distinct from terminating supplier resources.

The 7-, 30- or 90-day retention choice is a policy preview; browser state remains until reset or cleared. No automatic deletion is scheduled.

Before connected services launch

Maintain separate records for documentation edits, software releases, service incidents and capability qualification. A documentation date does not establish recent execution verification. Publish affected offers, start time, impact, workaround and recovery state for actual incidents. Link operational claims to evidence and a responsible owner. Preserve old contract versions and migration guidance. Mark unsupported or stale instructions explicitly instead of leaving an apparently current quickstart attached to a retired service.

23 September 2026: initial preview scope

The initial SAVRN Cloud preview at savrn.com/cloud/ covers 21 service and administration areas and a collection of 40 documentation guides. Its scope includes model discovery, playground requests, projects, deployment lifecycles, evaluations, datasets, training candidates, sandbox tasks, Work Orders, approvals and usage review. The records and results are demonstrations of those workflows.

This preview does not connect a model provider, allocate a GPU, execute a training job or process a payment. Its fictional models and synthetic measurements are not performance claims or inventory observations. This dated entry records the preview's documented scope; it is not an uptime report, a capacity attestation or an announcement that connected execution has launched.

How later updates should be interpreted

A documentation update may correct an explanation or add an example without changing any service capability. A preview update may change a browser workflow or its sample records. A future connected-service release would need to identify the eligible offer, verified functionality, access requirements, limits and support boundary. These should be recorded as different kinds of change.

Operational incidents belong to services that actually execute work. A production status entry should describe affected offers, customer impact, the timing of the event and the verified recovery state. Simulated incident controls and resource transitions in the current preview are practice records, so they cannot establish either a real outage or a restoration of service.