Tech stack selector
Not sure what to build your software on? Answer four quick questions about your app type, scale, realtime needs and team, and this tech stack selector recommends a mainstream, defensible stack, frontend, backend, database, realtime and hosting, with a one-line reason for each.
How it works
A tech stack is the set of technologies your software runs on: the frontend users see, the backend that holds your logic, the database that stores data, an optional realtime layer for live features, and the hosting it all runs on. Picking well early saves expensive rewrites later, and for most B2B products, the right answer is a boring, proven default rather than the newest framework.
This selector is rule-based. It maps four inputs, app type, stage, realtime needs and team size, to mainstream choices. Web apps default to Next.js on Node and PostgreSQL, deployed on Vercel; mobile apps to React Native or Flutter over a typed Node API; enterprise workloads add Kubernetes on a major cloud; and live features route to WebSockets or a managed service like Ably or Pusher.
Two forces drive the logic: hiring and horizon. JavaScript and TypeScript have by far the largest talent pool, so JS-centric stacks are easiest for small teams to build and maintain; larger or enterprise teams can justify specialist choices (Go, .NET, Java, Flutter) where throughput, typing or UI polish pays off.
Stack = frontend + backend + database + (realtime?) + hosting → matched to team skills
Once you know the stack, price the build with the software development cost calculator, or weigh building against off-the-shelf tools with the build vs buy calculator. Browse every tool at free tools.