Connections
A connection represents a set of credentials and configuration for reaching an external data source. DataRecs supports relational databases (PostgreSQL, MySQL, Oracle, IBM DB2, Microsoft SQL Server), cloud data warehouses (Snowflake), Google BigQuery, Google Sheets, Excel on SharePoint, and BI sources (Tableau, Looker).
Security model
Section titled “Security model”- Credentials are envelope-encrypted and stored in OpenBao — never in plaintext.
- Network access to your data source is tightly controlled: only authorised egress traffic leaves the platform.
- Each connection is validated at creation time before its credentials are stored.
Supported source types
Section titled “Supported source types”| Source | Identifier |
|---|---|
| PostgreSQL | postgres |
| MySQL | mysql |
| IBM DB2 | db2 |
| Oracle | oracle |
| Microsoft SQL Server | mssql |
| Snowflake | snowflake |
| Google BigQuery | bigquery |
| Google Sheets | google_sheets |
| Excel on SharePoint | excel_sharepoint |
| Tableau | tableau |
| Looker | looker |
Most relational sources authenticate with a username and password. Snowflake uses RSA key-pair authentication instead — see Connecting to Snowflake for the setup.
Lifecycle
Section titled “Lifecycle”- Create — provide the source type and its
credentials(for databases: host, port, username, password, database). - Test — validate connectivity (or the impersonation grant, for keyless types) via
connections test, without creating anything. - Use — reference the connection in reconciliation jobs.
- Rotate — update credentials at any time; active jobs will pick up the change on their next run.
Sharing across workspaces
Section titled “Sharing across workspaces”A connection has one owning workspace (controls who can modify it and its sharing) and can be shared into additional workspaces so more than one team can reference it in a job.