Connection recipes
Every recipe on this page is the same recipe: change your connection host from your warehouse hostname to your Airbrx gateway address. Everything else — the SQL you write, the credentials you use, the dashboards you've already built — stays exactly as it was. Pick your tool below for the per-tool specifics.
Pick your tool
Tableau
Snowflake or Databricks connector — change the server.
Power BI
Snowflake or Databricks connector — change the server.
Excel
Power Query / Get Data — same connector, change the Server field.
DBeaver
JDBC URL change. The cleanest demo of the pitch.
dbt
Update profiles.yml for tests / served queries.
Python & JDBC
Snowflake / Databricks connectors and JDBC drivers.
PostgreSQL
psql, libpq, JDBC, SQLAlchemy. Change the host, keep TLS on.
What every recipe shares
Each recipe walks through the same five things in the same order:
- The connection change. A side-by-side of your old warehouse hostname and your new gateway address — exactly what to paste into the tool's connection dialog or config file.
- Authentication. The same warehouse credentials you've always used. The Gateway forwards them to the warehouse without storing them; your warehouse remains the authority on who you are.
-
Verification. A quick check that you're hitting cache.
Look for
X-Airbrx-Cache-Status: HITin response headers (where the tool exposes them) or watch traffic in the App. - Tool-specific notes. The handful of things that are worth knowing for that tool — driver compatibility, refresh interactions, extract caching, and similar gotchas.
- Where to go next. Pointers into the rules workshop, the analytics API, and other places to deepen the integration.
For the bigger picture — why the Gateway is worth pointing at in the first place — start with What is Airbrx?
Ready to point your tool at a gateway address?
Airbrx is self-serve and live in minutes. Create an account and we'll set you up.
Create an account