SOC 2
Type II
Independently audited controls for security, availability and confidentiality over time.
Trust center
How OpenAna protects your code and data, where Ana can run, and how every action it takes is gated, approved and recorded.
SOC 2
Type II
+ ISO 27001 · HIPAA · GDPR
Compliance
Audited controls for security, availability and confidentiality, privacy by design, and reports available under NDA.
Deployment
Run Ana where your policies say it must run, with data residency under your control.
Data
Your code, findings and telemetry are used to do your work - never to train models.
Control
Policy gates, named approvers and a decision log for everything Ana does.
Compliance
Reports and certificates are shared with customers and prospects under NDA.
SOC 2
Type II
Independently audited controls for security, availability and confidentiality over time.
ISO
27001
A certified information security management system covering people, process and technology.
HIPAA
Compliant
Safeguards for protected health information, so healthcare and life-sciences teams can use Ana.
GDPR
Compliant
Lawful processing, data subject rights and data residency for personal data of people in the EU.
Deployment
Same engineers, same guardrails - four ways to deploy.
Isolation
Fastest start. Managed by OpenAna, with SSO, role-based access and scoped, read-only-first connections.
Isolation
Ana runs inside your own cloud account. Code and data stay within your environment and network boundary.
Isolation
Run Ana in your own data center for complete isolation and control.
Isolation
For regulated and classified environments with no outbound connectivity.
Data handling
Governance
Every action is classified by risk; your policies decide what Ana may do on its own and what needs a person.
Learn more →Sensitive changes - IAM, network, production, data - route to the specific people your policy names.
Learn more →Who approved what, when, and with which evidence - kept for audits and post-incident reviews.
Learn more →Ana SDE in VS Code and IntelliJ asks before it edits a file or runs a command.
Learn more →Security program
What our compliance program covers day to day. Details and evidence are in our reports, available under NDA.
Every production change is tracked, peer-reviewed in code review and released through a controlled process.
User access is reviewed every quarter, with corrective actions tracked to closure.
A documented patch policy covers cloud servers and endpoint devices, with monthly compliance reporting.
Alerting, capacity reporting and regular management reviews of operational and security signals.
Business continuity and disaster recovery plans are tested every year.
A maintained register of assets and software licenses.
SBOM generation and security review are part of the development lifecycle.
SAML single sign-on and role-based access for the Ana platform.
FAQ
Yes. OpenAna is SOC 2 Type II compliant. The report is available to customers and prospects under NDA - request it through the button on this page.
Security review
We’ll share our SOC 2 Type II report and ISO 27001 certificate under NDA and walk your security team through deployment, data handling and guardrails.