KBAISE/ for lovable
Head to head

Stop guessing which one. Put them side by side.

Up to 4 tools, same rows for each: what it is, what it really costs, the trap, and how to wire it up. The URL carries your picks — send it to anyone.

Firebase App HostingGitHub PagesAWS Amplify Hosting
Quick read
  • Free with no card: GitHub Pages.
FieldFirebase App Hostingfirebase.google.comGitHub Pagespages.github.comAWS Amplify Hostingaws.amazon.com
What it isGoogle's Cloud Run-backed hosting for Next.js and Angular, with GitHub integration, server-side rendering, rollouts and native hookups to Firestore, Auth and App Check. Classic Firebase Hosting remains a free static CDN with 10 GB of storage and 360 MB of daily transfer.Serves a static site directly from a repository branch or a GitHub Actions build, with free HTTPS on custom domains. Limits are soft rather than metered: a 1 GB published site, 100 GB of bandwidth a month and 10 builds an hour. No server-side code at all.AWS's managed CI/CD plus CloudFront hosting for React, Vite and Next.js, with SSR on Lambda and first-party wiring into Cognito, AppSync, DynamoDB and S3. Pricing is pure pay-per-unit — $0.15 per GB served, $0.01 per build minute, $0.30 per million SSR requests.
CategoryHosting, deploy & edgeHosting, deploy & edgeHosting, deploy & edge
Cost tiermixedfreemixed
PricingRequires Blaze pay-as-you-go; not on the free Spark plan. 5 GB storage free then $0.10/GB; 10 GiB/mo uncached egress free then $0.20/GiB; cached egress $0.15/GiB. Classic Firebase Hosting stays free at 10 GB storage and 360 MB/day transfer.Free on public repos with GitHub Free; private repos require Pro ($4/mo), Team or Enterprise. Soft limits: 1 GB published site, 100 GB bandwidth per month, 10 builds per hour (waived when using a custom Actions workflow).Free tier: 1,000 build minutes, 5 GB stored, 15 GB served, 500k SSR requests, 100 GB-hours SSR compute per month. Then $0.01 per standard build minute, $0.023/GB stored, $0.15/GB served, $0.30 per 1M SSR requests, $0.20 per SSR GB-hour.
Why builders pick itIf Firestore and Firebase Auth are already your backend, App Hosting deletes the glue code — SSR, secrets and the client SDK arrive pre-wired. Classic Hosting alone is still a fine free CDN for a Vite build.The zero-thought way to publish a Vite build, docs site or portfolio — one Actions workflow and it is live forever with no billing relationship to worry about and no credit card on file.If the rest of your stack already lives in AWS, Amplify keeps auth, data and hosting inside one IAM boundary with per-branch environments. The free tier covers a low-traffic first year comfortably.
Watch out forBlaze has no spend cap — budget alerts notify but never stop anything, which is how Firebase earned its reputation for five-figure overnight bills. Wire the budget Pub/Sub topic to a function that calls the billing API and disables billing, and enable App Check everywhere.GitHub's terms forbid running a business, e-commerce or SaaS on Pages. Billing risk is genuinely zero, but so are redirects, SSR, server env vars and access control. Exceeding 100 GB earns a polite email, not an invoice.AWS has no hard spend cap — Budgets only send alerts. Amplify tutorial defaults have produced four-figure bills, including a documented $1,100 charge from an undisclosed OpenSearch instance (refunded). Create an AWS Budget with an SNS or Lambda action that disables the offending resources.
How to wire it upnpm i -g firebase-tools && firebase init hosting && firebase deploynpx gh-pages -d distnpm create amplify@latest && npx ampx sandbox
Editor's pickNoNoNo
Which one did you ship?

The grid says what these tools are. This says what builders did about it — one decision per person, changeable whenever you change your mind.

0/280Sign in to add yours.
Or try
Hand this to your Lovable agent
# Tool comparison — Firebase App Hosting vs GitHub Pages vs AWS Amplify Hosting

Source: Kbaise, a directory of tools that work with Lovable projects.
Pick one and tell me why before writing any integration code.

