Connect Northwind to relational and analytical sources.
Database connectors are in active development with our design partners. This page describes what we are building and how to influence the order.
Database connectors are in active development.
We are building secure database connectors for early design partners. If your team would benefit from one of the sources below, we want to know; demand from real teams sets the order.
What we are building, in priority order.
These are the database surfaces under active design. None are generally available yet; this page reflects what is in development, not what is shipped.
Relational sources
PostgreSQL and MySQL are first; the connector design will extend to similarly shaped sources after.
Analytical warehouses
Snowflake and BigQuery are on the short list, prioritized after relational coverage stabilizes.
Read-only by default
Connectors will be read-only at the schema level to help prevent accidental source mutation.
Scoped credentials
Connection credentials will be scoped to the smallest privilege the workflow needs.
Schema-aware ingest
Tables and columns will land as first-class sources, with types preserved and lineage tracked.
Tenant isolation
Workspace isolation is designed to extend through the connector layer; access is scoped so workspaces cannot access another workspace`s schema or data.
Incremental change capture
Connector design will support incremental change detection, so updated rows can re-ingest without full table reloads.
Audited access
Connector reads are planned to be recordable in the workspace audit trail alongside the rest of the work.
Real workflows decide what ships first.
A database connector that returns rows is easy. A database connector that holds up against schema drift, partial data, mixed encodings, and the auth quirks of a real production warehouse is the actual work. We are doing that work with a small group of design partners before opening connectors to everyone.
If you have a concrete workflow that would benefit (a reconciliation that pulls from a Postgres replica, a board metric that lives in Snowflake, a legacy MySQL you would like to bring alongside spreadsheets), tell us. We are setting priority based on demand from teams that will actually use the result.
You will see a Live status here when the connector clears that bar, not before.
- Relational connectors first; warehouses to follow.
- Read-only and scoped credentials by default.
- Schema and column-level lineage are first-class.
- Priority driven by design-partner workflows.
Tell us which database matters to your team.
If a database connector is blocking you, your input shapes the priority order. We are taking a short list of design partners now.