Security
Data compliance
How compos approaches residency and compliance for sensitive workloads.
Overview
compos is designed for security- and compliance-sensitive workloads. That affects decisions across the platform: where data runs, how access is scoped, and how changes are reviewed.
Data residency
Data stays in the deployment region you choose. For teams with local data requirements, that means deployments can remain within the country without designing around a foreign default. Residency is a configuration of the platform, not an afterthought.
Encryption
- **At rest**: Data is encrypted at rest
- **In transit**: Connections are encrypted in transit
- **Backups**: Backups are encrypted
Compliance posture
Certifications are published the moment they are earned, and not before. Until then, the platform builds the controls those frameworks require: audit trails, role-based access, and reviewable change history. If a certification claim appears on this page, it is a fact, not a direction.