Skip to main content

Customer Portal — Migration Plan

Status: populated Owner: Product Engineering (Frontend) Last updated: 2026-04-18

1. Overview​

The customer-portal is a new service with no legacy predecessor. This document covers the phased rollout plan from initial deployment to full production availability.

2. Phases​

Phase 1 — Internal Alpha (Sprint 1–2)​

  • Deploy to portal-alpha.ghasi.io (internal only).
  • Auth flow + API key management pages complete.
  • Connects to staging Kong + staging backend services.
  • Tested by platform team members with real customer accounts.

Phase 2 — Closed Beta (Sprint 3–4)​

  • Invite 5–10 early-adopter customers.
  • Message log, test SMS sender, and webhook pages added.
  • Sentry error tracking live.
  • Performance baseline measured (LCP, TTFB).

Phase 3 — General Availability​

  • Billing page complete.
  • Cloudflare CDN static asset serving configured.
  • Autoscaling HPA configured.
  • All E2E tests green.
  • Documentation portal updated with customer-facing guides.

3. Rollback Plan​

  • Blue/green deployment via Kubernetes: new version deployed alongside old version; traffic switched via ingress annotation.
  • If critical bug detected post-rollout: repoint ingress to previous deployment within 5 minutes.
  • Cookie format changes require a version bump in the session schema; old cookies auto-expire on first request to new version (force re-login).

4. Feature Flags​

FlagDefaultPurpose
billing_page_enabledfalse in alphaGate billing page until billing-service is production-ready
webhook_events_v2falseEnable extended event types when webhook-dispatcher v2 is deployed

Feature flags managed via environment variables in the Kubernetes deployment manifest.