PostgreSQL test data, inside your network

What works today

Built-in connector (psycopg 3): catalog discovery, row-count estimates, column profiles, foreign-key relationships and streaming Arrow reads for subsetting.

TLS defaults to sslmode=verify-full; the password is supplied as a secret reference.

Authentication: password (secret reference).

Capability matrix

Each capability is tracked separately and shown at the level the recorded conformance evidence supports. A connector that only discovers metadata is never presented as equivalent to one that runs the whole workflow.

Read-only proof

Proven from the catalog before reading: the session must be read-only, the role must not be superuser/CREATEROLE/CREATEDB/REPLICATION/BYPASSRLS, and it must hold no table write, schema CREATE or database CREATE privilege.

Compatibility profiles

Managed variants of an engine are profiles of this connector, not separate connectors. A profile is marked tested only when its own conformance run passed.

• Amazon RDS for PostgreSQL — not tested yet (roadmap only)
• Amazon Aurora PostgreSQL-Compatible — not tested yet (roadmap only)
• Azure Database for PostgreSQL — not tested yet (roadmap only)
• Google Cloud SQL for PostgreSQL — not tested yet (roadmap only)

Conformance evidence

DataNivra runs every connector through a common conformance kit on synthetic data: no write statements, proven read-only access, secret redaction, schema and relationship discovery, bounded streaming, cancellation, clear reason codes, egress canaries and no raw values in logs, then the discover, mask, subset, certify and provision workflow. The published status is computed from those results.

Connector version 0.1.0, last verified 2026-09-30.

What crosses the boundary

Connectors run inside the agent in your network. Only metadata, aggregates and evidence reach DataNivra Cloud:

• Schema, table and column names and data types (for file sets, operator-declared or opaque table names — never data-derived file names).
• Aggregates such as row-count estimates, null and distinct ratios; counts from 1 to 10 are reported as 10 (small-cell protection).
• Classification findings (which column looks like which kind of sensitive data) and relationship metadata.
• Evidence metadata: checksums, gate outcomes, engine and policy versions, and templated error codes.

Never sent:

• Any cell value, row, sample, minimum/maximum or top-k value — masked or not.
• Credentials, connection strings or resolved secret values: DataNivra stores only the secret reference.
• Free text copied from your data, or exception messages that contain values.

See the customer-resident architecture and how to verify these claims yourself.

Setup outline

1. Create a dedicated login role with SELECT on the schemas to read and nothing else, and make its sessions read-only (ALTER ROLE … SET default_transaction_read_only = on).
2. Store the connection document in a secret store the agent can resolve, with the password as a secret reference.
3. In the console, register the source with the secret reference of that document (for example vault://tdm/source-connection) and the agent that can reach it, then run discovery.
4. Before reading a production source, the agent proves the role is read-only from the catalog and refuses to continue if it is not.

Example connection document, stored in your secret store and resolved by the agent locally (DataNivra only ever sees its reference):

{
  "kind": "POSTGRESQL",
  "host": "claims-replica.db.example.internal",
  "dbname": "claims",
  "user": "tdm_reader",
  "password_ref": "vault://tdm/claims-replica#password",
  "sslmode": "verify-full",
  "schemas": ["claims", "reference"]
}

Next: install the agent, then follow the getting started guide.