Tech Stack Summary¶
The technology behind each layer. The MVP adapter/vendor map at a glance.
| Layer | Technology |
|---|---|
| Starbase | Go monolith, two binaries (API + Worker) |
| Shuttle | Go, controller-runtime (library mode, no Reconciler) |
| Customer cluster substrate | Self-managed Talos Linux + gVisor on DO droplets; Cilium CNI (self-installed, overlay); DO CCM + CSI (Kubernetes Runtime) |
| Machine-lifecycle agent | Shipyard — per-region, post-MVP (MVP = manual talosctl) |
| Frontend | Next.js |
| Primary Database | DO Managed Postgres, pgx + sqlc |
| Customer Telemetry Store | ClickHouse (per-region VM droplet) — logs (otel_logs), L7 request rows (otel_http), cAdvisor meters (otel_metrics_*); per-plan TTL retention; billing audit copy post-MVP (§39.3 #71) |
| Telemetry Collection | OTel Collector — per-node agent (app-log tail + Envoy OTel access-log sink + cAdvisor scrape, k8sattributes identity) → regional OTel gateway (per-cluster tokens, batching, sole ClickHouse writer) |
| Resource Metrics (HPA) | metrics-server (installed at bootstrap) |
| Platform Monitoring / Alerting | Grafana Cloud — hosted metrics + Grafana Alerting + OnCall, fed by a per-cluster Grafana Alloy agent (MVP-only; §35.5) |
| Telemetry Transport | DO VPC Peering — intra-region $0, cross-region reads $0.01/GiB — + per-cluster bearer auth |
| Control Plane | Starform platform (Starbase, Stardeck) on DOKS, central (one region at MVP); customer workloads on self-managed Talos; one telemetry droplet per region on a DO VM (ClickHouse + the OTel gateway, off-cluster) |
| Gateway | Envoy Gateway (Gateway API standard) |
| CDN / DNS / WAF | Cloudflare |
| TLS | Cloudflare Edge + Origin Certificates (no cert-manager) |
| Build System | Depot SaaS (remote BuildKit) + Railpack (primary frontend, MIT) + Dockerfile fallback |
| Container Registry | DO Container Registry — one per region; builds push to the placement region's registry (§16.2) |
| Job Queue | Postgres table (MVP), RabbitMQ (scale) |
| Payments | Stripe |
| Git Providers | GitHub, GitLab, Bitbucket (all active simultaneously) |
| SSO Providers | GitHub + Google at MVP (FR-005); GitLab, Bitbucket interfaces exist, deferred |
| Object Storage (customer primitive) | Tigris (Partner Integration API) — post-MVP (§39.3 #16) |
| Platform Object Storage | DO Spaces — etcd snapshots, build-log archive (never Tigris) |
| Managed Cache | DO Managed Valkey |
| Managed Database (customer) | DO Managed Postgres |
Cross-references
Where each component runs → Cluster Topology · the build system → Starforge · the observability pipeline → §35 v2 · ports & adapters (one cloud adapter active per region) → Starbase Ports · integrations (Git/SSO/payments, all active) → Starbase Integrations. Canonical map: Canonical Sources.