Skip to content

Phase (parked) — Managed Hosting + First Revenue

Status: Parked. Renamed from phase-3-hosted.md on 2026-04-22 to reflect the R1-R4 vision-draft reprioritization — managed hosting is no longer the Phase 3 target. See plan.md for the active phases.

Why this is parked

During the Phase 3+ vision discussion (see phase-3-vision-draft.md), the user chose self-hosted-first as the strategic direction (Q5), deferred the UI license decision to "Apache 2.0 target, private repo today, flip when ready" (Q1), and reclassified Stripe metering to Tier 4 (#M Round 2 reframe). That left the original Phase 3 scope — open-source the backbone, stand up managed hosting, Stripe, pilot onboarding — without most of its premises.

The active Phase 3 is now Phase 3 — Foundations, covering the Tier 1 architectural commitments and data-model primitives. Managed hosting remains a planned future phase: retained in this document, but not scheduled.

When to revive this

Unpark when any of the following hold:

  • A design-partner workload justifies the managed-hosting ops overhead.
  • The user decides to pursue revenue from hosting before other goals.
  • Apache 2.0 legal review for the backbone completes and open-sourcing the repo is imminent (managed hosting is a natural companion).

At revival, rescope against the then-current reality — pieces below may be stale or subsumed by later phases (e.g., the release pipeline + versioned images are now in Phase 6 §6.13; Prometheus instrumentation is in Phase 3 §3.9; usage metering observability is in Phase 6 §6.11).

Original scope (retained for reference)

Entry conditions

  • Phase 2 complete.
  • Auth + RBAC + multi-tenancy battle-tested against at least one design partner workload.
  • Apache 2.0 legal review for the backbone complete; no secrets in git history (verified via gitleaks or equivalent).
  • UI license chosen (see open cross-cutting points in plan.md — current target is Apache 2.0, currently private repo).
  • Pilot customer timing and pricing agreed.

Engine (climate-lama-engine)

Area Work
Documentation Public-facing docs site (subsumed by Phase 3 §3.6 MkDocs scaffold)
Data packages Companion package climate-lama-data-jrc — preprocessed JRC flood for all EU

Backbone (climate-lama)

Area Work
Open-source Make backbone repo public (license review complete, no secrets in history).
Managed hosting infra Kubernetes (DigitalOcean or Hetzner) + Helm charts + ArgoCD + cert-manager + external-dns.
Billing Stripe integration, usage tracking (reads from usage_events from Phase 6 §6.11).
Landing page Marketing site (delivered in Phase 7 §7.6 as an Astro split).
Academic tier Verified .edu / .ac domains get free managed tier.
Pilot onboarding GIZ, World Bank, Greek agency — onboarding script + support runbook.
Carry-over #16 — scope centroid assignment to hazard dataset bbox (lands here when multi-region goes live).

UI (climate-lama-ui)

Area Work
License decision Target Apache 2.0 (R3 resolution) — legal confirmation before this phase.
Landing page integration Sign-up flow from landing page → managed instance.
OIDC Reuse the Phase 2 Wave 2 OIDC scaffolding for SSO pilot customers.
Separate domain Deploy UI to its own CDN/domain separate from API.

Retrospective backlog (filed 2026-04-18)

Issues filed after a cross-reference audit of Phase 0 against the actual closed work. Originally targeted here; revive alongside the managed-hosting work.

Issue Origin Title
#102 Phase 0 docs(adr): dev secrets and config management strategy — pulled forward to Phase 6 §6.14 (2026-04-26); resolved by ADR-034 (2026-04-28)
#103 Phase 0 docs: integration-test troubleshooting runbook for scripts/demo.py

Out of scope (for this parked phase)