Control Plane Roadmap

The managed control plane is a future SaaS layer above the FOSS core substrate.

What It Adds

• Fleet enrollment UX (add/remove repos, orgs, runner pools via web UI)
• Tenant and pool management (multi-org billing, resource quotas)
• Usage reporting and cost visibility (runner-minutes, cache hit rates, trend)
• Cache and runner observability (dashboards, alerts, diagnostics)
• Policy packs (scheduling rules, placement constraints, approval gates)
• Hosted control-plane APIs (REST/gRPC for enterprise fleet management)

What It Does Not Replace

The control plane does not replace the FOSS core for:

• Deploying the base runner and cache platform
• Bootstrapping a cluster
• Using Attic or Bazel cache
• Running GitHub ARC on a self-hosted cluster

Adopters can run the full FOSS core without the managed control plane.

Current State

The existing runner-dashboard app (SvelteKit 5 + WebAuthn) provides:

• Runner listing and status
• Cache health monitoring
• GitOps configuration view

This is the seed for the control plane. The next evolution adds:

• Multi-tenant views (tenant sees only their pools and usage)
• Enrollment workflows (guided forge adapter setup)
• Observability dashboards (Prometheus metrics, Attic cache analytics)

Implementation Approach

Build on the existing dashboard rather than starting a separate service. The dashboard already has:

• WebAuthn auth
• Role-based access
• PostgreSQL backend
• REST API (12 endpoints via MCP server)

Add tenant awareness, enrollment flows, and observability views as dashboard features, not separate microservices.

Timeline

Not in scope for the current longevity sprint (Apr-Jun 2026). Target: design phase in Q3 2026, first tenant features in Q4 2026.