Brume masks PostgreSQL copies while preserving table relationships
Brume 2.1 creates pseudonymized PostgreSQL copies for testing and debugging while preserving foreign-key relationships. It transforms values before writing the target, using deterministic secrets so the same input gets a consistent replacement. Its configuration can also link matching values across tables without formal foreign keys, helping realistic test data retain working joins without copying the original personal values.
Brume · PostgreSQL community news · Nov 7, 2026
Why it matters
A useful test copy needs both realistic relationships and an explicit account of which sensitive fields were transformed.
More context
The released Apache-2.0 CLI supports PostgreSQL 12–18 and packages for Linux and macOS. Start with a small extract, a read-only source account and a reviewed brume.yml. It also requires pg_dump at least as new as the source database’s major version.
Keep in mind
Pseudonymization is not a guarantee of anonymity: unconfigured fields and combinations of remaining attributes can still identify people. Review the resulting data before sharing it.
Original read