Connect the data you have. Keep the tools you use.
Connect databases on your own servers or in AWS, Azure and Google Cloud, Microsoft Fabric, Dynamics 365 and data lakes, with connector-specific caching and configurable result retention. Explore data in ZeaData, or bring governed results into Excel, Power BI, Teams and AI assistants.
Sources
Databases and Fabric are queried where they are; lake tables are cached inside your deployment for analysis. Connections are read-only. Credentials are encrypted, and in a private deployment the key is in your own Key Vault.
Databases
Queried live where they are, read-only.
PostgreSQL
Read-only, with an account you create for ZeaData.
MySQL
Read-only, with an account you create for ZeaData.
MariaDB
Through the MySQL connector, read-only, with an account you create for ZeaData.
SQL Server
Read-only, with a SQL login or Microsoft Entra sign-in. Each person's identity can be passed through so the row-level security you already set keeps applying.
Azure SQL Database and Managed Instance
The SQL Server connector, with the same Entra sign-in and pass-through of each person's identity.
Managed databases in the cloud
The same engines run by your cloud provider, reached with the connectors above over the network you allow.
Amazon RDS
PostgreSQL, MySQL, MariaDB and SQL Server instances.
Amazon Aurora
PostgreSQL- and MySQL-compatible clusters.
Azure Database for PostgreSQL and MySQL
Flexible servers, with an account you create for ZeaData.
Google Cloud SQL
PostgreSQL, MySQL and SQL Server instances.
Microsoft Fabric and business apps
Fabric warehouses and lakehouses, Dynamics 365 and Power Apps data, and SharePoint content.
Microsoft Fabric
Read-only T-SQL on warehouse and lakehouse SQL analytics endpoints, signed in with a service principal, a managed identity or each person's own sign-in so Fabric's permissions apply. Questions run live.
OneLake
Delta tables read at their current version into a cache inside your deployment, with no ingestion pipeline to build.
Dynamics 365
Sales, service and other Dynamics 365 data through the read-only Dataverse endpoint, or the tables Link to Microsoft Fabric lands in OneLake, tagged bronze, silver and gold.
Power Apps (Dataverse)
Tables in your Dataverse environments, through the same read-only endpoint.
SharePoint
Sites, lists and document libraries through Microsoft Graph, with an app registration you control.
Lakes, storage and files
Files read in place, cached inside your deployment for analysis.
Azure Data Lake Storage and Blob
Delta, Parquet, CSV and JSON files, read in place and cached inside your deployment for analysis.
Amazon S3
The same formats, from the buckets you give ZeaData read access to.
MinIO
Self-hosted S3-compatible storage inside your own network.
Wasabi
S3-compatible cloud storage, read through the same connector.
Delta Lake
Delta tables read at their current version, in any of these stores.
Apache Parquet
Every folder of Parquet, CSV or JSON files becomes a table.
CSV and Excel uploads
Files people upload (.csv, .xlsx, .xls), analyzed inside ZeaData with sensitive columns masked for the AI by name.
Bring your rules and lineage
Keep the tests and definitions your data team already maintains.
dbt
Tests from manifest.json become quality rules, run_results.json records your pipeline's results, metric definitions import into the semantic layer, and models feed lineage.
Great Expectations
Expectation suites import as quality rules, with their warning levels.
Soda
Soda checks import as quality rules, with their warning and failure levels.
OpenLineage
Lineage events import alongside the lineage ZeaData builds from your catalog, views and queries.
Results from your pipelines
Send the result of any check to ZeaData's results API and it appears with the rest of the product's quality.
Where answers go
Every outlet uses the same governed path as chat and dashboards, and administrators can switch exports and feeds off for the whole organization.
Tools your teams use
Governed data in the apps people already have open.
Excel
Snapshot downloads, and a refreshable workbook connected through Power Query, signed in with a personal data key or the organizational account.
Power BI
An OData v4 feed, with the person's own access on every refresh.
Microsoft Teams
Dashboard KPIs and their change posted to a channel through a Teams workflow, on a schedule or on demand.
SharePoint
A dashboard as a PDF in a SharePoint folder, through Microsoft Graph.
Email
Scheduled dashboard emails computed for each recipient, data alerts and notifications through your SMTP server.
AI assistants and models
Assistants act as their owner, and the model that writes SQL runs where you choose.
Claude
Add ZeaData as a custom connector in Claude, on the desktop or at claude.ai, to list and query certified metrics and governed data over MCP, as its owner.
Microsoft Copilot Studio
Copilot Studio agents add ZeaData as an MCP tool, signed in with a data key.
Other MCP assistants
Other assistants that support MCP, signed in with their owner's data key or Microsoft Entra token.
Azure OpenAI
The model for questions and summaries, in your own Azure subscription.
OpenAI and compatible endpoints
The OpenAI API or another OpenAI-compatible endpoint you approve. ZeaData calls only the hosts on your allow-list.
Sign-in and keys
Microsoft Entra ID
Single sign-on, with groups and person attributes kept in step for row rules.
Azure Key Vault
In a private deployment, the key that encrypts connection credentials stays in your own Key Vault.
On request
We add these connectors for customers who need them. Tell us what you run and we will plan the connector with you.
Snowflake
Google BigQuery
Databricks
Oracle Database
SAP
ClickHouse
Trino
MongoDB
Redis
Google Sheets
Product names and logos belong to their owners. They show which systems ZeaData works with and do not imply endorsement.