Where Safeguard runs. Region by region.
Thirty-plus public-cloud regions, five deployment shapes, and sovereign zones for regulated workloads. Every region runs the full platform — same scanners, same models, same audit trail.
Run Safeguard where your data already lives.
Amazon Web Services
AWS
Microsoft Azure
Azure
Google Cloud Platform
GCP
Oracle Cloud Infrastructure
OCI
Sovereign and regulated zones
Sovereign
Sovereign regions run the full Griffin model lineup inside the customer trust boundary. Weights and traces never leave the boundary.
The full Griffin lineup, inside your boundary.
The full Griffin model family — including Griffin Zero — runs inside the customer trust boundary in air-gapped environments. Model weights, scan inputs, traces, and the audit log never leave the boundary. Updates ship as signed artefact bundles that customers verify and apply on their own cadence.
Built to survive failure.
Multi-AZ by default, cross-region on demand, RTO / RPO targets that scale with the deployment tier.
Multi-AZ within region
Every Safeguard cluster runs across three availability zones by default. Loss of an AZ is transparent to the user — sessions continue, scans continue, the audit log keeps writing.
Optional cross-region replication
Customers on the dedicated and sovereign tiers can opt into hot standby in a second region. Traffic shifts automatically on regional failure; the audit log replicates synchronously.
RTO / RPO targets per tier
Shared cloud: RTO 4h, RPO 1h. Dedicated: RTO 1h, RPO 15m. Sovereign: RTO < 30m, RPO near-zero with synchronous replication. Targets are contractual on the dedicated and sovereign tiers.
Live region status, incidents, and historical uptime.
Real-time health for every region, scheduled maintenance windows, postmortems for past incidents, and a 90-day uptime ledger.
Open status page