Skip to content

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)
Frontend Next.js
Primary Database DO Managed Postgres, pgx + sqlc
Billing Audit / Logs ClickHouse (per-region VM droplet)
Customer Metrics VictoriaMetrics (per-region VM droplet) + vmagent (sources: Envoy Gateway, kubelet/cAdvisor, kube-state-metrics)
Resource Metrics (HPA) metrics-server (installed at bootstrap — not bundled on DOKS)
Platform Monitoring / Alerting Grafana Cloud — hosted metrics + Grafana Alerting + OnCall, fed by a per-cluster Grafana Alloy agent (MVP-only; §35.5)
Log Shipping Fluent Bit (per-node agent) → Vector (regional aggregator) → ClickHouse
Telemetry Transport DO VPC Peering — intra-region $0, cross-region reads $0.01/GiB — + per-cluster bearer auth
Control Plane Central (one region at MVP); telemetry stores per region on DO VM droplets (ClickHouse + VictoriaMetrics, separate droplets, 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
Job Queue Postgres table (MVP), RabbitMQ (scale)
Payments Stripe
Git Providers GitHub, GitLab, Bitbucket (all active simultaneously)
SSO Providers GitHub, GitLab, Bitbucket, Google (all active simultaneously)
Object Storage Tigris (via Partner Integration API)
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 · ports & adapters (one cloud adapter active per region) → Starbase Ports · integrations (Git/SSO/payments, all active) → Starbase Integrations. Canonical map: Canonical Sources.