How a fix reaches production
-
Step 1
The developer requests
Writes the fix. Sensitive values are sealed the moment they are sent.
-
Step 2
The DBA reviews
Checks the SQL without ever seeing the values.
-
Step 3
The business approves
Confirms the change, with the values masked.
-
Step 4
sealfix runs it
Exactly as approved. If anything differs, nothing changes.
Safe by design
Customer data stays sealed
Not in screens, logs or error messages. Only the fix itself reads the values.
Every fix can be undone
With the same approvals as the fix.
A log nobody can rewrite
Every action is recorded and protected against tampering.
Editions
Enterprise
Pricing on request
Everything in Community, plus executor keys in a hardware security module, a database account issued for each job, and support.
Talk to usdocker compose up -d