Skip to content
SQLAnvil SQLAnvil SQLAnvil

Warehouse connections

A project’s warehouse connection tells Cloud where your models run. You set it from Settings → Warehouse.

Fields

Section titled “Fields”
  • Type — the adapter SQLAnvil compiles for: supabase, postgres, bigquery, or mysql. This matches the warehouse: in your project’s workflow_settings.yaml.
  • Region — where your warehouse runs (e.g. us-east-1). Used to reach the right connection endpoint.

These describe the shape of the connection. They’re safe to store and appear in the dashboard.

Credentials are brokered, not stored

Section titled “Credentials are brokered, not stored”

SQLAnvil Cloud does not keep your database password or service-account key. Connections are brokered at run time — the runner obtains a short-lived credential for the specific run and discards it. This is the “custodian → broker” principle: Cloud orchestrates access without holding long-lived secrets.

For branch CI, this goes a step further: rather than touching your production database, SQLAnvil provisions a disposable ephemeral branch of your warehouse, runs against that, and destroys it — so a PR never writes to production. See Supabase connections.

Compilation overrides

Section titled “Compilation overrides”

Alongside the connection, a project carries compilation overrides — default database, schema suffix, and table prefix — that shape how your SQL compiles per environment.