Architecture, security, and governance — in writing.
The written material we share with CISOs, compliance officers, and platform architects evaluating Eisberg. Shared under NDA as working documents — written for the audit committee, not the marketing channel.
What's in this set.
The Eisberg architecture
Under NDA · on request
Three-plane separation, customer-owned data plane, the open standards we commit to, and the implementation rationale. The document most architects read on the second call.
Security model & threat model
Under NDA · on request
Per-layer controls, audit chain design (HMAC tamper-evident, verified in our live environment), encryption posture, and customer-owned KMS key management — fail-closed by design, verified in our live environment.
Agent governance specification
Under NDA · on request
Agent Birth Certificates, two-key approvals, impact-as-a-gate, approval-chain semantics, kill-switch behavior, and the audit guarantees behind every agent action.
Compliance module roadmap
Under NDA · on request
BCBS 239, SR 11-7, HIPAA, 21 CFR Part 11 — the module roadmap, what each will ship with, and how evidence rides the platform's tamper-evident audit chain today. These modules are roadmap, not shipped — the document says so plainly.
GPU-native compute: methodology brief
In preparation
The paired-run methodology we will use to measure GPU vs CPU on real workloads. We publish numbers when they are measured — never before. The GPU lane itself is roadmap.
Hardware-ready architecture brief
Under NDA · on request
How Eisberg's storage / cache / routing / scheduling abstractions slot future memory and compute hardware into existing interfaces. Forward-architecture rationale.
Request whitepapers
We share whitepapers under NDA with prospects we are working a real opportunity with. Tell us what your team needs and we will get the relevant set to you within 24 hours.