We build the audit trail before the incident.

OmniPriv was built by people who had already run privileged access programmes and watched the same failure repeat: the controls existed on paper, and the evidence did not exist at all.

So the record came first. Every privileged action produces something an auditor can follow, every secret is encrypted and vault-managed, and the whole platform runs on infrastructure you control rather than ours.

capability modules over one policy engine
9capability modules over one policy engine
compliance frameworks mapped out of the box
6compliance frameworks mapped out of the box
hard-coded credentials inside the platform
0hard-coded credentials inside the platform
inbound ports to open on managed systems
0inbound ports to open on managed systems

Built to be deployed, not demoed

A privileged access platform only counts once it is running against real systems, so the deployment model is treated as part of the security argument rather than an implementation detail. OmniPriv runs where your other critical systems run, and it asks nothing of the machines it protects.

  • On-premise deployment across VMware, Red Hat and OpenStack as a hardware-agnostic appliance
  • Multi-node clustering with container health checks, heartbeat monitoring and database replication
  • Strict multi-tenancy through org_id isolation on every resource, schema-per-tenant
  • Layered key protection, with an external installation key you hold
  • Break-glass emergency procedure and granular credential restore without a full system restore
See the full specification

Mapped to the frameworks you report against

We would rather be checked than believed. These are the frameworks the platform's controls are mapped to out of the box.

Controls mapped out of the box
  • SOC 2
  • ISO 27001
  • NIST SP 800-53
  • HIPAA
  • PCI DSS
  • SOX 404
Security posture and framework detail
Mapped

SOC 2

Controls mapped to the Trust Services Criteria: security, availability, processing integrity, confidentiality and privacy.

Mapped

ISO 27001

Controls mapped to the ISO 27001 information security management requirements, across platform operations and development.

Mapped

PCI DSS

Controls mapped to PCI DSS requirements for environments that handle payment card data.

Mapped

NIST SP 800-53

Controls mapped to the federal security and privacy control catalogue that regulated environments are assessed against.

What we hold ourselves to

These are positions on how the product gets built, not claims about how many people work here.

  • Security is not a trade-off

    Security does not lose to shipping speed. The platform itself holds zero hard-coded credentials, and every secret it uses is vault-managed and auditable.

  • Built for hard environments

    Designed for on-premise estates in financial services, healthcare, government and energy, where the network cannot be re-architected around a vendor.

  • Evidence over assertion

    Control mappings are published rather than implied, so a capability can be checked instead of taken on trust.

  • You hold the keys

    The installation key is generated at installation and stored independently of the platform, so a compromise of our storage is not a compromise of yours.

See what the platform does before you take our word for it

  1. On-premise
  2. Mapped to your frameworks
  3. Yours to run

Nine modules, one audit trail, and a deployment model that matches the infrastructure you already run.

We will walk through the capability set and the control mappings against your own environment.

Frequently Asked Questions

Have a question that is not here?

Talk to the OmniPriv team about your identities, systems and AI agents.

Request a Demo

On-premise, regulated environments that need to prove what happened to a privileged account. The platform covers the full privileged access lifecycle, vaulting, session control, approval workflow, integration and audit, in nine capability modules that share one policy engine and one audit trail.