Security & Compliance

Is MiOpsAI SOC 2 compliant?

Not yet — SOC 2 compliance is on our 2026 roadmap. MiOpsAI is currently in private beta and the platform was architected from day one against SOC 2 control requirements, but the formal SOC 2 Type I attestation process is scheduled for 2026, with Type II audit to follow within 12 months of general availability.

The underlying infrastructure we run on (AWS, Stripe, OpenAI, Anthropic) is already SOC 2 Type II certified, which means data in transit and at rest already benefits from those compliance controls. MiOpsAI inherits those infrastructure protections while we work toward our own attestation.

Current security posture

  • Encryption at rest: AES-256 on all stored data including client records, AI memory, and file uploads
  • Encryption in transit: TLS 1.3 for all network traffic
  • Tenant isolation: Per-client data separation at the architectural level
  • Access controls: Role-based access control, audit logging, and 2FA available
  • Secrets management: API keys and credentials stored via AWS KMS

For organizations that require formal compliance today

If you require a SOC 2 report to procure software, please contact us. We can share our current security documentation, infrastructure attestations, and roadmap timeline. Many organizations are willing to accept the path-to-compliance posture during the beta period if appropriate documentation is provided. Enterprise plan customers receive priority compliance support.

Last updated April 21, 2026

Ready to see MiOpsAI in action?

Request access and we’ll walk you through how the platform solves your specific workflow.

Request Access →