For regulated software · ISO 27001 · GDPR
Audit evidence built in, not bolted on.
kernable covers the technical controls auditors ask for, in the software your teams build, and lets you prove them with kernable verify.
Controls your teams don't have to build.
In most systems every control is a separate project: an audit table here, an access check there. In kernable they come with the architecture:
- 01
Audit tables someone forgot to fill in→A complete history, automaticallyEvery change is a signed event, with who made it and on whose behalf.
- 02
Access checks spread across services→One chain of checks, failing closedMiddleware checks every command and query; a missing check refuses instead of allowing.
- 03
Personal data copied into every table and log→Personal data in one vaultEncrypted, referenced from the history, and erasable with a signed proof.
- 04
Logs anyone with access could edit→Proof instead of promisesHash-chained and signed;
kernable verifyshows any change afterwards. - 05
Keys nobody dares to rotate→Rotation without a restartKeys rotate and are revoked while running; verify flags what a revoked key signed.
What kernable covers, and the standards it supports.
Each one is part of every application built on kernable, from the first day.
- Tamper-evident audit trail
Every change signed and hash-chained, checked by
ISO 27001 A.8.15 · SOC 2 · PCI DSS 10 · GoBDkernable verify. - Who did what, for whom
A signed request context with every event: sender, on behalf of, cause.
ISO 27001 A.8.15 · SOC 2 CC6.1 · GDPR Art. 5(2) - Erasure of personal data
An encrypted vault; an erasure is a signed event that leaves a proof.
GDPR Art. 17 · Art. 25 · ISO 27001 A.8.10 - Access control that fails closed
Grants per process, middleware on every request.
ISO 27001 A.5.15 · A.8.3 · SOC 2 CC6.1 · NIS2 - Cryptography and key management
Ed25519 signatures, mutual TLS, AES-256-GCM in the vault, rotation.
ISO 27001 A.8.24 · GDPR Art. 32 · HIPAA - Monitoring and backup
Metrics, readiness checks, documented backup and restore.
ISO 27001 A.8.13 · A.8.16 · DORA
Each control, mapped in detail: Compliance in the docs →
Honest about the rest.
Certification covers your organization; kernable covers these controls in your software. These are yours to cover:
- Reads are not recorded. Queries are checked but not stored; log reads in your API if you must.
- Failover through a standby. A pair with a witness takes over within seconds without losing an acknowledged write; availability still needs your runbook and backups.
- The store is not encrypted as a whole. Only vault values are; encrypt the disk the store lives on.
- People, not processes. kernable authenticates processes; signing in people is your application's part.
- Retention periods. Events are never deleted; erasures of personal data are triggered by you.
- The organization. Risk assessment, policies, training and suppliers: no software covers these.
Prepare for the audit with us.
We review your system against the controls your auditors will ask about, and build the parts that are missing on kernable, together with your team.
Twenty years of shipping software, the last seven designing the architecture other engineers build on. Author of comby, the event sourcing and CQRS framework that carries multiple commercial platforms in regulated markets. kernable brings the same model to teams that work in any language.
LinkedIn →[ Early access ]
Build on kernable before 1.0.
kernable is in private preview. Tell us what you're building, and we'll send you the binaries and the docs.