Amazon Web Services vs DigitalOcean
Of the 3,549 makers' products we know the hosting of, 460 chose Amazon Web Services (13%) and 150 DigitalOcean (4%); 9 use both. Among the 860 launched in 2026, Amazon Web Services is in 9% and DigitalOcean in 2%, 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. DigitalOcean is the more common pick among Django products (8 vs 4).
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.
- App Platform deploys from git next to DigitalOcean's managed databases, storage and droplets.
Use it whenYou already use DigitalOcean servers or databases and want managed deploys in the same account.
Trade-offFewer built-in extras than Vercel or Railway, and instances are billed per size, not per request.
At a glance
| Used by | 460 makers' products · 18 open-source projects | 150 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) | — |
| 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 | Pay-as-you-go and fixed monthly plans; Droplets from $4/month; App Platform hosts up to 3 static sites free; promotional credits for new users. · paid from $4/mo (Droplets) |
| Free tier | Yes | Yes |
| Open source | No | No |
| Incidents, 90 daysfrom its status page | no public status feed | 16 (2 major) |
Which makers on your framework pick
Makers' products built with each framework that chose either one, for hosting.
| Framework | |||
|---|---|---|---|
| 161 | 25 | All 1312 Next.js products' picks → | |
| 45 | 17 | All 147 React products' picks → | |
| 9 | 9 | All 31 Laravel products' picks → | |
| 10 | 3 | All 112 Astro products' picks → | |
| 4 | 8 | All 17 Django products' picks → | |
| 5 | 1 | All 15 FastAPI 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 | 4% 4 | 89 |
| 2024 | 10% 59 | 5% 29 | 582 |
| 2025 | 14% 89 | 4% 26 | 629 |
| 2026 | 9% 80 | 2% 18 | 860 |
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…
…es our email and chat help desk Asana - project management for issues, bugs, and features Digital Ocean - where all 57 of our servers are housed, they were recently purchased by Amazon.…
We rely on DigitalOcean to host all our backend infrastructure. Its a simple interface, so we don't waste time figuring out a cluttered UI, and rather focus on developing.
DigitalOcean keeps our infrastructure simple and cost-effective. The UI is clean, docs are developer-friendly, and we were able to go live without headaches.
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 DigitalOcean: which do makers choose?
Of the 3,549 makers' products we know the hosting of, 460 chose Amazon Web Services (13%) and 150 DigitalOcean (4%); 9 use both. Among the 860 launched in 2026, Amazon Web Services is in 9% and DigitalOcean in 2%, 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. DigitalOcean is the more common pick among Django products (8 vs 4). Choose Amazon Web Services if the widest catalog of building blocks — Lambda, containers, managed databases, queues — to assemble your own infrastructure; choose DigitalOcean if app Platform deploys from git next to DigitalOcean's managed databases, storage and droplets.
Can you use Amazon Web Services and DigitalOcean together?
9 makers' products we track use both, often one replacing the other or each for a different part of the product: Vamah.ai, Maildroppa, Thankbox, Offorte, Crisp and others.

