Copy your records into your own Postgres database (beta)
An owner or admin can have Turtini copy the organization's records into a Postgres database the organization runs, in its own network. It is in beta.
**What gets copied**
Contacts, accounts, opportunities, projects, runbooks and authored grants -- you choose which. Each lands in its own table in a schema you name (default `turtini_replica`): the full record as `data` (jsonb), a few typed columns beside it, and the time it last changed. Only this organization's records are sent. The replicator binds the schema to your organization the first time it connects, and every table carries a check constraint that refuses a row for any other organization.
**Setting it up**
1. Prepare a Postgres database with TLS enabled, reachable on a public address. Create a user that may create the schema, or that already owns it.
2. Open **Account > Data Replica**. Enter the host (the name your server certificate carries), port, database, user and schema, and pick the collections.
3. Paste your CA certificate so Turtini can verify the server. For mutual TLS, paste a client certificate and its key; Postgres certificate authentication maps the certificate's CN to the user. A password works too, alone or with the certificate.
4. Choose **Save**, then **Test and enable**. The test shows the TLS version and whether a client certificate was presented.
**How it stays current**
It is a periodic pass, not a live stream. The first pass is the backfill. After that, each pass copies new and changed records and marks deleted ones: a deleted record stays as a row with `deleted` set and its content removed. **Lag** on the status card is the time since the last completed pass began; you set the threshold at which it is flagged as behind. **Run now** does part of a pass immediately; **Start a full pass** begins a new one from the start.
**Good to know**
- The connection always verifies the server's certificate and host name. There is no unencrypted or unverified mode.
- Credentials are kept in Turtini's credential store, under your own encryption key if you set one in **Account > Encryption**, never in the database.
- Saving the form pauses the replica until it passes a test again. Changing the target or the collections starts a new full pass.
- Deleting the configuration removes the credentials. The rows already in your database are yours and are left alone.
- To stream changes onward (for example with Debezium into Kafka), point that tool at your replica database. Turtini does not run it.
- Private network connectivity (VPN or private service connect) is arranged with Turtini; by default only public addresses are accepted.