Trust Center

Enterprise trust and security posture

Omnis Genomics is built for teams that need deterministic outputs, explicit provenance, and controls that survive procurement review.

Last reviewed: February 19, 2026

Control areas

Security program baseline

  • • Controls are mapped to SOC 2-style criteria (access, change management, logging, and incident response).
  • • Production changes run through code review plus CI gates (lint, typecheck, unit tests, e2e).
  • • Public-facing APIs enforce validation, rate limiting, and idempotency for retried writes.

Data handling

  • • Public website forms are designed for business intake, not regulated data submission.
  • • Customer data paths for pilots and enterprise deployments are scoped by written agreements (MSA/DPA/BAA where applicable).
  • • Evidence artifacts are deterministic and hash-addressed to support audit and replay.

Deployment models

  • • Managed SaaS for fastest onboarding.
  • • Customer VPC / private networking for stricter ingress and residency requirements.
  • • Self-hosted adapter patterns for environments that require local execution and explicit egress control.

Reliability and incident response

  • • Release workflows are tied to immutable artifacts and documented rollback paths.
  • • Incidents are triaged with severity levels, ownership, and post-incident action tracking.
  • • Enterprise customers can request escalation contacts and operating cadence during onboarding.

Assurance artifacts available on request

  • •Security architecture summary
  • •Subprocessor and data-flow summary
  • •Incident response escalation matrix
  • •Business continuity and access-control notes

Need procurement-ready answers? Start with the security intake flow and we will route to the right technical owner.