Pitch 25: move the Lovable site to AWS on the advarion framework
Pitch 25 is a Houston soccer sports bar (indoor pitch, classes with captains, dining, events, memberships, loyalty points, staff scheduling). The product was built in Lovable between January and May 2026 on Lovable Cloud (managed Supabase). This site is the working reference for moving it to your own AWS account: what exists, how it gets downloaded, how it gets rebuilt, what is decided, and where things stand.
What now (your next three actions)
- Read Decisions & approvals and answer D1-D10 (a plain "approved, go" accepts every recommendation).
- Authorize the code export: allow the codebase ZIP download and connect GitHub in Lovable (Settings > Git) - tasks D1.1 / D1.2.
- Sign into the Lovable preview once in the Chrome tab Claude is using, so the admin / member / employee screens can be captured (D9).
How the work is layered
1. Inventory (done)
Routes, screens, 14 admin modules, 37 tables, 24 functions, 126 policies, assets, integrations and the full build history - all read from Lovable without changing anything. See Site inventory and Build history.
2. Download plan
Code (ZIP + GitHub mirror), schema (migrations + live snapshot), data (every table as JSON with counts and hashes), users, storage, brand assets, screen captures and the chat history, all under D:\work\pitch25\lovable-export. See Download plan.
3. Rebuild plan
Keep the approved Lovable UI, move the backend to AWS with the Foundry pipeline from D:\work\advarion\foundry: Aurora PostgreSQL Serverless v2, Cognito, action-router Lambdas, S3 + CloudFront, Route53. Costs and the alternative (re-platform onto the advarion admin platform) are spelled out. See Rebuild plan.
4. Tracking
Tasks lists every step with owner and status, Progress shows the phase bars, Decisions holds the open questions, Activity log records what happened when.