kernablekernable

For health software · GDPR · HIPAA

Patient data with a history, and erasure that holds up.

Every change to a record, who made it and on whose behalf, signed and verifiable. Personal data lives in an encrypted vault and can be erased without breaking the history.

[ Why kernable ]

The two things health data needs at once.

A complete history, so every change can be explained. And erasure, so a person's data can go when they ask. Usually they fight each other; in kernable they don't:

  1. 01"Who changed this record, and when?"→
    Every change, with who and for whom

    Each change is a signed event, carrying the person who made it and the one it was for.

  2. 02Access rules spread across services→
    One chain of checks, failing closed

    Your rules check every read and every change; a missing rule refuses.

  3. 03Deleting a patient breaks the audit trail→
    Erasure that keeps the history

    Personal fields live in a vault; erasing them leaves the history intact and verifiable.

  4. 04Logs full of personal data→
    References instead of copies

    The history holds references to the vault, not the data itself.

  5. 05"Trust us" when the auditor asks→
    Proof instead of promises

    kernable verify shows any change, removal or reordering afterwards.

[ The controls ]

What kernable covers.

kernable doesn't make your organization compliant, but these technical controls come with every application built on it:

  • Audit controls

    Every change recorded, with who made it, tamper-evident.

    HIPAA §164.312(b) · ISO 27001 A.8.15
  • Integrity

    Signed, hash-chained history; kernable verify checks it.

    HIPAA §164.312(c)(1)
  • Right to erasure

    Personal data in a vault, erased by a signed event that leaves a proof.

    GDPR Art. 17 · ISO 27001 A.8.10
  • Encryption and transport

    Vault values encrypted with AES-256-GCM; mutual TLS between processes.

    HIPAA §164.312(a)(2)(iv) · (e) · GDPR Art. 32

Where kernable stops: the event store is not encrypted as a whole, so encrypt the disk it lives on; the request context (who acted) is stored in clear, so use IDs that do not identify a patient; and there is no failover yet. Each control in detail: Compliance in the docs →

[ Consulting ]

Model patient data with us.

We help you decide what is history and what is personal, design the erasure from the start, and build the first records on kernable with your team.

Artur Susdorf
Artur Susdorf Author of kernable

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.