Supported engines

Airbrx supports three engines today: Databricks, Snowflake, and PostgreSQL. Each one is spoken in its own native wire protocol, which is what lets you change a hostname instead of changing a driver.

The three engines

EngineProtocolHow you connect
Databricks Thrift binary over HTTP, plus the JSON statement API Change the server hostname on your existing connection; keep the HTTP path.
Snowflake REST/JSON over HTTPS Change the account hostname on your existing connection.
PostgreSQL PostgreSQL wire protocol over TCP Point the host at your gateway address on port 5432. TLS is required.

MySQL and SQL Server are not supported yet. If you need one of them, tell us, since it changes how they get prioritized.

Why native protocol, not a vendor SDK

The Gateway speaks each warehouse's own protocol, so to your driver it looks like the warehouse itself. That is why "no code changes, no refactoring" is a description rather than a promise.

The practical consequence for you: your driver, your connection string format, your credentials, and your existing warehouse-side grants all keep working. There is no Airbrx driver to install.

What is the same on every engine

Behavior does not fork by engine:

PostgreSQL specifics

PostgreSQL works a little differently from the two warehouse connections, because a Postgres client authenticates before it says anything else. The things worth knowing:

TLS is mandatory

A client that tries to skip the TLS upgrade — sslmode=disable — gets a clean error and the connection closes. It is never silently downgraded to plaintext. Set sslmode to require or stricter.

Routing

The Gateway resolves your tenant from the TLS SNI name. If your client sends SNI — most do — routing is automatic. Where it does not, the Gateway falls back to reading the database field as your gateway address, so psql "dbname=<your-gateway-address>" routes correctly too.

Three ways to authenticate, none of which hand us a credential

ModeUse it when
relay Your backend uses short-lived tokens — RDS IAM auth, Azure Entra — or your policy forbids the Gateway participating in auth at all. The entire exchange is relayed byte for byte between client and backend; the Gateway never inspects credential material.
verifier-proxy You want a real SCRAM-SHA-256 exchange. The exchange is checked against your own database, and the Gateway never sees a plaintext password. Supported on self-hosted PostgreSQL, Neon, and Supabase.
cleartext The simplest option: a password over the mandatory TLS channel.

There is no fourth option where you store a warehouse username and password in your tenant configuration. That field does not exist in the schema. An auth mode is required — a PostgreSQL tenant without one is rejected at configuration time.

Simple and extended query

Both the simple and extended query protocols are supported, and both integrate with the cache.

COPY, notifications, and cancel

The rest of the protocol is relayed as a direct connection would see it: COPY in both directions, LISTEN/NOTIFY (delivered while the session is idle), notices from RAISE NOTICE, ParameterStatus changes such as SET TimeZone, and the fast-path FunctionCall. A bad row in COPY FROM fails the copy with the backend's error and leaves the connection usable. COPY is never cached.

Cancel works over TLS only, like every other Gateway connection. libpq 17 and later send cancels over TLS, so psql Ctrl-C and psycopg cancels work. pgjdbc and libpq before 17 send cancels in plaintext, which the Gateway refuses.

Current limits:

Routine deploys

You should not see a query killed mid-execution by a routine Gateway deploy.

Where to go next

Point your engine at the Gateway

Databricks, Snowflake, and PostgreSQL all work through the same connection change. Create an account and try it.

Create an account