Skip to content

Datalyptica sealfix

Edition: Community and Enterprise

Production data needs fixing. A wrong status, a duplicated payment, a customer record that must change today. sealfix lets your teams make those changes through one governed path: reviewed, approved, run exactly as approved, and reversible. The customer data inside the fix stays sealed the whole way.

flowchart LR
    R["Requester<br/>writes the fix"] --> D["DBA reviewer<br/>checks the SQL"]
    D --> B["Business approver<br/>confirms the change"]
    B --> E["sealfix executor<br/>runs it as approved"]
    E -. "if needed" .-> RB["Governed rollback"]
    classDef person fill:#E9EEF6,stroke:#23407A,color:#13202D
    classDef system fill:#DCE3EE,stroke:#13202D,stroke-width:2px,color:#13202D
    class R,D,B person
    class E,RB system

  • Get started

    Run the five-minute demo with fake data, then evaluate sealfix on your own servers.

    Get started

  • How it works

    Sealed values, split visibility, approvals, rollback and the audit trail, explained.

    Concepts

  • Use sealfix

    Step-by-step guides for requesters, DBA reviewers, business approvers and auditors.

    Guides

  • Administer

    Install offline, connect your directory and databases, set the policies, run it.

    Administration

  • Security

    What sealfix protects, what it does not, and how the cryptography works.

    Security

  • Reference

    States, checks, masking, the configuration file and the supported databases.

    Reference

Why teams use it

Without sealfix With sealfix
The script travels by email or chat, with the customer's national ID written in it. The SQL is a template; the values are sealed on arrival and never shown to reviewers.
One DBA runs it on production, alone, at night. Two different people approve, and the requester can never approve their own fix.
"It said 1 row" until it updated 40,000. A dry run counts the rows first; the real run rolls back by itself if the count differs.
Undoing it means finding a backup. The touched rows are saved, encrypted, before the change; a rollback is one request.
The trail is a ticket comment. Every step lands in an append-only, hash-chained audit log.

sealfix runs on your own servers, works offline, and is open source under AGPL-3.0. It supports PostgreSQL, Oracle and SQL Server.