Skip to content

Epic: Nat SaaS production-readiness #18

Description

@ianpatrickhines

Context

Nat ships in two forms: a CLI (works today) and the SaaS product — Chrome extension + AWS backend + Stripe billing + marketing site. The SaaS was built as a complete MVP (27 Ralph stories) and then half-migrated from per-user to per-nation billing. The migration updated most of the backend but left the tests, the extension, and one handler on the old model — so the pieces no longer agree, CI is red, and the part that actually enforces payment is built but never switched on.

This epic tracks the arc from that half-finished state to production / public launch. Assessment basis: three parallel code audits (backend, extension, site/tests/CI) on 2026-06-20. Overall ~65% ready.

Gating decision: RESOLVED 2026-06-20 — keeping per-nation pricing (Ian). Rationale: it's how NationBuilder customers think about their bills, and it's simpler (no seat management). Per-user revert is off the table; do not re-raise.

Phases

Phase 1 — Finish the migration (make it work end-to-end)

Phase 2 — Turn on the money + lock the doors

Phase 3 — Wire up the real world

Phase 4 — Chrome Web Store

Phase 5 — Operate with confidence

Acceptance Criteria

  • Per-nation vs per-user decision recorded — per-nation, 2026-06-20
  • Phases 1–2 complete: CI green, extension↔backend agree, paid-only access enforced, security gaps closed
  • Phase 3 complete: real domain + secrets + Stripe prices; end-to-end smoke passes in target env
  • Phase 4 complete: extension live (or submitted) on the Chrome Web Store
  • Phase 5 complete: monitoring/alerting in place

Metadata

Metadata

Assignees

No one assigned

    Labels

    epicTracks a multi-issue arc

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions