Guides
PrivaCI use cases
PrivaCI masks and subsets PostgreSQL while keeping foreign keys and joins intact. Each guide below covers a complete workflow — configuration, CI orchestration, and operational boundaries — so you can run it in your own environment without shipping data outside your network.
- Getting started
Anonymize Postgres for staging and CI
Full-database masking when you outgrow pg_dump scripts — bounded memory, auto-detect, and an audit trail.
- Guide
Production-shaped Postgres test databases in CI
Ephemeral masked Postgres per pull request — realistic distributions, automatic teardown, strict masking policy gate.
- Guide
Reproduce a customer bug without production access
One-button CI from DR warm standby: subset one tenant, mask PII, hand back a VPC-local repro database — no production access.
Operator reference lives on docs.boundarylogic.io — including the error code catalogue and configuration guide.