The lane IT can trust.
Salus exists so security can say "yes" to AI without losing control. Here's how the lane stays governed — and where our compliance program stands.
Where our program stands today.
Both audits are complete, carried out by an independent audit firm. Here's what we hold, and how to get a copy.
SOC 2 Type II
CompleteIndependent audit complete · report available under NDA
ISO 27001:2022
CertifiedIndependent certification audit complete · certificate on request
Penetration testing
In progressIndependent third-party tests via our compliance program · reports under NDA
Salus is SOC 2 Type II compliant and ISO 27001:2022 certified, following independent audits. Compliance is monitored continuously in Vanta, and penetration testing is performed by independent third parties. Ask our team for the SOC 2 Type II report, shared under NDA, or a copy of the ISO 27001 certificate.
Governed by default. For humans and agents.
The controls that let you hand a lane to every team and every agent without losing the plot — set once, inherited by every app.
Your rules, enforced
RBAC · humans & agents
Policy gates
Release window
humans + agents · weekdays 06–20 UTC
Vulnerability scan
0 critical allowed
Egress to unlisted API
external network · not allow-listed
Last resort
Take offline
any deployment · bring it back or roll back
Audit trail
Role-based access control
Scope what every person can deploy, reach and change, at organisation, space and project level. An agent acts with its builder’s access, so it inherits those bounds and can never exceed them.
Encrypted secrets
Secrets encrypted at rest and in transit, injected at runtime — never stored in code or logs.
Isolation & controls
Each workload runs isolated, with its own credentials and network boundary, so what one app can reach is bounded before it runs.
Audit & observability
Audit events are written append-only — never edited or deleted — isolated per tenant, each recording the actor and the time. An agent acting for someone is recorded as that person — agents do not yet hold their own identity in the trail. Any deployment can be pulled offline instantly.
Who owns what — in plain terms.
The question every security questionnaire asks first, answered before you ask it.
You own
- Your cloud account and IAM (Enterprise/BYOC)
- Your data and your databases
- Your policies — who may build, deploy, and promote
Salus operates
- The platform: builds, pipelines, runtime, upgrades
- The governance controls: roles, isolation, audit storage, taking apps offline
- Monitoring, patching, and vulnerability management
You both see
- The audit trail — append-only, naming the person whose access each action used, agent or not
- Observability: logs, metrics, costs per workload
- The SOC 2 Type II report (under NDA) and the ISO 27001 certificate
Your data never leaves your cloud.
Salus Enterprise runs single-tenant inside your own AWS, GCP, Azure, or Huawei account (BYOC). Apps, data, and secrets stay within your perimeter and your compliance boundary — in whatever region your obligations require, from the US to the EU to Africa. Residency isn't a feature tier; it's a consequence of the architecture.
The governed lane sits alongside production — never inside it.
Need our security documentation?
We'll walk your security team through the architecture, share our controls and current audit status, and provide documentation under NDA. No pitch deck.