Blank BigQuery project
A preconfigured home for governing your BigQuery estate — bring your extract now or later.
Data EngineerRelated use →
Cloud Warehousevendor
Connect Google BigQuery
Turn INFORMATION_SCHEMA from an inventory into a contract you can audit.
How CoreModels works with Google BigQuery
BigQuery’s information schema is fast, free, and complete. It answers what the estate looks like right now. It does not answer what the estate is supposed to mean, who approved the last type change, or which tables are undocumented on purpose versus by accident.
CoreModels imports that metadata as types and elements, records the first audit, and treats every later extract as a candidate for drift. The estate documentation audit recipe flags tables and columns that never received a description. Generate-back emits DDL aligned with governed types so the warehouse and the model do not fork.
Wire the CI drift gate and a pull request that retypes a revenue column fails with the column named — before the query still runs and the number is quietly wrong.
Recipes
Recipes
Recipes for Google BigQuery
CI Drift Gate for BigQuery
Fail the Dataform/Terraform PR when the estate drifts from the governed model.
Data EngineerRelated use →
Estate Documentation Audit
Find every undocumented table and every ungoverned STRUCT/ARRAY/JSON payload.
Data StewardRelated use →
First Governed Import for BigQuery
Turn one INFORMATION_SCHEMA query into a governed estate.
Data EngineerRelated use →
Generate BigQuery DDL from the Governed Model
Close the loop: meaning goes back where BigQuery users actually read it.
Data EngineerRelated use →
Uses
Problems this connector fixes
Articles that explain the gap, then point at the recipe that closes it.
Problem
A Complete Answer That Tells You Nothing: The BigQuery Metadata Problem
There is a query most BigQuery engineers can write from memory. Select from `INFORMATION_SCHEMA.COLUMNS`, join `TABLES`, and you get a perfect inventory of the estate: every table, every column, every `data_type`, every `is_nullable` flag, in order. It is fast, it is free, and it is complete.
Recipe: Estate Documentation Audit
OutcomesThe First Thing You Notice Is What Stops Happening
Govern a BigQuery estate with CoreModels and the change is less a new capability than an absence. The archaeology stops. The "does anyone know what this column is" thread stops. The quarterly scramble to work out what changed since the last review stops, because the answer is already written down, dated, and fingerprinted.
Recipe: CI Drift Gate for BigQuery · Estate Documentation Audit · First Governed Import for BigQuery · Generate BigQuery DDL from the Governed Model
GovernanceFollow One Column: Where the Machine Stops and a Person Starts
Trust in a governance tool is not established by a promise on a landing page. It is established by being able to point, precisely, at the places where automation ends and human judgement begins — and by those places being the same ones every time.
EcosystemThirteen Connectors, One Model: Where BigQuery Fits
Ask a CoreModels deployment which vendors it knows and it will tell you at runtime. The vendors endpoint returns every registered connector with its key, display name, capabilities and the artifacts it expects: `bigquery`, `snowflake`, `databricks`, `fabric`, `glue`, `dbt`, `confluent`, `airbyte`, `airflow`, `neo4j`, `salesforce`, `redcap`, `cbioportal`.
AgentsWhat Your Agent Reads in the Four Seconds Before It Writes the Query
The interesting question about AI agents and BigQuery is not whether an agent can write SQL. It plainly can. The question is what it consults in the moment before it does.
QuickstartYour First BigQuery Drift Audit with CoreModels
*Zero to a recorded schema audit of a BigQuery dataset: one SQL query, two HTTP calls, no credentials shared.*
Recipe: Blank BigQuery project · First Governed Import for BigQuery · Generate BigQuery DDL from the Governed Model
APIThe CoreModels BigQuery Integration, Route by Route
*The complete HTTP surface for governing a BigQuery estate: every verb, every role, every payload.*
MCPGoverning BigQuery from an AI Agent over MCP
*The same import–audit–generate loop, driven by tool calls instead of curl — including how agents ship multi-megabyte extracts.*
AutomationA CI Drift Gate for BigQuery: Fail the PR, Not the Dashboard
*Turning the CoreModels schema audit into an automated gate — the v1 API, `errorCount` semantics, the badge, the history trail, and the two directions drift can come from.*
Recipe: CI Drift Gate for BigQuery
Deep diveInside the BigQuery Connector: How an Estate Becomes a Governed Graph
*What actually happens between a flat JSON extract and a queryable governed model — identities, type mappings, metadata mixins, audit rules, and the approximations we admit to.*
Recipe: Estate Documentation Audit