Our access model
Aureus engineers have administrative access to your cluster infrastructure. This is inherent to the managed service model — we operate it. What we've built around that access is an audit trail and a set of controls that give you visibility and trust.
Access is logged
All SSH sessions and Kubernetes API interactions by Aureus staff are logged with user identity, timestamp, and command history. Logs are stored in an append-only audit system. We can provide audit logs upon request.
No standing access
Engineers don't have persistent sessions into your cluster. Access is granted on-demand via a privileged access management system and expires automatically after the session ends. This limits the blast radius of any credential compromise.
Your team's access
You control what your team can access. We can configure Kubernetes RBAC to give your developers read access to logs and metrics without write access to cluster resources. Role structures are designed during onboarding and can be modified via a support ticket.
We don't read your application data
Our access is to the infrastructure layer — operating system, Kubernetes control plane, and container orchestration. We don't access your database records, user data, or application-level secrets except when explicitly asked to troubleshoot a specific issue and with your consent.
We have the access needed to operate your infrastructure. We use it only when necessary, and we leave a record every time.
Compliance
If you have specific compliance requirements (SOC 2, GDPR, HIPAA), contact us before signing up. We can discuss architecture and access controls appropriate for regulated workloads. Cluster L customers can negotiate custom data processing agreements.