Binaries & Repos¶
The shippable artifacts, where each runs, and which repo it lives in — four at MVP, plus Shipyard and Mass Relay post-MVP.
| Binary | Repo | Language | Runs in | Notes |
|---|---|---|---|---|
| Starbase API | starform/starbase | Go | Infra cluster | cmd/api/main.go |
| Starbase Worker | starform/starbase | Go | Infra cluster | cmd/worker/main.go (same module) |
| Shuttle | starform/shuttle | Go | Each customer cluster | Single binary, controller-runtime |
| Frontend | starform/stardeck | Next.js | Infra cluster or CDN | Customer dashboard |
| Shipyard | starform/shipyard | Go | Regional droplet (one per region) | Machine-lifecycle agent; post-MVP (MVP = manual talosctl) — shares the DO-adapter/desired-state lib with Starbase |
| Mass Relay | starform/massrelay | Go | Telemetry droplet, in regions without DO VPC peering (DO regions keep direct-over-peering) | Egress-only telemetry query channel; post-MVP, built with the first non-DO region — dials out to Starbase, executes filtered ClickHouse reads locally; doubles as the emergency transport for a peered region (§39.3 #43) |
Starforge is a BuildService port inside Starbase Worker, not a separate binary.