How Makers Build

https://www.ondial.ai/

this is a good tool !

nice one! 1

Hi Fazier 👋 I built How Makers Build because every "what stack should I use" thread ends in opinions. So I collected evidence instead: for each decision behind a web SaaS or AI app (database, auth, hosting, payments, email, LLM APIs…), which tools 6,600+ makers' products actually use — each claim linked to a source you can open, like the maker's own words, public code, DNS records or subprocessor lists. It's free, no sign-up. I'd love to hear which decision you'd want covered next, or any tool you think I've got wrong.

Love that every usage has a source link, most stack lists are guesswork. I just moved my site off Netlify because their credit plan charges for every deploy, which none of the comparisons I read mentioned. Does the pricing calculator cover usage-based gotchas like per-deploy or bandwidth charges? That's where my real costs surprised me.

Really clean concept! It’s super helpful to see transparent proof of what makers are actually using to build and ship their products. Are you planning to add tech-stack filtering in the future?

Really clean concept! It’s super helpful to see transparent proof of what makers are actually using to build and ship their products. Are you planning to add tech-stack filtering in the future?

Sourced usage data is a refreshing take on stack research — opinions are cheap, but pull requests and source links are hard evidence. The 'check my stack' idea especially stands out; most teams never revisit their tool choices after the first commit. Curious how often the migration trends get updated.

Sourcing the claims is a differentiator - most galleries in this space just list what builders say about themselves. Curious how you decide what counts as verifiable: a live URL, a screenshot, or something the builder submits? That rule will shape trust more than the design does. Also worth showing when a link was last checked, since project pages tend to rot quietly.

Really useful angle - sourcing every claim directly helps a lot when evaluating tools for my own workflow. Would love to see a filter by industry or a way to export the sourced claims into a spreadsheet, since I often need to share comparisons with my team.

Sourcing every claim is what makes this useful. Most "stack" lists are guesses or affiliate links. "Check my stack" is a smart touch. One request: could you show how recent each source is? A job posting from 2023 says less about what a product runs on today than a pull request from last month. Filtering by product size (solo maker vs 20-person team) would help too, since the right choice changes a lot with scale.

Sourcing every claim with real evidence and source links makes this so much more valuable than typical guesswork stack lists. 'Check my stack' is a brilliant touch for teams!

Sourcing every claim with real evidence and source links makes this so much more valuable than typical guesswork stack lists. 'Check my stack' is a brilliant touch for teams!

The 'every claim sourced' angle is the right answer to stack-shopping fatigue — nobody trusts another 'we use Notion' listicle. Do you verify versions over time or is it a point-in-time snapshot?

Linking every tool claim to a source like public code or a subprocessor list, then letting you paste your own stack to compare, is a smart way to cut through stack opinions. If your business ever wants to put AI to work, PZERO is worth a look at pzero.studio.

Love the idea of making real product decisions and their costs transparent. As a product designer and AI product builder, I know how much time goes into choosing the right tools and stack. Seeing what others actually use, why they chose it, and what they pay could save makers a lot of time and money. Great concept!

Love the idea of making real product decisions and their costs transparent. As a product designer and AI product builder, I know how much time goes into choosing the right tools and stack. Seeing what others actually use, why they chose it, and what they pay could save makers a lot of time and money. Great concept!

Finding real, verified tech stacks without the marketing fluff is always a challenge. Being able to compare tools side-by-side and see actual pricing for your scale is a game-changer when deciding what to build with. Great work on this! 👏

I am totally amazed by how other developers use almost the same version or overlapping pieces of the stacks. It gives you real insight into market trends and what is latest in the tech community.

The distinction between a point-in-time stack snapshot and changes found in pull requests is especially useful. Could the comparison view surface a ‘last independently observed’ date beside each claim? That would make it easier to weigh older job posts against newer code evidence.

Sourcing every claim is what makes this useful. Most stack lists are just affiliate links. The pricing calculator at launch vs traction vs scale is the part I wish I'd had earlier, since the cheap choice at 10 users is often the expensive one at 10,000. Do you plan to cover media heavy stacks too, like video storage, transcoding and streaming? That's where the costs surprised me most.

Really like the "every claim sourced" approach — stack advice online is mostly opinions, so being able to open the maker's own words or subprocessor list to verify a tool choice is genuinely useful. The migration trends from real pull requests are the standout feature for me: they show what's actually being adopted versus abandoned, which is data you can't get from a blog post. Would love to see this extended beyond web SaaS to mobile or data engineering stacks down the line.

Showing the source next to each usage is what makes this trustworthy. What happens when sources disagree, say a maker wrote about one database while their subprocessor list or recent code shows another? Showing that conflict openly instead of picking a winner would be valuable, since it often means a migration is under way. Do you rank evidence types, for example code above a job posting?