ORDR ZeroMythic
ZeroMythic inverts the trust model of security platforms: the customer, not the vendor, authorizes every privileged action. A customer-signed scope bundle defines what the platform may ever do; a policy engine inside the customer's own perimeter must co-sign each action token before anything executes. No signature, no action — and every event lands on a tamper-evident provenance mesh an auditor can verify offline.
v0.1.0-preview — not for production use.
audience: Enterprises and governments running privileged or offensive security programs
Ed25519
event signatures
256
Merkle tree depth
200
event taxonomy
2K+/s
CI throughput floor
Capabilities
What ORDR ZeroMythic actually does.
Customer Authorization Plane
CSB → CPE → PAST: customer-signed scope, customer-side policy engine, co-signed action tokens. Fail-closed by construction.
Multi-officer ceremony
Scope bundles signed by a quorum of named officers (e.g. CISO + GC) on hardware keys, canonicalized and self-hashed.
Signed event mesh
Every event sealed with Ed25519 over canonical bytes; per-component signatures verified downstream.
Tamper-evident provenance
Per-tenant immudb anchoring under a 256-depth sparse Merkle tree, with signed root checkpoints and a proof endpoint verifiable offline.
Hard tenant isolation
Each tenant in its own NATS operator-mode account — cross-tenant access is broker-rejected, and integration tests assert it.
Replay & taxonomy
Replay any tenant stream from any timestamp; 200 stable-numbered event types across 10 platform components.
stack: Go · Rust · NATS JetStream · immudb · PostgreSQL · React
verify: sha256:d93b71c0e6f4…
Part of the ORDR core: deterministic · audit-chained · fail-closed
Next: ORDR Connect