A tech stack is the set of technologies a product is built with: the programming languages, frameworks, database, cloud platform and services. Non-technical founders do not need to choose it and should be wary of vendors who ask them to. What matters is that the stack is mainstream, well supported and easy to hire for, so that the product can be maintained by any competent team, not only the one that built it.
In plain terms
If the product were a building, the tech stack would be the materials and methods: steel frame or timber, which kind of wiring, which plumbing standard. A builder chooses them from experience and the job's requirements. The client cares that the choices are sound, standard and serviceable by other tradespeople later.
What is in a tech stack?
| Layer | What it is | What founders should check |
|---|---|---|
| Frontend framework | The tools used to build the web app or mobile apps | Mainstream, actively maintained, large talent pool |
| Backend language and framework | What the server-side logic is written in | Same: mainstream, maintained, easy to hire for |
| Database | Where data is stored | A well-known database suited to the product's data |
| Cloud platform | Where it all runs | A major provider, in your company's account |
| Third-party services | Payments, email, maps, analytics and so on | Each is a dependency with a cost and a switching cost |
| Tooling | Testing, deployment, monitoring | That it exists. Its absence is the warning sign. |
Does a founder need to choose the stack?
No. A non-technical founder is not equipped to compare frameworks, and a vendor who asks you to choose is either testing you or avoiding responsibility. What you should do is set the constraints and let the team choose within them: mainstream technologies, a major cloud provider, everything in your accounts, and a written rationale for the main choices. If you have a technical advisor, have them review the rationale. Our post on what investors look for in your tech explains why "boring" is the compliment you want.
Why should a founder care at all?
- Hiring. A mainstream stack means the next engineer you hire already knows it. An unusual one means a small, expensive pool.
- Longevity. Technologies fall out of maintenance. Popular ones last longer and get security updates.
- Portability. If you change vendors, another team must be able to pick the product up. Standard stacks make that a handover. Proprietary ones make it a rebuild.
- Investor questions. "What is it built with?" is a standard diligence question, and the answer they want is unremarkable.
Warning signs
- A vendor's own proprietary framework that nobody else uses.
- A stack chosen because the team wanted to try something new.
- No tests, no automated deployment, no monitoring.
- Reluctance to write down what was chosen and why.
Questions to ask your development team
- What is the stack, and why these choices for this product?
- How large is the pool of developers who know it?
- Could another competent team take this over from the documentation alone?
Related terms
Frequently asked questions
Is there a best tech stack for startups?
No single one. Several mainstream combinations are excellent and any competent team will have a preferred one. The choice between them matters far less than the team's skill with it and the product's actual requirements.
Should I ask for the same stack a famous company uses?
No. Famous companies have problems and teams you do not. Ask for a stack suited to your product, your budget and the people you will be able to hire.
What if my current product is on an unusual stack?
Get a technical advisor to assess how hard it would be for another team to take over. If the answer is very hard, plan a gradual move to mainstream technologies as part of the next phase rather than an emergency later.