Starter · free, forever
You were about to build this yourself. Don’t.
Repeated queries, a service account nobody watches, a bill that only goes up — the usual answer is a weekend spent bolting a caching layer onto the warehouse and then owning it forever. Starter is that layer, already built, and it costs nothing to find out if it helps. One dashboard, one dbt target, one team’s worth of queries — for a project that size, there is no reason to hold back.
No credit card. No form. No sales call. Log in with Google or Microsoft and your tenant exists · leaving is one hostname away
This afternoon, not next sprint
Log in. Point. Watch.
-
1
1 minute
Log in — that’s the entire signup
Google or Microsoft. No card, no form, no plan picker, no approval queue — you get a tenant on the spot.
-
2
read-only to start
Point one connection string at the gateway
One tool, one dashboard, one dbt target — your choice. Everything you don’t point at it keeps reaching the warehouse exactly as it does today.
-
3
same afternoon
Watch your own hit rate come in
Read latency, bytes served and cache hits from your own traffic — not a number we estimated for you. That’s the whole decision.
Use cases
Real problems. One rule each.
Everything below is a single rule in the schema the gateway runs — written in minutes, live on the next query. Not a project. Not a migration. A sentence about your data.
Nothing changes overnight. Your bill doesn’t know that.
The load lands at 2 a.m. and the data is settled until tomorrow night — but off-hours dashboards and cron jobs keep waking the warehouse anyway. A time-of-day rule caches hard from 5 p.m. to 9 a.m. — the window wraps midnight — and steps aside for the workday.
timeOfDay · between
A leaked token works from anywhere. It shouldn’t.
A stolen service-account token runs queries from an attacker’s laptop exactly as it does from your VPC. The engines offer an account-wide IP allowlist; here, network is one condition among many — this CIDR, that service account, those tables, outside business hours — and a match answers with an error in the caller’s own wire protocol, credentials and all, before a single query runs.
clientIp · deny
Row-level security, without giving up the cache.
“We can’t cache — everyone sees different rows” is the oldest reason warehouses run raw. Key results on user, group, role, warehouse — any mix. Teammates who see the same rows share one answer; everyone else gets their own. Your masking and RLS apply untouched, because the caller’s own token passes through.
cacheKeyElements
The write that busts exactly what it touched.
The reason caches get turned off is one stale number in front of one executive. Here an INSERT or UPDATE invalidates the cache rules it names, the moment it lands — customer queries go fresh, finance rollups and everything else stay served. Where it’s critical, a failed invalidation blocks the write itself.
invalidateRules · on DML
Freshness that follows your load schedule.
Yesterday’s numbers are correct until the next load — so say that. Declare the freshness your schedule implies and entries expire on the clock, with no call at all. Want it exact instead? The pipeline’s last step makes one API call and that rule’s cache is stale, everywhere, immediately.
ttlSeconds · markers API
One prompt becomes forty near-identical queries.
AI agents explore, retry, and never get tired — machine pace against per-second billing. Behind the gateway the repeats land on the cache instead of the meter, and every statement an agent runs lands in the same query log as everything else — so “what has AI been asking our data?” is a query, not a project.
same protocol · same record
Every card above is real schema, not roadmap — eight worked examples and the full rule reference show the JSON.
What you get, at $0
Not a trial. Not a sandbox. The real gateway.
Starter
$0
Individual analyst / evaluation · pay-as-you-go
- 1 tenant
- ABUs metered, no minimum
- AI Rule Generation view only
- Full query log & rollups, in your own bucket
Land
No credit card. No form. No plan picker. No approval queue. Google or Microsoft, and it’s yours before the dashboard finishes loading.
Growth, Pro and Enterprise exist for when a tenant, tenants, or scale genuinely outgrow this — not because Starter is a teaser. Compare every plan.
Before you ask
The questions an engineer asks before signing anything.
Is this actually free forever, or a trial that converts?
Starter has no platform fee and no expiration date. For a project the size Starter is built for — one dashboard, one pipeline, one team’s queries — play with it for as long as you want. You pay only metered ABUs as you go, with no minimum. Pro is the 30-day trial, not this.
What do you see, and what do you never see?
The caller’s own token passes straight through, so your row-level security and masking apply exactly as they do today — we never hold your credentials. One record per query is written to your own bucket. Result rows and raw credentials are never recorded. More in trust and security.
What if I still end up building it myself?
Point the hostname back at the warehouse and you are native again in minutes — there is no driver to uninstall and no copy of your data on our side to retrieve. Trying Starter first costs you nothing you can’t get back.
The part where you come in
Then show us what you built.
Starter isn’t a demo we’re guarding — it’s the real gateway, handed over to see what engineers do with it. Cache a homelab Postgres. Put a time-of-day rule in front of a side project. Find an edge we didn’t. The clever rules people write teach us what to build next, and we genuinely want to see yours — post them on r/airbrx, where the team actually hangs out.
Stop building. Start pointing.
No credit card. No form. No sales call. Log in and you have a tenant — by the time the dashboard loads, it’s already yours.
No card · no form · read-only · nothing to install