getbusbar/busbar repository overview

⁠Busbar — Control what AI can do before it acts.

License: Apache-2.0

Busbar is the self-hosted execution boundary for AI systems. Run it in your infrastructure to govern model calls, tool use, and agent delegation before they reach approved destinations.

For traffic routed through Busbar, it:

• Admits requests by checking identity, grants, budgets, and trust.
• Governs execution with policy, credential custody, and request-path hooks.
• Executes through approved protocol, routing, failover, and evidence paths.

Applications and agents → Busbar → Models, MCP tools, and A2A agents

⁠Start with model control

Keep supported SDK workflows while centralizing provider credentials, model routing, budgets, circuit breaking, failover, and telemetry.

Busbar is a FROM scratch image: a static Rust binary plus the vetted provider catalog. No shell, libc, runtime, or sidecar. It runs as a non-root user and can be deployed in private or air-gapped environments.

⁠Quick start

Create a minimal config.yaml. Provider keys come from environment variables and do not live in configuration.

providers:
  anthropic:
    api_key_env: ANTHROPIC_KEY

models:
  claude:
    provider: anthropic
    max_concurrent: 10

Run Busbar:

docker run -d -p 8080:8080 \
  -e ANTHROPIC_KEY \
  -v "$PWD/config.yaml:/etc/busbar/config.yaml:ro" \
  getbusbar/busbar:latest

Point a supported client at http://localhost:8080 instead of the provider endpoint.

Full quickstart: getbusbar.com/getting-started⁠

⁠Execution planes

⁠Model control

Centralize supported provider credentials, routing, budgets, circuit breaking, failover, and telemetry behind one customer-operated boundary.

⁠Tool governance

Treat MCP tool calls as execution events. Enforce caller grants and budgets, validate approved schemas, and quarantine tools when their approved contract drifts.

⁠Agent trust

Verify, pin, and re-check remote A2A agent identity. Enforce configured egress scopes and use target-bound leased credentials rather than forwarding caller credentials downstream.

⁠Why run Busbar

• Static Rust binary.
• FROM scratch; no shell, libc, runtime, or sidecar.
• Self-hosted and customer-operated.
• Runs as a non-root user.
• Private and air-gap deployable.
• Native protocol continuity where supported; explicit translation where needed.
• Apache-2.0 licensed.

⁠Tags

• latest — most recent stable release.
• X.Y.Z / X.Y / X — pin the release line you want; breaking changes require a major version bump under SemVer.
• Multi-architecture: linux/amd64 and linux/arm64.
• Signed image artifacts are available for verification.

⁠Verify what you pull

Images are keylessly Cosign-signed and include GitHub build provenance.

gh attestation verify \
  oci://index.docker.io/getbusbar/busbar:latest \
  --repo MattJackson/busbarAI

⁠Learn more

• Quickstart⁠
• Architecture⁠
• Model control⁠
• Tool governance⁠
• Agent trust⁠
• Security⁠
• Benchmarks⁠
• Source⁠