Skip to content

MVP Scope at a Glance

What ships at launch versus what is deferred. Detailed tiering lives in §39 (MVP-blocking §39.1, pre-launch-blocking §39.2, post-MVP/seed §39.3) and §15.10.

In MVP

Area What
Login SSO via GitHub + Google (dashboard auth only)
Deploy GitHub App + webhooks; Railpack (primary) / Dockerfile (fallback) via Depot; zero-downtime rolling deploys + one-click rollback
Service types Web, worker, cron
Config Customer health checks (liveness/readiness/startup)
Managed data Postgres + Valkey, per environment
Object storage Tigris S3-compatible buckets, per environment
Env/secrets Var Groups (attachable, env-scoped, per-Var-Group K8s Secret)
Permissions Two-tier RBAC (workspace + project roles) + environment protection
Observability Logs (ClickHouse) with live streaming; 7 customer metrics (latency, RPS, throughput, error rate, CPU, memory, network); platform self-monitoring (Grafana Cloud)
Autoscaling HPA on CPU/memory (metrics-server); cluster autoscaling
Domains Wildcard *.starform.app
Billing Per-minute pod snapshots, plan credits, Stripe

Deferred (post-MVP / seed — §39.3 unless noted):

Area Status
Customer auth primitive (JWKS, gateway SecurityPolicy, claim-to-header) Seed-stage — distinct from MVP SSO login
Email primitive Seed-stage
Queue primitive Seed-stage
CLI tool Post-MVP
Preview environments Decision pending (launch vs seed)
Scale-to-zero Post-MVP
Custom domains + cert-manager Post-MVP
Autoscaling on RPS/latency Deferred (needs prometheus-adapter; §39.1 #9)
Per-tier metric retention Deferred (MVP = global 90d; FR-051)
Distributed tracing Out of MVP scope
Audit logs, API tokens, status page, GDPR, rate limiting Pre-launch-blocking (§39.2)
Custom roles, SSO/SAML (Enterprise), per-user env overrides Post-MVP (§15.10)
BYOC (bring-your-own-cloud) Out of scope — not offered (§37)

Preview environments — Decision pending

Whether preview/ephemeral environments ship at launch or seed-stage is still open. They are identified by the is_ephemeral flag, not name-matching. See §39.

Pre-launch-blocking (§39.2)

Audit logs, API tokens, status page, GDPR, and rate limiting are pre-launch-blocking — not in the initial MVP cut, but required before public launch.

Out of scope — not offered (§37)

BYOC (bring-your-own-cloud) is explicitly not offered. See §37.


Cross-references

Full open-work tiering → §39 · RBAC build-vs-defer → §15.10 · the normative "done" definition → Functional Requirements / Success Criteria. Canonical map: Canonical Sources.