Writing from the Airbrx team on data architecture, warehouse cost, and the engineering doctrine behind the Airbrx Gateway — the ideas we keep coming back to, cached here so you don't have to wake the warehouse for them.
Seven data center projects in the Columbia Gorge have asked for about 5,450 megawatts, more than the four lower Columbia dams make in a typical year. Follow one dashboard refresh, computed and billed 21 times, to see how much of that load is the same answer again, and why taking out the repeats pushes the next building out.
Read the articleConnecting an agent to the warehouse takes an afternoon. Running one against production data takes a control plane, and most teams find that out from the bill. The peak is "just give it a login." The valley is the invoice, then the incident. The way out is something in the query path, and you don't have to walk the valley to get there.
Read the article SecurityThe July 2026 agent intrusion spent 24 to 48 hours fuzzing its way out, and nobody noticed. Fuzzing is failure by design — malformed frames, auth attempts that never open a session, queries against databases that don't exist — so almost none of it reaches the warehouse to land in an audit view. The footprint is at the gateway, where the refusals are.
Read the article Engineering DoctrineGitHub opened an incident at 14:17 UTC for degraded Grok models in Copilot. Nothing GitHub operates failed, and their customers still had a bad morning. Twelve of GitHub's last fifty incidents cite an upstream AI model provider — the argument for putting the model beside the request path instead of in it.
Read the article ProductPoint a tool at your Airbrx hostname and nothing changes. Queries pass through to your warehouse untouched — we just log them, so we can show you where the repeats are. You turn up caching when, and only where, you want. Start with the noisiest tool you've got, and decide about everything else later — or never.
Read the article Cost & FinOpsTableau extracts and Power BI Imports are data islands by another name. The hidden costs — drift, sync work, eroded trust, a growing archipelago of slightly-different copies of the same truth — never make it into the business case. The fix that doesn't require another island.
Read the article ArchitectureReduce compute, reduce costs. The Airbrx Gateway is the flat-stack doctrine shipped as a product — a sleeping warehouse, predictable keys, surgical cache-busting, gateway-layer security, and scale-to-zero. The reason no traditional stack could have built it is the reason it works.
Read the article Engineering DoctrineThe public edition of the doctrine we build by. The cloud made adding infrastructure free, so stacks bloated — and AI removed the last bit of friction that used to force a moment of thought. Flat-stack puts the discipline back: use almost nothing, keep your center of gravity low, and make every dependency a decision someone made on purpose.
Read the manifestoNothing filed under this theme yet. More writing is on the way — check back soon.
The scan reads your own query history and tells you what the repetition is costing you.
Read-only · your token is never stored · nothing to install