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.
AWS Amplify HostingGitHub PagesBunny.net
Quick read
- Free with no card: GitHub Pages.
| Field | AWS Amplify Hostingaws.amazon.com | GitHub Pagespages.github.com | Bunny.netbunny.net |
|---|---|---|---|
| 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. | 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. | A pay-per-gigabyte CDN across 119 points of presence, with edge storage, image optimization, video streaming, Edge Scripting and Magic Containers for serverless compute in 41 regions. There are no plans or seats — you top up a balance and pay per unit above a $1 monthly minimum. |
| Category | Hosting, deploy & edge | Hosting, deploy & edge | Hosting, deploy & edge |
| Cost tier | mixed | free | paid |
| Pricing | 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. | 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). | $1/mo minimum, prepaid. CDN bandwidth $0.01/GB Europe and North America, $0.03/GB Asia and Oceania, $0.045/GB South America, $0.06/GB Middle East and Africa; Volume network $0.005/GB. Magic Containers $0.02 per core-hour and $0.005 per GB RAM-hour, storage $0.10/GB-mo. |
| 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. | 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. | The bandwidth escape hatch: park a Vite build or media on Bunny at $0.01/GB and the terabyte that costs about $150 on Vercel costs $10. Setup is one pull zone and a CNAME. |
| Watch out for | 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. | 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. | Prepaid balance means an attack drains credit instead of generating an invoice — safer, but the site goes dark at zero, so keep auto top-up modest and alerts on. It is not a Git-deploy platform: you still need somewhere to build, and Edge Scripting is a far smaller ecosystem than Workers. |
| How to wire it up | npm create amplify@latest && npx ampx sandbox | npx gh-pages -d dist | Create a Pull Zone, point a CNAME at it, upload the build to Edge Storage |
| Editor's pick | No | No | No |
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 — AWS Amplify Hosting vs GitHub Pages vs Bunny.net Source: Kbaise, a directory of tools that work with Lovable projects. Pick one and tell me why before writing any integration code. ## 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 ## 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 ## Bunny.net (bunny-net) - URL: https://bunny.net - Category: Hosting, deploy & edge - Cost: paid — $1/mo minimum, prepaid. CDN bandwidth $0.01/GB Europe and North America, $0.03/GB Asia and Oceania, $0.045/GB South America, $0.06/GB Middle East and Africa; Volume network $0.005/GB. Magic Containers $0.02 per core-hour and $0.005 per GB RAM-hour, storage $0.10/GB-mo. - What it is: A pay-per-gigabyte CDN across 119 points of presence, with edge storage, image optimization, video streaming, Edge Scripting and Magic Containers for serverless compute in 41 regions. There are no plans or seats — you top up a balance and pay per unit above a $1 monthly minimum. - Why builders pick it: The bandwidth escape hatch: park a Vite build or media on Bunny at $0.01/GB and the terabyte that costs about $150 on Vercel costs $10. Setup is one pull zone and a CNAME. - Trap: Prepaid balance means an attack drains credit instead of generating an invoice — safer, but the site goes dark at zero, so keep auto top-up modest and alerts on. It is not a Git-deploy platform: you still need somewhere to build, and Edge Scripting is a far smaller ecosystem than Workers. - Wiring: Create a Pull Zone, point a CNAME at it, upload the build to Edge Storage - Full dossier: /api/public/tools/bunny-net ## 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=aws-amplify-hosting,github-pages,bunny-net