Amazon Web Services vs Firebase
Of the 4,047 makers' products we know the AI tool behind, 460 chose Amazon Web Services (11%) and 187 Firebase (5%); 11 use both. Among the 1,010 launched in 2026, Amazon Web Services is in 8% and Firebase in 4%, against 10% and 7% of those launched in 2024 or earlier. They're different kinds of tool, hyperscaler cloud and backend platform, so the counts don't measure the same choice.
Two ways to build a product with AI: Amazon Web Services, a hyperscaler cloud, and Firebase, a backend platform. What makers built with each, what they chose for the rest of the stack, and what they 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.
- Mobile apps that need offline sync and client-side SDKs.
Use it whenYou're shipping a mobile app first and want the client to read and write data directly, including while offline.
Trade-offA document store without SQL joins; hard to migrate off.
At a glance
| Used by | 460 makers' products · 18 open-source projects | 187 makers' products · 78 open-source projects |
|---|---|---|
| Downloads | 4.2M/wk−40% vs npm | 9.5M/wk−22% 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 Spark plan; pay-as-you-go Blaze plan. · paid from Pay as you go (Blaze) |
| Free tier | Yes | Yes |
| Open source | No | No |
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 whose AI building tool we know (by the year they launched on Product Hunt).
| Launched | Products | ||
|---|---|---|---|
| 2022 or earlier | 17% 22 | 4% 5 | 131 |
| 2023 | 13% 14 | 7% 8 | 109 |
| 2024 | 8% 59 | 7% 51 | 700 |
| 2025 | 12% 89 | 5% 41 | 760 |
| 2026 | 8% 80 | 4% 37 | 1,010 |
What makers say
Makers on building with it, 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…
Key role in helping us deliver results in real time, because the analysis streams onto the page as it completes instead of making founders wait for a finished report.
Firebase powers the backbone of uList, ensuring robust real-time data handling, secure authentication, and scalable backend infrastructure. It's the unsung hero making our app fast and reliable.
Firebase was chosen because its Realtime Database and seamless integration allow the application to instantly sync AI tutoring feedback directly to a user's device.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
- Auth, Firestore, Cloud Functions and hosting wire up in minutes, the fastest path to a working backend for a solo developer. PHHN
- Real-time sync across devices, with offline caching that remains stronger than most all-in-one rivals. PHHN
- The free tier and serverless pricing keep costs near zero when starting out. PHPH 2
- A server-side change made the iOS SDK crash apps everywhere, exposing the risk of a closed SDK you cannot control. HNHN 2HN 3HN 4
- It feels neglected and bolted onto Google Cloud, and it cannot be self-hosted, so leaving means a full migration. HNHN 2HN 3
- Client-accessible databases guarded only by optional security rules are a common cause of data leaks. HNHN 2
Who uses each
What makers pair each with
Questions
Amazon Web Services or Firebase: which do makers choose?
Of the 4,047 makers' products we know the AI tool behind, 460 chose Amazon Web Services (11%) and 187 Firebase (5%); 11 use both. Among the 1,010 launched in 2026, Amazon Web Services is in 8% and Firebase in 4%, against 10% and 7% of those launched in 2024 or earlier. They're different kinds of tool, hyperscaler cloud and backend platform, so the counts don't measure the same choice. Choose Amazon Web Services if the widest catalog of building blocks — Lambda, containers, managed databases, queues — to assemble your own infrastructure; choose Firebase if mobile apps that need offline sync and client-side SDKs.
Can you use Amazon Web Services and Firebase together?
11 makers' products we track use both, often one replacing the other or each for a different part of the product: Bricks, ConnectMachine, Kipps AI, Sukha, Blink.new and others.

