COMMUNITY

Built in the open. Moved by the people who use it.

Go teams building AI products face a real choice: Python interop, fragile bindings, or incomplete libraries. Beluga is the answer built entirely in Go — testable, deployable, reasoned about with standard Go tooling. MIT licensed. The roadmap is public. The issues are public. The code review is public.

WHY GO

Three reasons, no manifesto.

01

Deterministic concurrency

context.Context is the cancellation, tracing, tenant, and auth story in one primitive. Goroutines are cheap but bounded by worker pools, not sprayed on hope.

02

Single-binary deployment

Ship one binary to production. No Python venv, no node_modules, no wheel compilation on the target. Docker images are tens of megabytes, not gigabytes.

03

Compile-time safety

Generics carry types through the Stream[T] pipeline. interface never appears in public APIs. Refactoring agents is a type-checked operation, not a grep.

CONTRIBUTING

The ladder is short.

  1. File a good first issue. Issues tagged good-first-issue are small, self-contained, and reviewed within 48 hours.
  2. Read the architecture. The seven-layer model and the four extensibility rings are the entire mental model — see Concepts.
  3. Send a PR. Red/Green TDD, table-driven tests, go vet ./..., gosec, govulncheck pass locally. CI runs the same plus Snyk, Trivy, CodeQL, SonarCloud.
  4. Become a maintainer. A sustained record of merged PRs, thoughtful reviews, and Discussions participation. We name maintainers in public.
Read the contributing guide →
ROADMAP

Four phases shipped. One in progress.

01 Foundation complete

core · schema · config · o11y · resilience · streaming via iter.Seq2

02 Capabilities complete

llm · tool · memory · rag · voice · guard · prompt · cache

03 Runtime complete

agent · runtime · orchestration · protocol (MCP / A2A / REST / gRPC / WS)

04 Production complete

workflow durability · audit · cost · auth · eval · HITL · enterprise observability

05 Next in progress

stability hardening, expanded provider catalog, documentation pass — shaped by Discussions

Shape phase 05 in GitHub Discussions. No promise grid — only merged milestones.

MIT. That's it.

Use Beluga in a closed-source product. Fork it. Rewrite it. We ask that you contribute improvements back so the next person who hits the same edge case does not have to rediscover the solution — but we will not force you.

Read the license →