<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Busbar</title>
    <link>https://getbusbar.com/blog/</link>
    <description>Notes from Busbar on AI control-plane reliability, fidelity, and performance.</description>
    <language>en-us</language>
    <lastBuildDate>Wed, 15 Jul 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://getbusbar.com/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Headroom: a compression hook that reports its own savings</title>
      <link>https://getbusbar.com/blog/headroom-compression-hook/</link>
      <guid>https://getbusbar.com/blog/headroom-compression-hook/</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <description>Context compression belongs on the request path, not bolted onto your app. Busbar runs it as a rewrite gate: prompt text in, a smaller body out, before routing and before dispatch. And because the hook self-describes its settings and self-reports its metrics, you configure it and read its savings entirely through the frozen Admin API — no second dashboard.</description>
    </item>
    <item>
      <title>Busbar 1.3: your code on the request path</title>
      <link>https://getbusbar.com/blog/busbar-1-3-the-api-release/</link>
      <guid>https://getbusbar.com/blog/busbar-1-3-the-api-release/</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <description>Hooks put your logic on the normalized request path across all six protocols. Auth becomes a pluggable chain you can compile out. And the admin API v1 is frozen: the surface tools get to build on.</description>
    </item>
    <item>
      <title>Run Claude Code through Busbar</title>
      <link>https://getbusbar.com/blog/run-claude-code-through-busbar/</link>
      <guid>https://getbusbar.com/blog/run-claude-code-through-busbar/</guid>
      <pubDate>Mon, 13 Jul 2026 00:00:00 GMT</pubDate>
      <description>Point Claude Code at Busbar with one environment variable — get observability, failover, and budgets for the agent you already use. Then the twist: because Busbar translates between protocols, you can point Claude Code at a Gemini or Bedrock model instead.</description>
    </item>
    <item>
      <title>The smart router you want is a hook</title>
      <link>https://getbusbar.com/blog/smart-routing-today/</link>
      <guid>https://getbusbar.com/blog/smart-routing-today/</guid>
      <pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate>
      <description>Everyone asks for automatic model selection by task, latency, quality, and cost. It is not a product, it is a hook. Busbar runs yours two ways: a compiled Rust binary on a local socket that decides in about 8 microseconds, or a webhook in any language. Both wired to the same failover and fail-safe machinery.</description>
    </item>
    <item>
      <title>Busbar 1.2: more than chat</title>
      <link>https://getbusbar.com/blog/busbar-1-2-more-than-chat/</link>
      <guid>https://getbusbar.com/blog/busbar-1-2-more-than-chat/</guid>
      <pubDate>Fri, 10 Jul 2026 00:00:00 GMT</pubDate>
      <description>Embeddings, moderations, image generation, and audio (transcription and speech) now run through Busbar, and every one is cross-protocol. A Gemini client can call embeddings on Bedrock, an OpenAI client can route images and audio to Gemini, and every answer comes back in the caller's own dialect. Lossless, both ways.</description>
    </item>
    <item>
      <title>Valuable before the second provider exists</title>
      <link>https://getbusbar.com/blog/valuable-before-the-second-provider/</link>
      <guid>https://getbusbar.com/blog/valuable-before-the-second-provider/</guid>
      <pubDate>Thu, 09 Jul 2026 00:00:00 GMT</pubDate>
      <description>Why a control plane earns its keep with one provider: key custody, hard caps, and real metrics on day one, plus an option you can exercise mid-incident.</description>
    </item>
    <item>
      <title>Busbar, in numbers</title>
      <link>https://getbusbar.com/blog/busbar-in-numbers/</link>
      <guid>https://getbusbar.com/blog/busbar-in-numbers/</guid>
      <pubDate>Wed, 01 Jul 2026 00:00:00 GMT</pubDate>
      <description>A fast, lightweight, single-binary AI control plane isn't my roadmap. It's what shipped. Straight answers on memory, latency, throughput, reproducibility, and what you actually deploy.</description>
    </item>
    <item>
      <title>Busbar 1.0 is stable</title>
      <link>https://getbusbar.com/blog/busbar-1-0-stable/</link>
      <guid>https://getbusbar.com/blog/busbar-1-0-stable/</guid>
      <pubDate>Sun, 21 Jun 2026 00:00:00 GMT</pubDate>
      <description>The HTTP API, config schema, and six wire-protocol contracts are now frozen under Semantic Versioning, hardened across a multi-round security and correctness audit. It's production-ready.</description>
    </item>
    <item>
      <title>Busbar 1.0.0-rc.1, the first release candidate</title>
      <link>https://getbusbar.com/blog/rc1-first-release-candidate/</link>
      <guid>https://getbusbar.com/blog/rc1-first-release-candidate/</guid>
      <pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate>
      <description>From an empty repo to a feature-complete, API-stable release candidate. Six protocols, lossless translation, in-flight failover, and fault-attributed breaking, in one Rust binary.</description>
    </item>
    <item>
      <title>Why I'm building Busbar</title>
      <link>https://getbusbar.com/blog/why-im-building-busbar/</link>
      <guid>https://getbusbar.com/blog/why-im-building-busbar/</guid>
      <pubDate>Fri, 01 May 2026 00:00:00 GMT</pubDate>
      <description>As teams go multi-model, the control plane becomes critical infrastructure, and 'flatten everything to OpenAI and retry on failure' isn't enough. Before I write a line of code, here's what I'm setting out to build.</description>
    </item>
  </channel>
</rss>
