What is a tech stack?

Why it matters

A tech stack is one of the few early decisions that follows a product for years. It affects who you can hire, since people know some tools and not others; how fast you can ship; how much hosting costs; and how long the thing stays maintainable before it needs a rewrite. You do not need to read code to care about it, because every one of those is a business outcome, not just a technical one.

What goes in one

Most stacks have a few layers: the front end that runs in the browser, the back end that runs on a server, a database that stores the data, and the hosting it all runs on. An API connects the layers and lets other systems plug in. For a typical web app the popular, well-supported combinations exist precisely because they cover these layers without nasty surprises.

A common mistake

Picking a stack for novelty rather than fit. The newest framework can mean a tiny hiring pool, thin documentation, and tools that break under real load. We choose boring, proven technology that the team can hire for and maintain, and we match the stack to the problem. That is also what a technical due diligence looks at: not whether the stack is fashionable, but whether it is a sane, supportable choice for what the company is actually building.