Connectors for the stack you already run
Bring the file your tools already produce — a dbt manifest, a registry dump, a warehouse extract. No passwords.
Connect dbtShowing 26 of 26 connectors in Alls
Airbyte
Govern the catalog every sync trusts - before a silent type change lands in the warehouse.
Connect Airbyte →Apache Airflow
Govern the scheduler that already knows your freshness, ownership, and lineage.
Connect Apache Airflow →Confluent
Put meaning under every Kafka subject the Schema Registry already inventories.
Connect Confluent →Databricks
Give Unity Catalog something to check thousands of columns against.
Connect Databricks →dbt
Meaning has no home in dbt. Bring a manifest; we turn `accepted_values` into a vocabulary you can govern and your agent can read.
Connect dbt →Google BigQuery
Turn INFORMATION_SCHEMA from an inventory into a contract you can audit.
Connect Google BigQuery →JSON Schema
Stop asking a validator four questions it was only built to answer one of.
Import a JSON Schema file →Salesforce
Govern the org whose schema can change in forty seconds from Setup.
Connect Salesforce →Snowflake
Your Snowflake schema is not a contract. Generate one from the governed model.
Connect Snowflake →Apache Avro
One governed reading of the schema that currently lives in four places.
Import a Apache Avro file →AWS Glue
Stop treating a crawler snapshot as the meaning of your lake.
Connect AWS Glue →Azure Synapse
Record the constraints that die on the way to a registered schema.
Connect Azure Synapse →cBioPortal
Govern the four comment rows that are the schema of your study.
Connect cBioPortal →JSON-LD
Make the vocabulary you already trust executable downstream.
Import a JSON-LD file →LinkML
Let the pipeline read the model that is already right.
Import a LinkML file →MACH ODM
Stop shipping a recollection of the standard as if it were the standard.
Import a MACH ODM file →Microsoft Fabric
Catch the warehouse type change that never pages anyone.
Connect Microsoft Fabric →Neo4j
Write down the graph schema MERGE has been inferring for you.
Connect Neo4j →ODCS
Make the contract a derived artifact of governed meaning, not a YAML twin of the table.
Import a ODCS file →Open Semantic Interchange
Put two revenue numbers next to the same definition.
Connect Open Semantic Interchange →OWL
Keep the ontology and the application schema from becoming two portraits of Person.
Import a OWL file →Protocol Buffers
Carry reserved field numbers with the meaning, not only with the .proto file.
Import a Protocol Buffers file →REDCap
Diff the codebook so a study change is a review, not a memory.
Connect REDCap →Schema Converter
A neutral hub between fourteen schema formats, with an honest lossiness ledger.
Connect Schema Converter →ShEx
Keep the four assertions in every shape constraint from dying in a hand copy.
Import a ShEx file →SQL
Give the column nobody can explain a rule the database can actually carry.
Import a SQL file →