Connect your warehouse to Airbrx
Paste your warehouse URL. The App auto-detects Snowflake or Databricks.
The Gateway is wire-compatible with Databricks and Snowflake. It needs the same connection details those tools normally need — a hostname, maybe an HTTP path, the warehouse identifier — so it can forward requests when the cache misses. Credentials are not part of this configuration; those flow through with each query at runtime, untouched and unstored.
In the App, the configuration card looks like this
Paste your warehouse URL and the App auto-detects the adapter type (Databricks vs Snowflake) and pre-fills the fields below. You'll review and save; that's the whole step. The fields are described next so you know what you're confirming.
Pick the adapter
The tenant configuration screen offers two adapter types. Pick the one that matches your warehouse:
For Databricks SQL Warehouses (any region, any cloud). Needs server hostname and HTTP path.
For Snowflake (any region, any cloud). Needs server hostname only.
Fill in the fields
Databricks
- Server hostname
- Your Databricks SQL Warehouse hostname — e.g.
dbc-1234567890.cloud.databricks.com. The Gateway forwards requests here when the cache misses. - HTTP path
- The HTTP path of the SQL Warehouse — e.g.
/sql/1.0/warehouses/abc123. Find this in the Databricks SQL Warehouse details page under "Connection details."
Snowflake
- Server hostname
- Your Snowflake account host — e.g.
your-account.snowflakecomputing.com. The full account identifier including region and cloud, not just the account name.
What's not on this screen
- Credentials. Whoever connects through the gateway address provides their own warehouse credentials. The Gateway forwards them to your warehouse without storing or inspecting them. See Security posture.
- The warehouse / database / role. Those vary per query and stay on the BI tool's side of the connection. You don't configure a "default warehouse" at the tenant level.
- Cache rules. Step 5. The tenant works fine with no rules — every query just passes through to the warehouse. Caching starts when you author the first rule.
What you should see
After saving, the tenant's status switches from "unconfigured" to "ready." The App shows the live runtime topology — your clients on the left, your gateway address in the middle, your warehouse on the right:
The traffic page is still empty (no BI tool has connected yet) but the Gateway is ready to receive traffic. Step 4 sends some.
If something goes wrong
- The save fails with a validation error. Re-check the server hostname for typos — the form validates the shape but not the reachability of the host.
- You picked the wrong adapter. Switch it. Tenant adapter type is changeable until traffic starts flowing through; once there's cached traffic, switching adapters effectively means starting fresh.
-
HTTP path is hard to find. In Databricks, open the
SQL Warehouse, look at the Connection details tab; the path looks like
/sql/1.0/warehouses/<some-id>.