Security, built in from day one.
Opryx treats security as a first-class concern. Communications are encrypted with TLS, identity runs through your existing SSO with multi-factor authentication, access is least-privilege, and every change is scanned for vulnerabilities before it ships. Formal certifications come as we scale; the controls are in place today.
How we approach security
Encrypted in transit
All communication is encrypted with TLS, including traffic between internal services. Data is scoped to what the workflow needs, with clear separation between environments.
SSO and MFA from day one
Sign in through your existing identity provider, including Microsoft Entra ID, Okta, and Google Workspace, with multi-factor authentication supported from the start.
Least-privilege access
Access is granted by role and scope and enforced server-side, so people and services get only the permissions their job requires.
Scanned before it ships
Every change runs through automated security scanning: static analysis, dependency CVEs, container images, infrastructure config, and secrets, all gated in CI.
Auditability
Consequential actions leave an auditable trail, including who approved work, when decisions were made, and the workflow events attached to the work order.
Human oversight
AI assists and recommends; people approve the actions that matter. Oversight is a feature, not an afterthought.
Real controls now. Formal certifications as we scale.
The controls above are live today, not aspirations. We won't claim certifications we haven't completed, like SOC 2. The architecture is built to meet formal enterprise and compliance requirements, and we're working through them as we grow.
- Security controls implemented and gated in CI today
- Built to meet formal enterprise and compliance requirements
- Straight answers about our posture, partner to partner
Have a security question? Ask us directly.
Common identity, deployment, and access questions are covered in the FAQ.