Amazon Web Services vs Render
Of the 3,549 makers' products we know the hosting of, 460 chose Amazon Web Services (13%) and 137 Render (4%); 15 use both. Among the 860 launched in 2026, Amazon Web Services is in 9% and Render in 3%, against 12% and 5% of those launched in 2024 or earlier. They're different kinds of tool, hyperscaler cloud and paaS, so the counts don't measure the same choice. At our calculator's default usage, Amazon Web Services comes to $17 a month and Render $39, at list prices. On GitHub, 8 public pull requests moved projects from Amazon Web Services to Render, and 19 the other way.
Two sides of the hosting decision: hyperscaler cloud and paaS. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.
Which fits you
- The widest catalog of building blocks — Lambda, containers, managed databases, queues — to assemble your own infrastructure.
Use it whenYou need a specific AWS service, enterprise customers ask for it, or you have credits to spend.
Trade-offYou wire up networking, permissions and deploys yourself; billing is per service and hard to predict.
- You have a long-running server, a background worker and a database to deploy together
Use it whenYou want a managed server, cron jobs and Postgres with a flat per-instance price.
Trade-offFree instances sleep when idle and wake slowly; paid instances are billed whether busy or not.
At a glance
| Used by | 460 makers' products · 18 open-source projects | 137 makers' products |
|---|---|---|
| Cost at default usagerequests 5 million requests, data transfer out 100 GB, serverless function compute 100 GB-hours | $17/mo Pay as you go (Lambda + EC2 t4g.small) | $39/mo Hobby |
| Moved to it on GitHubpull requests since Oct 2024 | 19 from Render | 8 from Amazon Web Services |
| Downloads | 4.2M/wk−40% vs npm | |
| Pricing | Pay-as-you-go per service; new accounts get up to $200 in Free Tier credits over 6 months. · paid from Pay as you go | Free tier for static sites and small services; paid per instance. · paid from $7/mo per instance |
| Free tier | Yes | Yes |
| Open source | No | No |
| Incidents, 90 daysfrom its status page | no public status feed | 13 (6 major) |
Which makers on your framework pick
Makers' products built with each framework that chose either one, for hosting.
| Framework | |||
|---|---|---|---|
| 161 | 34 | All 1312 Next.js products' picks → | |
| 45 | 12 | All 147 React products' picks → | |
| 10 | 2 | All 112 Astro products' picks → | |
| 9 | 0 | All 31 Laravel products' picks → | |
| 5 | 2 | All 15 FastAPI products' picks → | |
| 4 | 0 | All 17 Django products' picks → | |
| 1 | 2 | All 14 Nuxt products' picks → |
New launches vs older products
A tool that came first has products from every year since, so its total runs ahead. Here is what products launched each year chose, as a share of those that made the hosting decision (by the year they launched on Product Hunt).
| Launched | Products | ||
|---|---|---|---|
| 2022 or earlier | 19% 22 | 5% 6 | 118 |
| 2023 | 16% 14 | 1% 1 | 89 |
| 2024 | 10% 59 | 6% 33 | 582 |
| 2025 | 14% 89 | 4% 28 | 629 |
| 2026 | 9% 80 | 3% 28 | 860 |
Cost as you grow
At 100k requests Amazon Web Services costs less ($16 vs $25); from about 500M requests Render does ($1,524 vs $1,600). They're different kinds of tool — hyperscaler cloud and paaS — so the prices don't buy the same thing.
The numbers, plan by plan
| Requests per month | Amazon Web Services | Render |
|---|---|---|
| 0.1 | $16 Pay as you go (Lambda + EC2 t4g.small) | $25 Hobby |
| 0.5 | $16 Pay as you go (Lambda + EC2 t4g.small) | $26 Hobby |
| 1 | $16 Pay as you go (Lambda + EC2 t4g.small) | $27 Hobby |
| 5 | $17 Pay as you go (Lambda + EC2 t4g.small) | $39 Hobby |
| 10 | $32 Pay as you go (Lambda + EC2 t4g.small) | $54 Hobby |
| 50 | $160 Pay as you go (Lambda + EC2 t4g.small) | $174 Hobby |
| 100 | $320 Pay as you go (Lambda + EC2 t4g.small) | $324 Hobby |
| 500 | $1,600 Pay as you go (Lambda + EC2 t4g.small) | $1,524 Hobby |
From each vendor's pricing page: Amazon Web Services, Render.
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "Amazon Web Services to Render" or the reverse — real code changes, by developers in general rather than makers only.
- [enterprise-4.21][OCPBUGS-86765]: Add render-sensitive flag to HCP on AWS procedureopenshift/openshift-docs · 2026-08-19
- [enterprise-4.20][OCPBUGS-86765]: Add render-sensitive flag to HCP on AWS procedureopenshift/openshift-docs · 2026-08-19
- [enterprise-4.19][OCPBUGS-86765]: Add render-sensitive flag to HCP on AWS procedureopenshift/openshift-docs · 2026-08-19
- [enterprise-4.18][OCPBUGS-86765]: Add render-sensitive flag to HCP on AWS procedureopenshift/openshift-docs · 2026-08-19
- [enterprise-5.0] [OCPBUGS-86765]: Add render-sensitive flag to HCP on AWS procedureopenshift/openshift-docs · 2026-08-19
- [enterprise-4.22] [OCPBUGS-86765]: Add render-sensitive flag to HCP on AWS procedureopenshift/openshift-docs · 2026-08-19
- [OCPBUGS-86765]: Add render-sensitive flag to HCP on AWS procedureopenshift/openshift-docs · 2026-08-19
- tf: Add Render access to AWS Redis via PrivateLinkpolarsource/polar · 2026-08-11
- Move the API from Render to AWS LightsailHrishi75/CropBid · 2026-07-29
- feat: migrate deployment from Render to AWS serverlessglaboryp/fontray · 2026-07-20
- Move hosting from AWS to Render + Cloudflare R2zupa-na-plantach/zupa · 2026-09-29
- feat: migrate application configuration from AWS to Render, update environment variables and remove AWS dependencies (#150)vertsan/sbku-app · 2026-07-19
- feat: migrate application configuration from AWS to Render, update environment variables and remove AWS dependenciesvertsan/sbku-app · 2026-07-18
- replace config from aws to renderryannguyen1105/Simplepayment · 2026-04-22
- fix(env): update dead AWS IP to active Render backend URLmhdmirzan/RecruBotX · 2026-03-08
- fukk aws ec2, back to renderreijjo/bet · 2025-09-29
- from aws to rendermjkats/mercado-lance · 2025-05-26
- fix(common): migrate aws to renderminhoyunlife/my-projects · 2025-05-12
What makers say
Makers on using it for hosting, from Product Hunt and Starter Story interviews, each linked to the source. Products with a page of their own and fuller notes first.
We are so excited to integrate with AWS Lambda. Look for our upcoming co-authored blog about how Fleak and AWS Lambda bring goodness to data teams and help them win their time back!
AWS provides the global infrastructure we need to deliver low-latency voice translation to users worldwide. Their reliable services ensure our calls connect seamlessly across regions.
…m - for customer support, knowledge base, and live chat support Webflow - for our website AWS - for our cloud hosting needs Figma - for all our design collaboration Microsoft Clarity…
Render is stable, easy to use, and get started with - ideally for a startup. We considered Railway but we had some issues with it and didn't have the time to work through them.
Render made hosting and deployment ridiculously simple. It’s honestly so smooth that we dont use Azure and AWS, even though we still have a bunch of credits sitting there.
I love using Plausible for analytics, LogSnag for event tracking, NewRelic for application monitoring, MailGun for emails, Render for hosting, Stripe for billing.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
Who uses each
What makers pair each with
Neither quite right?
See the whole hosting decision →Questions
Amazon Web Services or Render: which do makers choose?
Of the 3,549 makers' products we know the hosting of, 460 chose Amazon Web Services (13%) and 137 Render (4%); 15 use both. Among the 860 launched in 2026, Amazon Web Services is in 9% and Render in 3%, against 12% and 5% of those launched in 2024 or earlier. They're different kinds of tool, hyperscaler cloud and paaS, so the counts don't measure the same choice. At our calculator's default usage, Amazon Web Services comes to $17 a month and Render $39, at list prices. On GitHub, 8 public pull requests moved projects from Amazon Web Services to Render, and 19 the other way. Choose Amazon Web Services if the widest catalog of building blocks — Lambda, containers, managed databases, queues — to assemble your own infrastructure; choose Render if you have a long-running server, a background worker and a database to deploy together.
Can you use Amazon Web Services and Render together?
15 makers' products we track use both, often one replacing the other or each for a different part of the product: AgentR, ClarityUX, Dopamine.chat, Gan.AI, TensorPool and others.
When should I pick Render over Amazon Web Services?
Pick Render if: You have a long-running server, a background worker and a database to deploy together.
Which is cheaper, Amazon Web Services or Render?
At requests 5 million requests, data transfer out 100 GB, serverless function compute 100 GB-hours: Amazon Web Services $17/mo (Pay as you go (Lambda + EC2 t4g.small)), Render $39/mo (Hobby), at list prices.
How do Amazon Web Services and Render compare in cost as you grow?
At 100k requests Amazon Web Services costs less ($16 vs $25); from about 500M requests Render does ($1,524 vs $1,600). Cheapest usable plan at each scale, at list prices.
Are people switching from Amazon Web Services to Render?
Public GitHub pull requests since 2024-10-02: 8 from Amazon Web Services to Render, 19 from Render to Amazon Web Services.