## Firebase App Hosting (firebase-app-hosting)
- URL: https://firebase.google.com/products/app-hosting
- Category: Hosting, deploy & edge
- Cost: mixed — Requires Blaze pay-as-you-go; not on the free Spark plan. 5 GB storage free then $0.10/GB; 10 GiB/mo uncached egress free then $0.20/GiB; cached egress $0.15/GiB. Classic Firebase Hosting stays free at 10 GB storage and 360 MB/day transfer.
- What it is: Google's Cloud Run-backed hosting for Next.js and Angular, with GitHub integration, server-side rendering, rollouts and native hookups to Firestore, Auth and App Check. Classic Firebase Hosting remains a free static CDN with 10 GB of storage and 360 MB of daily transfer.
- Why builders pick it: If Firestore and Firebase Auth are already your backend, App Hosting deletes the glue code — SSR, secrets and the client SDK arrive pre-wired. Classic Hosting alone is still a fine free CDN for a Vite build.
- Trap: Blaze has no spend cap — budget alerts notify but never stop anything, which is how Firebase earned its reputation for five-figure overnight bills. Wire the budget Pub/Sub topic to a function that calls the billing API and disables billing, and enable App Check everywhere.
- Wiring: npm i -g firebase-tools && firebase init hosting && firebase deploy
- Full dossier: /api/public/tools/firebase-app-hosting

## GitHub Pages (github-pages)
- URL: https://pages.github.com
- Category: Hosting, deploy & edge
- Cost: free — Free on public repos with GitHub Free; private repos require Pro ($4/mo), Team or Enterprise. Soft limits: 1 GB published site, 100 GB bandwidth per month, 10 builds per hour (waived when using a custom Actions workflow).
- What it is: Serves a static site directly from a repository branch or a GitHub Actions build, with free HTTPS on custom domains. Limits are soft rather than metered: a 1 GB published site, 100 GB of bandwidth a month and 10 builds an hour. No server-side code at all.
- Why builders pick it: The zero-thought way to publish a Vite build, docs site or portfolio — one Actions workflow and it is live forever with no billing relationship to worry about and no credit card on file.
- Trap: GitHub's terms forbid running a business, e-commerce or SaaS on Pages. Billing risk is genuinely zero, but so are redirects, SSR, server env vars and access control. Exceeding 100 GB earns a polite email, not an invoice.
- Wiring: npx gh-pages -d dist
- Full dossier: /api/public/tools/github-pages

## AWS Amplify Hosting (aws-amplify-hosting)
- URL: https://aws.amazon.com/amplify/
- Category: Hosting, deploy & edge
- Cost: mixed — Free tier: 1,000 build minutes, 5 GB stored, 15 GB served, 500k SSR requests, 100 GB-hours SSR compute per month. Then $0.01 per standard build minute, $0.023/GB stored, $0.15/GB served, $0.30 per 1M SSR requests, $0.20 per SSR GB-hour.
- What it is: AWS's managed CI/CD plus CloudFront hosting for React, Vite and Next.js, with SSR on Lambda and first-party wiring into Cognito, AppSync, DynamoDB and S3. Pricing is pure pay-per-unit — $0.15 per GB served, $0.01 per build minute, $0.30 per million SSR requests.
- Why builders pick it: If the rest of your stack already lives in AWS, Amplify keeps auth, data and hosting inside one IAM boundary with per-branch environments. The free tier covers a low-traffic first year comfortably.
- Trap: AWS has no hard spend cap — Budgets only send alerts. Amplify tutorial defaults have produced four-figure bills, including a documented $1,100 charge from an undisclosed OpenSearch instance (refunded). Create an AWS Budget with an SNS or Lambda action that disables the offending resources.
- Wiring: npm create amplify@latest && npx ampx sandbox
- Full dossier: /api/public/tools/aws-amplify-hosting

## Quick read

- Free with no card: GitHub Pages.

## Rules
1. Prefer the free tier when no budget was stated, and say what the ceiling is.
2. Read the full dossier before integrating.
3. Fetch /api/public/models before writing any AI model ID.

Agents can fetch the same thing: GET /api/public/compare?slugs=firebase-app-hosting,github-pages,aws-amplify-hosting