Editions¶
Edition: Community and Enterprise
sealfix comes in two editions built from one code base. Community is free and open source under AGPL-3.0, with no limit on users or databases. Enterprise adds integrations and controls that large organisations need, under a commercial licence.
Every control that protects a fix and its data is in Community¶
| Capability | Community | Enterprise |
|---|---|---|
| Sealed values, opened only by the executor | ||
| Split visibility: DBAs never see values, approvers see them masked | ||
| Checks, dry run and row-count guard | ||
| Encrypted before-images and governed rollback | ||
| Approvals by different people, configurable per environment | ||
| Approvals signed with passkeys | ||
| Emergency changes with a review owed afterwards | ||
| Tamper-evident audit log with signed checkpoints | ||
| LDAP, Active Directory and OIDC single sign-on | ||
| Roles and projects | ||
| PostgreSQL, SQL Server and Oracle | ||
| Notifications, Git record, SIEM over syslog, OpenTelemetry | ||
| Executor keys in an HSM (PKCS#11) | ||
| A database user per job, issued and revoked by OpenBao |
Planned for Enterprise¶
SAML and SCIM, more SIEM and ITSM integrations, custom roles and access reviews, standard (pre-approved) changes, several executors for high availability, and signed compliance evidence packs.
When a licence ends¶
| When | What happens |
|---|---|
| The last weeks before the end date | Everything works; System health shows a warning |
| 30 days after the end date | Everything still works (grace period) |
| After the grace period | The installation is Community again. Data held by Enterprise features stays readable for rollback, but no new work uses them |
Pricing¶
[PRICE] per [UNIT]. Contact [SALES EMAIL].