Free tool
Technology stack selector
Answer six questions and see a sensible starting point for the technology behind your product, with the reasoning for each choice and the trade-offs worth discussing. It runs in your browser and sends nothing.
About this recommendation: it is an educational starting point based on common patterns, not a final architecture. The right choice also depends on your team's skills, your existing systems and constraints that only a technical conversation will uncover.
This tool needs JavaScript
Without it, email us a short description of your project and we will talk through the technology options with you.
What the recommendation covers
Rather than naming a single product, the selector looks at each layer of a typical system and explains why a particular approach fits your answers. That makes it easier to challenge, and easier to adapt when something about your situation is unusual.
Frequently asked questions
Is this a final architecture decision?
No. It is a reasoned starting point for a conversation. Final choices depend on your team's skills, existing systems, budget and risks that only a technical discussion will reveal.
Does the tool use AI?
No. It follows a fixed set of rules written by people, so the same answers always give the same result and you can follow the reasoning behind each line.
Why does it often suggest managed services?
For most early-stage projects, time and focus are scarcer than infrastructure budget. Managed services hand routine operations to a provider while you learn what users actually need, and they can be replaced later if scale or cost demands it.
Why are Hong Kong and Mainland China treated differently?
Hosting and regulatory arrangements differ. A product serving users in Mainland China often needs a separate deployment and a local provider, and planning that early avoids an expensive redesign.
Why not recommend the newest technology?
New tools can be excellent, but mainstream technologies have better documentation, more developers who know them and fewer surprises. We favour the familiar where it lowers risk and newer options where they clearly pay off.
What if my project does not fit one type?
Pick the type closest to your main customer-facing need, then use the capabilities question to add the rest. A conversation can refine anything the tool cannot capture.
Can I change my answers?
Yes. Use Back at any step, or start again after you see the result.
What should I do with the result?
Use it as a conversation starter with any development team, including us. If you would like our comments, send it along with your enquiry.
Related tools and services
Want a second opinion on your architecture?
Share your project and, if you have one, the recommendation you received. We will tell you what we would keep and what we would question.
Request a project quote