For the engineer in the room
The whole product, front to back.
Airbrx speaks the protocols your applications already speak, transactional and analytical alike. One data path, any workload.
The core
Six things, and nothing else on the path.
Rules engine
Serve it, or turn it away — by caller, by time of day, by identity, before it reaches the engine. Eight rules, worked through — in the exact schema the gateway runs.
Deterministic keys
Same inputs, same key. A hit returns byte-identical bytes, not a re-derivation.
Surgical invalidation
One rule’s results, never the whole cache. A pipeline call, a schedule, a rule edit or a write — each busts the subtree it should and nothing else.
Stale-while-revalidate
Answer now, refresh behind — where you have declared that trade acceptable.
Credential pass-through
The caller’s own token. Your row-level security and masking apply exactly as they do today.
Audit and rollups
One record per query, in a fixed shape — in your own bucket on a hybrid install, segregated and encrypted on SaaS.
Where it runs
Three deployment models.
SaaS, hosted by Airbrx
Nothing to run, and the lower-cost path. The gateway is on the path here — and everything it keeps is segregated per tenant and encrypted at rest, with access governed by the DPA’s controls — Airbrx doesn’t read your data.
Hybrid / cloud install
The gateway is deployed inside your network, so Airbrx’s network is never on the data path — queries and results never leave yours. Only policy sync reaches us, off the query path.
Custom install
The whole stack — Admin App included — deploys inside your perimeter. The data path and the control plane are both yours.
In every model, queries execute on your engine, under the caller’s own token — and the admin plane never sits on the query path.
Measured
One production run, with its limits named.
A real run against a real Databricks tenant, and an honest account of what it does and does not prove.
The run. Databricks gateway tenant, 29 July 2026. Open-loop, 60 queries a minute for 25 seconds, 2 distinct queries, 25 arrivals. 20 measured (5 warm-up excluded), 0 failed, 0 dropped, target rate achieved.
What it does not prove. The 100% hit rate is the workload’s design — two distinct keys — and is not a hit-rate result; do not read it as one. Latency here tracks driver roundtrips rather than cache status: 175ms median at one roundtrip (n=13), 627ms at four (n=7), and every one of those was a hit. With n=20 the tail is meaningless, so we quote the median and the roundtrip split and leave p95 alone. There was no direct-to-Databricks arm, so this is not a before-and-after. The cache was warm at the first arrival, so the run never exercised a miss-and-fill.
Don’t take our run for it. Get your own numbers.
The scan reads your own query history and tells you what the repetition is costing you — on your traffic, against your own bill.