Every bowl.
Every twirl.
Rated.

1. Recommended stack: Firebase Hosting

You're already using Firebase for Auth and Firestore, so Firebase Hosting is the path of least resistance — same project, same CLI login, one dashboard, and the free "Spark" plan covers a small personal/friends-and-family app comfortably:

• 10 GB stored, 360 MB/day transferred — free, no credit card required
• Automatic HTTPS/SSL on both the default *.web.app URL and any custom domain you attach
• Global CDN, so it's fast for everyone rating pasta from wherever they are
• Deploys straight from this same folder — no build step, no framework, no bundler needed

Alternatives considered: Netlify and Vercel are both excellent free static hosts and would work fine too — but they'd mean juggling a second account and dashboard for zero real benefit here, since Firebase already hosts the data. Supabase is a Firebase alternative (auth + database), not a hosting add-on — switching to it would mean re-doing the auth/Firestore integration for no upside, so it's not worth it unless you want to leave Firebase entirely.

2. One-time setup

1. Install Node.js if you don't have it (nodejs.org — grab the LTS version).
2. Install the Firebase CLI:

   npm install -g firebase-tools

3. Log in with the Google account that owns the pastadiary-93913 Firebase project:

   firebase login

4. From inside this project's folder, initialize hosting:

   firebase init hosting

   When prompted:

   • "Use an existing project" → select pastadiary-93913
   • "What do you want to use as your public directory?" → type . (a single period — your index.html already lives at the project root, no separate build folder needed)
   • "Configure as a single-page app?" → No (it's one real index.html with anchor-linked sections, not client-side routing)
   • "Set up automatic builds and deploys with GitHub?" → No for now, unless you want that later
   • "File index.html already exists. Overwrite?" → No — never overwrite your real site

3. Deploy

firebase deploy --only hosting

That's it — the CLI prints a live URL like https://pastadiary-93913.web.app. Every time you make changes, run that same command again to push the update.

4. Add a custom domain (optional)

1. Buy a domain from a normal registrar — Namecheap, Cloudflare, or Porkbun are all reputable and typically run $10–$20/year for a standard .com — see the pick below.
2. In the Firebase Console → Hosting, click Add custom domain and enter it.
3. Firebase gives you a TXT record (to verify ownership) and then A records to point at Firebase's servers — add both in your registrar's DNS settings.
4. Wait for DNS to propagate and SSL to auto-provision — usually a few hours, occasionally up to 24–48h.

5. Suggested name & domain

⚠️ Heads up: Olive Garden's own pass checkout site is literally PastaPass.com, so any domain built around "Pasta Pass" — including PastaPassDiary.com — risks looking like it's officially affiliated. The picks below sidestep that on purpose.

Suggested app name to pair with it: Twirl Diary, with a tagline like "for Olive Garden's Never-Ending Pasta Pass" — that keeps the trademark-safe distance in the actual name/domain while still being clear about what it's for in the description.

Standard (non-premium) .coms like these typically run $10–$16/year at cost-friendly registrars — Porkbun and Cloudflare price near cost (~$9–11/yr), while Namecheap runs a bit higher, especially on renewal. This was checked by search, not a live registrar lookup, so confirm exact availability and price at checkout before buying.

6. Total ongoing cost

• Hosting: $0/mo on Firebase's free Spark plan for this traffic level
• Firestore + Auth: $0/mo — well within the free tier for a small group of pass holders
• Domain: the one real cost, ~$10–20/year, renewed annually at your registrar

If usage ever outgrows the free tier, Firebase asks you to upgrade to the pay-as-you-go "Blaze" plan before anything breaks — it won't silently start charging you.