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.
Fly.ioGitHub PagesAWS Amplify Hosting
Quick read
- Free with no card: GitHub Pages.
| Field | Fly.iofly.io | GitHub Pagespages.github.com | AWS Amplify Hostingaws.amazon.com |
|---|---|---|---|
| What it is | Runs Firecracker microVMs of your Docker image across 35+ regions with anycast routing, private WireGuard networking and Machines that auto-stop and auto-start per request. Billing is per second on provisioned resources, and new organizations no longer receive the legacy free allowances. | 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. |
| Category | Hosting, deploy & edge | Hosting, deploy & edge | Hosting, deploy & edge |
| Cost tier | paid | free | mixed |
| Pricing | Pay-as-you-go with no free allowance for new orgs. shared-cpu-1x 256 MB about $2.43/mo ($0.0034/hr), volumes $0.15/GB-month, outbound $0.02/GB in North America and Europe, $0.04/GB most other regions, $0.12/GB India. Support plans $29/mo and $199/mo. | 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 it | Puts your app physically near users worldwide without touching Kubernetes, and idle machines scale to zero so a side project runs for a couple of dollars a month. Postgres and Redis live in the same private network. | 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 for | Volumes and stopped-machine rootfs keep billing when the app is off — orphaned volumes are the classic surprise line item. India egress is $0.12/GB, 6x North America. There is no hard spend cap; watch the dashboard and delete unused apps properly. | 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 up | fly launch && fly deploy | npx gh-pages -d dist | npm create amplify@latest && npx ampx sandbox |
| 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 — Fly.io 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. ## Fly.io (fly-io) - URL: https://fly.io - Category: Hosting, deploy & edge - Cost: paid — Pay-as-you-go with no free allowance for new orgs. shared-cpu-1x 256 MB about $2.43/mo ($0.0034/hr), volumes $0.15/GB-month, outbound $0.02/GB in North America and Europe, $0.04/GB most other regions, $0.12/GB India. Support plans $29/mo and $199/mo. - What it is: Runs Firecracker microVMs of your Docker image across 35+ regions with anycast routing, private WireGuard networking and Machines that auto-stop and auto-start per request. Billing is per second on provisioned resources, and new organizations no longer receive the legacy free allowances. - Why builders pick it: Puts your app physically near users worldwide without touching Kubernetes, and idle machines scale to zero so a side project runs for a couple of dollars a month. Postgres and Redis live in the same private network. - Trap: Volumes and stopped-machine rootfs keep billing when the app is off — orphaned volumes are the classic surprise line item. India egress is $0.12/GB, 6x North America. There is no hard spend cap; watch the dashboard and delete unused apps properly. - Wiring: fly launch && fly deploy - Full dossier: /api/public/tools/fly-io ## 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=fly-io,github-pages,aws-amplify-hosting