Busbar 1.0 is stable

Busbar 1.0 is here, and it’s stable. After the release-candidate window of soak, audits, and fixes, I’m ready to make the promise that 1.0 represents.

What “stable” means

• Frozen contracts. The HTTP API, the configuration schema, and the six wire-protocol contracts are stable under Semantic Versioning. No breaking change without a major-version bump. You can build on Busbar and trust the surface won’t move under you.
• Hardened. 1.0 went through multiple rounds of security and correctness review: SSRF-safe upstreams, constant-time token comparison, parameterized SQL, secret-free logs, request-body caps, and native-protocol error envelopes that leak no internals.
• Complete where it counts. Lossless cross-protocol translation across all six protocols (both directions, streaming included), fault-attributed per-lane circuit breaking, in-flight streaming-safe failover, and key-scoped governance for budgets, rate limits, and access control.

Still one binary

Everything above ships as a single static Rust binary. No interpreter and no garbage collector anywhere in the request path. Linux and macOS on Intel and ARM, Windows on Intel. Your keys stay on your network.

What’s next

From here the work is depth: more providers, richer routing policy, deeper observability, on top of a surface that no longer moves. The reliability and fidelity guarantees are the part I care most about keeping honest, and they’re now locked in.

Get it at getbusbar.com. If you’re running multi-provider LLM traffic in production, I’d love to talk. I’m taking on design partners.