# Keep the research workflow portable as compute changes

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

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

SAVRN Cloud’s architectural direction is to retain control of the project, workflow and evidence layer while qualifying different ways to execute work. The goal is continuity as research requirements and infrastructure evolve. The public preview illustrates the records and interactions. Connected service architecture and placement options are Coming soon.


## Separate decisions from execution

Projects, approvals, budgets and release decisions belong to the layer that determines what work may occur. Inference runtimes, training jobs and task execution belong to the layer that performs it. The planned boundary allows an execution choice to change without discarding the project’s purpose, authorization history or the evidence used to accept its results.

## Connect evidence across the lifecycle

A model catalog entry, a qualified configuration, an offer, a deployment and a run are different records. Dataset and environment revisions add the context needed to interpret an experiment. The preview exposes these distinctions through local examples. In a connected implementation, stable identity and access-controlled links would make the chain understandable without exposing private operational or research information.

## Qualify the rented-to-owned path

The planned approach starts with suitable rented execution and develops an owned-placement path where justified. Portability involves model artifacts, runtime behavior, storage, networking, policy and operations. It should be demonstrated with the relevant workload at the destination. A common interface can reduce integration work, but it cannot make different providers or machines equivalent by declaration.

## Define sovereignty through specific controls

Ownership of software and infrastructure can support greater control, but each institutional requirement still needs evidence. Processing location, logs, backups, operator access, retention and contractual responsibilities must be assessed separately. SAVRN’s intended architecture makes those choices explicit. The browser preview does not establish a private deployment, a residency guarantee, a certification or an approved institutional processing environment.

## What you can explore today

Explore the proposed layers and their relationships through browser-local workflows and documentation.

## Before this service launches

Connected architecture requires implemented boundaries, tenant isolation, qualified execution adapters and verified placement controls.

## The customer outcome

The intended outcome is continuity of research context and governance when execution providers or infrastructure placements change.

## Related documentation

- [Models, offers and deployments](https://savrn.com/cloud/docs/concepts-models-offers-deployments)
- [Move to owned capacity](https://savrn.com/cloud/docs/compute-owned-transition)
- [Deployment and trust matrix](https://savrn.com/cloud/docs/trust-deployment-matrix)
- [Explore the architecture](https://savrn.com/cloud/console/#/architecture): Inspect the intended platform layers in the preview.