# Deployment and trust matrix

Canonical: https://savrn.com/cloud/docs/trust-deployment-matrix

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

Infrastructure ownership does not by itself establish data residency, isolation or compliance. SAVRN Cloud's deployment matrix separates model identity, processing location and operating responsibility across rented and owned capacity, with prepared candidates kept distinct from approved customer allocations.

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

## Compare the intended placements

Review [Architecture](https://savrn.com/cloud/console/#/architecture) and [Compute](https://savrn.com/cloud/console/#/compute). SAVRN Cloud is preparing model configurations for execution SAVRN operates on separately rented or owned capacity. Neither placement becomes a customer service through a browser demonstration. The two prepared Qwen profiles identify configurations for review, while available capacity and data eligibility remain separate questions.

| Dimension | Rented capacity operated by SAVRN | Owned capacity operated by SAVRN |
|---|---|---|
| Model identity | Verify artifact and runtime on the allocated lane | Verify artifact and runtime on the allocated lane |
| Private access | Test network controls and infrastructure-provider boundaries | Test network controls and operator access |
| Data location | Assess compute, storage, logs and infrastructure terms | Assess compute, storage, logs and physical operations |
| Operations | Assign infrastructure and SAVRN responsibilities | Assign SAVRN infrastructure and service responsibilities |
| Customer availability | Requires an approved allocation and qualified release | Requires an approved allocation and qualified release |

An owned resource can increase placement control, but it does not automatically establish isolation, retention or institutional compliance.

## Use the preview application appropriately

Prepared candidate profiles contain real model and artifact descriptions; execution records, usage and workflow results remain simulated and stored in browser localStorage. The application has no multi-user authentication boundary, institutional data agreement or approved production retention service. Use public or invented inputs and retain simulation labels on exports.

## Before connected services launch

Document processing, storage, logging, backups, control-plane location and operator access. Identify provider responsibilities and SAVRN controls separately. Publish only verified certifications or commitments with their actual scope. Assess the intended workload and customer terms before declaring it eligible. A private endpoint, a regional label or an approved UI record cannot substitute for technical and contractual evidence.