hoogvliets makes the data layer reviewable on its own terms

A downstream fork's database work gets carved out into a standalone slice so AGPL reviewers can actually inspect it.

As part of a broader open-source license disclosure, hoogvliets has split the database half of the work into its own pull request - migrations, schema, and local-development plumbing in one place, separate from the runtime and frontend pieces. The headline change is moving off a single big schema file onto a managed migration tool, so the database can evolve forward and roll back one step at a time instead of being recreated wholesale.

The schema itself isn't just plumbing. It adds row-level security to keep tenants from seeing each other's data, an encrypted store for API keys, soft-delete on user profiles, and scaffolding for an account deletion job - the kind of lifecycle and isolation controls a buyer's security review will ask about. There's also PDF conversion status tracking and workflow-sharing checks woven in.

The stated point is transparency to the upstream community rather than shipping new behaviour.