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.

Authentication
Your warehouse credentials, untouched
SQL dialect
Snowflake / Databricks, as-is
Latency
Cache hits in milliseconds
Security
RLS & masking preserved

Pick your tool

What every recipe shares

Each recipe walks through the same five things in the same order:

  1. 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.
  2. 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.
  3. Verification. A quick check that you're hitting cache. Look for X-Airbrx-Cache-Status: HIT in response headers (where the tool exposes them) or watch traffic in the App.
  4. Tool-specific notes. The handful of things that are worth knowing for that tool — driver compatibility, refresh interactions, extract caching, and similar gotchas.
  5. 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 in private preview. Create an account and we'll set you up.

Create an account