Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xPfG3-00000000oeC-3MSW for pgsql-announce@arkaria.postgresql.org; Sat, 07 Nov 2026 12:10:57 +0000 Received: from localhost ([127.0.0.1]:48290 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xPfG3-000000033jg-429Z for pgsql-announce@arkaria.postgresql.org; Sat, 07 Nov 2026 12:10:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]:56360) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xPfAV-00000002jLe-0BTL for pgsql-announce@lists.postgresql.org; Sat, 07 Nov 2026 12:05:11 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xPfAS-00000000pWB-0FUH for pgsql-announce@lists.postgresql.org; Sat, 07 Nov 2026 12:05:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=JV2MOQrHsmUsKqSE40PiGnG2k6SQBzJz/1+q2ytlrzg=; b=riyY5zqspiS52Qqs80nAN0iH8p 1JoibpjcuTDM38QieuCu38aFynHYIqZoUusBsXPPfukGQoJSMrFxBzgTbMK460bb/fIbQY1qp++et f19SI8LVhCKN5ldbFb9Liu7nKzlT+4mN/qE9B9TNRvYHanAs71jjJeNylr97KAFBEd/sJH+JR8Yeb OLWrmxXPszveWJ461/73iCRQ/YBAWja+ApXE/hfDORqApgH8rVh+0VtdrBg6tAF5lRTCjj1GRH8/3 7iLB/jyoMf2WpPGiRl3MygtwdDkHZAh6uKfFp8qMpzwZJb3mU0gduWGN3fKCpuO/em4XGOo6NA/wz kMKbBaCA==; Received: from wrigleys.postgresql.org ([217.196.149.60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xPfAP-00000001xpS-0M9U for pgsql-announce@lists.postgresql.org; Sat, 07 Nov 2026 12:05:06 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xPfAM-00000004xIL-2pyL for pgsql-announce@lists.postgresql.org; Sat, 07 Nov 2026 12:05:03 +0000 Content-Type: multipart/alternative; boundary="===============5156850226422233272==" MIME-Version: 1.0 Subject: Brume: FK-safe pseudonymization for PostgreSQL test and debug copies To: PostgreSQL Announce From: Brume via PostgreSQL Announce Reply-To: frederik@brume.software Date: Sat, 07 Nov 2026 12:04:54 +0000 Message-ID: <179405309462.595141.455056588245268087@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 7cde54ea8b14b62818729cb5831916750153a8b4c523d2a813c91ccacd5df04d List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============5156850226422233272== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Brume 2.1, an open source (Apache 2.0) tool that creates deterministic, for= eign-key-safe pseudonymized copies of PostgreSQL databases for testing, deb= ugging and demos, is now available. ## Why Brume? Development teams often need realistic data to reproduce bugs, run tests or= prepare demos, but copying production exposes real personal data. Classic = masking scripts also tend to break referential integrity, which forces you = to disable triggers, suspend constraints or repair broken joins by hand. Brume copies a targeted subset of a source database to a target database or= to a `.sql` file, and transforms personal data on the fly, before anything= is written. Foreign keys stay valid end-to-end on the target. Brume only r= eads from the source database. ## Key features - **Column-level strategies:** `FAKE` for realistic synthetic values, `MASK= ` for partial reveals, `HASH` for one-way hashing, `NULLIFY` to drop sensit= ive data, `FPE_ID` / `FPE_UUID` for format-preserving encryption of identif= iers, and `DATE_SHIFT` to move dates while keeping their distribution. - **Deterministic output:** transformations are keyed by your own secrets. = The same input with the same secret always gives the same output, across al= l releases of a major version, so test fixtures and debug sessions stay sta= ble from one run to the next. - **Referential integrity:** format-preserving encryption rewrites primary = keys and the foreign keys pointing to them consistently. With `linked_colum= ns`, a value shared between tables that have no formal foreign key (for exa= mple, an email in both `users` and `audit_logs`) gets the same pseudonym ev= erywhere. - **Subsetting:** define row-level filters on any table (`created_at >=3D '= 2025-01-01'`, `tenant_id =3D 42`...). Brume follows foreign keys up to a co= nfigurable depth, towards parents and children, to produce a small, self-co= ntained and coherent extract. - **Declarative configuration:** a single `brume.yml` file describes the st= rategy for each table and column, with semantic types (`EMAIL`, `PHONE`, `I= BAN`, `ADDRESS`...) and JSONB paths to target nested fields. The file can b= e version-controlled and reviewed like code before any run. ## GDPR Pseudonymization is one of the measures cited by GDPR Articles 25 and 32. B= rume gives DPOs and security teams a reviewable, auditable description of h= ow personal data is transformed before it leaves production. ## Compatibility and installation Brume supports PostgreSQL 12 to 18. Packages are available for Debian/Ubunt= u (apt), RHEL/Fedora (dnf) and macOS (Homebrew). ## Links - [Website and documentation](https://www.brume.software/) - [Quickstart](https://www.brume.software/docs/getting-started/) - [Source code](https://github.com/brumeorg/Brume) - [Releases](https://github.com/brumeorg/Brume/releases) --===============5156850226422233272== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Brume: FK-safe pseudonymization for PostgreSQL test and debug co= pies
 

Brume: FK-safe pseudonymization for PostgreSQL test and debug copies<= /h1>

Brume 2.1, an open source (Apache 2.0) tool= that creates deterministic, foreign-key-safe pseudonymized copies of Postg= reSQL databases for testing, debugging and demos, is now available.

Why Brume?

Development teams often need realistic data= to reproduce bugs, run tests or prepare demos, but copying production expo= ses real personal data. Classic masking scripts also tend to break referent= ial integrity, which forces you to disable triggers, suspend constraints or= repair broken joins by hand.

Brume copies a targeted subset of a source = database to a target database or to a .sql file, and transform= s personal data on the fly, before anything is written. Foreign keys stay v= alid end-to-end on the target. Brume only reads from the source database.

Key features

  • Column-= level strategies: FAKE for realistic synthetic values= , MASK for partial reveals, HASH for one-way hash= ing, NULLIFY to drop sensitive data, FPE_ID / FPE_UUID for format-preserving encryption of identifiers, and DATE_SHIFT to move dates while keeping their distribution.
  • Determi= nistic output: transformations are keyed by your own secrets. The = same input with the same secret always gives the same output, across all re= leases of a major version, so test fixtures and debug sessions stay stable = from one run to the next.
  • Referen= tial integrity: format-preserving encryption rewrites primary keys= and the foreign keys pointing to them consistently. With linked_colu= mns, a value shared between tables that have no formal foreign key (= for example, an email in both users and audit_logs) gets the same pseudonym everywhere.
  • Subsett= ing: define row-level filters on any table (created_at >= =3D '2025-01-01', tenant_id =3D 42...). Brume follows f= oreign keys up to a configurable depth, towards parents and children, to pr= oduce a small, self-contained and coherent extract.
  • Declara= tive configuration: a single brume.yml file describes= the strategy for each table and column, with semantic types (EMAIL, PHONE, IBAN, ADDRESS...) and = JSONB paths to target nested fields. The file can be version-controlled and= reviewed like code before any run.

GDPR

Pseudonymization is one of the measures cit= ed by GDPR Articles 25 and 32. Brume gives DPOs and security teams a review= able, auditable description of how personal data is transformed before it l= eaves production.

Compatibility and installation<= /h2>

Brume supports PostgreSQL 12 to 18. Package= s are available for Debian/Ubuntu (apt), RHEL/Fedora (dnf) and macOS (Homeb= rew).

Links

This email was sent to you from Brume. It was delivered on their behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to Brume.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Open Source. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============5156850226422233272==--