# Governed agent access for the warehouses and engines you already run

> Governed AI agent access for BigQuery, Snowflake, Trino, Databricks, PostgreSQL and MySQL, with a customer identity per role and source policies preserved.

Canonical URL: https://sembric.app.arelis.digital/integrations

Integrations

Sembric connects to BigQuery, Snowflake, Trino, Databricks, PostgreSQL and MySQL with a customer identity per Sembric role. Your engine keeps enforcing its own policies; Sembric decides which certified answers an agent may receive.

Connectors

## Six sources, one governed workflow

-   Google Cloud data warehouse
    
    ### [BigQuery](https://sembric.app.arelis.digital/integrations/bigquery)
    
    Discover a BigQuery dataset and serve certified aggregates and governed views to agents, with each Sembric role impersonating its own customer service account.
    
-   Cloud data platform
    
    ### [Snowflake](https://sembric.app.arelis.digital/integrations/snowflake)
    
    Connect a Snowflake schema over the SQL API with one key-pair user and role per Sembric role, and let agents query only certified surfaces.
    
-   Federated SQL engine and lakehouse catalogs
    
    ### [Trino](https://sembric.app.arelis.digital/integrations/trino)
    
    Discover one Trino catalog and schema, including a lakehouse catalog you operate, and serve certified surfaces through role-specific read-only users.
    
-   Databricks SQL warehouse with Unity Catalog
    
    ### [Databricks](https://sembric.app.arelis.digital/integrations/databricks)
    
    Connect a Databricks SQL warehouse and one Unity Catalog schema with a separate OAuth service principal per Sembric role.
    
-   Native PostgreSQL
    
    ### [PostgreSQL](https://sembric.app.arelis.digital/integrations/postgresql)
    
    Connect an existing PostgreSQL schema over verified TLS with a restricted login per Sembric role, keeping row-level security in force.
    
-   MySQL 8.0 and 8.4
    
    ### [MySQL](https://sembric.app.arelis.digital/integrations/mysql)
    
    Connect a MySQL 8.0 or 8.4 database over mandatory verified TLS with direct read-only grants per Sembric role.
    

Every connector

## Guarantees that hold for every source

-   Source rows stay in your engine; Sembric stores only reviewed metadata, definitions and audit records.
-   Each Sembric role maps to its own narrow customer identity, so source row and column policies keep applying.
-   Only owners connect sources, test role identities or change mappings. Engineers may rediscover.
-   Every submitted statement reserves workspace read budget before contact, including catalog pages and schema reads.
-   Queries check the live schema against the certified fingerprint and refuse drift.
-   Editing or pausing a source withdraws dependent reviews and certificates atomically; resuming requires rediscovery and recertification.

A local DuckDB adapter exists for single-host pilots only; the isolated customer runtime disables it at startup.

## Put your first certified data product in front of an agent.

Tell us which warehouse you run and what your agents need to answer. We will help you connect a source, certify a first surface and query it over MCP.

[Request a pilot](https://sembric.app.arelis.digital/contact) · [Email us](mailto:contact@arelis.digital?subject=Sembric%20pilot%20request)

---

Last updated 2026-10-14. Published by Arelis AI (https://arelis.digital).