Federate everyengine you own
45 sources across 8 categories — relational, cloud-managed, warehouses, NoSQL, streaming, files, APIs and SaaS. Every connector pushes down what it can; DuckDB federates the rest.
45
data sources
5
native relational engines
8
cloud-managed variants
8
data warehouses
4
output protocols
45 sources across 8 categories
Pushdown class shown per connector. Federation across mixed engines is stitched in DuckDB — full lineage preserved.
Relational
Cloud & Managed
Connects via native engine protocol — Aurora/RDS as Postgres or MySQL, Cloud SQL as PG/MySQL/MSSQL
Data Warehouses
NoSQL, Graph & Search
Streaming & Events
Consume topics as virtual tables with schema registry support
Files & Object Storage
APIs & SaaS
Federation & Legacy
Migration, interoperability and generic connectors
Four protocols, one governed view
Every published view is reachable across all four channels — same RBAC, same masking, same audit log.
SQL (pgwire)
PostgreSQL wire protocol. psql, JDBC, DBeaver, Metabase, dbt — any PG-compatible client connects natively.
REST API
JSON over HTTPS. Per-view endpoints, signed responses, OpenAPI spec auto-generated.
MCP for AI
Model Context Protocol. Every view is also a typed MCP tool with RBAC and audit per call.
JDBC / ODBC
Driver bundles for Java and ODBC tooling. Same governed surface as pgwire — different protocol.
What infra leads ask first
Plain answers about connection types, pushdown classes, custom connectors and tenant isolation.
Yes. Enterprise plans include a custom connector via the SDK — we've shipped connectors for SAP HANA, proprietary mainframe drivers and internal data APIs under NDA. Most take 1–2 weeks of joint engineering.
// connect anything
Wire your first sources in an afternoon.
Trial includes all native connectors + JDBC bundle. Custom connector and ODBC available on Enterprise.