Security whitepaper
Architecture, threat model, and the boundaries we do not cross.
Request →01 / Resources
Documentation, the security whitepaper, and the raw data behind our research. We would rather you evaluate us properly than quickly.
02 / Documentation
Connect a Postgres instance and validate your first million rows.
The full grammar, the type system, and what compiles to bytecode.
Bring your own keys across AWS, GCP and Azure without three audit trails.
Inspect rejected rows, relax a rule, and replay what comes back.
Declare SOC 2 and GDPR controls in your repository and enforce them.
Helm chart, licence server, and the offline tolerance window.
03 / Documents
No form wall on the whitepaper. The SOC 2 report needs an NDA because our auditor insists, not because we do.
Architecture, threat model, and the boundaries we do not cross.
Request →Current report under NDA. Request through the sales route.
Request →The 240 filings behind our 2026 research, with our coding.
Request →A working GDPR pack you can fork and adapt.
Request →04 / Journal
The EU AI Act moves the burden of proof onto the operator. What that means for teams already running models in production.
Three regions, three key management services, one audit trail. A working pattern for keeping custody of your keys across providers.
We read 240 breach disclosures from the last eighteen months. The same four failures account for most of them, and none are exotic.