Plans / Rebuild plan (AWS)
Rebuild plan: run Pitch 25 on your AWS account with the advarion framework
Recommendation Decision D1.
Three ways to do it
Target architecture (path A)
| Layer | What runs there |
|---|
Source of the patterns: D:\work\advarion\aws-architecture-reference.html, D:\work\advarion\foundry\docs\PLAYBOOK.md, SUPABASE-MAPPING.md, DECISIONS.md. Precedents in this account: ClassFirst (CDK, Aurora PG + Data API, Cognito, action routers, Jul 2026) and Lumenal (same shape on MySQL, Jul 2026).
What Foundry handles vs what is hand work for this project
| Item | In Pitch 25 | Handling |
|---|
Phases and tasks (path A)
Costs
| Line | Estimate | Note |
|---|
Prices are list prices for us-east-1 as of Aug 2026 and will be re-checked before provisioning. The biggest lever is Aurora auto-pause: with it the whole stack runs in the $12-20/mo range at club traffic; without it the 0.5 ACU floor alone is about $44/mo.
Path B in detail (if you choose the advarion admin platform instead)
| Area | How it would map |
|---|
Definition of done
- app.pitch25.com (or the interim domain) serves the same UI as the Lovable preview; api.pitch25.com answers only with a valid Cognito token.
- Every row from
lovable-export/datais in Aurora with the same ids; users exist in Cognito with their original app ids; roles and location scopes carry over. - The parity checklist (R7.2) passes for public, member, employee and admin flows, verified against the comps.
- Real email confirmation is on, CORS is tight, test passwords rotated, CloudWatch alarms exist, runbook delivered.
- Lovable unpublished and cancelled after the soak period; the export kept as the archive.