PostgreSQL Integration | DualEntry

PostgreSQL

Overview

You already run the database. Your analysts query it, your dashboards point at it, and finance data needs to land there in a shape your own tooling understands. PostgreSQL in DualEntry is not a general-ledger sync like Stripe or Brex. It is an export destination: you hand DualEntry the connection details, and DualEntry makes them available to the export infrastructure that writes into your database.

The mechanism is deliberately narrow. You supply a host, port, database name, username, password, and an optional SSL mode. DualEntry validates that payload against a fixed credential schema, then opens a connection to PostgreSQL with a ten-second connect timeout and closes it again. A clean open and close counts as validation. On success the destination moves from Pending through Testing to Validated, the linked integration shows as Connected, and the full credential payload is written to AWS Secrets Manager.

Flow runs one way: out of DualEntry and into your database. Downstream AWS-based export jobs, typically AWS Glue pipelines configured for your organization, read the credentials from Secrets Manager and perform the actual writes. DualEntry does not read from your PostgreSQL instance, and nothing in your database flows back into the ledger.

So be precise about what connecting does. It registers and tests an export destination. It does not start a sync. Table layout, job cadence, and the SQL for specific datasets are owned by your deployment's export configuration, not by this integration. One active PostgreSQL export integration is allowed per organization.

Data synced

The integration syncs the following data types:

Connection and Credentials

Credential Validation

Security and Storage

Key Features

  1. An export destination, not a sync
  2. Validated in the background
  3. Status you can watch
  4. TLS to your standard
  5. Managed PostgreSQL and Redshift
  6. One destination per organization
  7. Disconnect that respects running jobs
  8. Credentials held outside the product database

FAQ

Does data flow from PostgreSQL back into DualEntry?
No. This integration is an export destination, not a general-ledger sync. Data moves out of DualEntry and into your database, and DualEntry does not read from your PostgreSQL instance as part of this flow.

What actually performs the export?
Downstream AWS-based export infrastructure does, typically AWS Glue pipelines configured for your organization. Those jobs read your PostgreSQL credentials from AWS Secrets Manager and write data into your database. The connect flow in DualEntry registers and tests the credentials so that infrastructure has something to read. It does not move data itself.

Where are my database credentials stored?
In AWS Secrets Manager, under a secret name keyed to your organization and the destination's identifier. The username and password never land in DualEntry's relational database and are never returned by DualEntry's APIs after creation. DualEntry stores only the non-sensitive metadata: engine, host, port, and database name. Because there is no in-place credential edit, treat any rotation or reset as a full re-create of the destination.

Can I use this with Amazon RDS, Aurora, or Redshift?
Yes. Amazon RDS for PostgreSQL and Aurora PostgreSQL both work with engine=postgres. Amazon Redshift uses engine=redshift on the same credential schema, and the validation path is identical, so the same operational notes apply.