Isolation by construction, not by configuration.
A tenancy boundary that depends on software configuration is one misconfiguration from failing. Ours is physical first, and everything above it is defense in depth.
Controls by layer
| Layer | Control | How it is evidenced |
|---|---|---|
| Physical | Dedicated accelerators; optional separately keyed cage with independent access control | Site visit, access logs, asset register by serial |
| Network | Dedicated VLAN, no shared inference gateway, egress default-deny with an allowlist you approve | Configuration export and periodic review |
| Runtime | Pinned model version, isolated serving process, no cross-tenant batching under any circumstance | Version attestation on every request |
| Data | Tenant-scoped storage and index; encryption at rest and in transit; documented destruction | Destruction certificate on termination |
| Identity | Federated to your identity provider; no local accounts for your users; time-bound operator access | Access log export to your SIEM |
| Contractual | No training, no retention, no subprocessor changes without consent, right to audit | The agreement itself |
Our operators are inside your audit boundary
The failure mode that matters in practice is not an external attacker. It is a vendor employee with standing access and no oversight. We designed around that first.
Strata operator access to a tenant environment is time-bound, purpose-logged, and visible to you in the same access log you receive for your own users. There is no permanent administrative session and no shared operator credential.
Where a customer requires it, operator access can be gated on customer approval per session — slower, and worth it for some workloads.
Certification path
- SOC 2 Type II is in progress, with the observation window scheduled ahead of first third-party tenant onboarding.
- The control set has been designed against FedRAMP Moderate and CMMC Level 2 from the outset for the defense and government path.
- Customer-run penetration testing is permitted and encouraged under a standard rules-of-engagement document.
- We will not claim a certification before it is issued. Where a control is designed but not yet audited, the security pack says so explicitly.
Send it to your CISO before you send it to procurement.
We would rather answer the hard questions in week one. Request the full security pack and architecture diagrams.