Tech stack

Definition
A tech stack is the set of technologies a product is built on: the framework, the database, the hosting, and the services bolted on.

Why it matters

Every later decision is built on top of the stack, so a poor choice early means an expensive rewrite later. For a lean team building with AI help, there is an extra rule. AI coding tools write far more reliable code in popular, well-documented tools than in niche ones, because they have seen much more of that code. A mainstream stack also means more ready-made libraries, more answers online and an easier time hiring.

How to apply it

  • Choose the proven, well-documented option over the clever or unfamiliar one.
  • Prefer combinations many teams already use, so examples and fixes are easy to find.
  • Let vendors run the plumbing where possible, such as hosting, sign-in and payments, rather than building it.
  • Change the stack only when a real limit appears, not because a newer tool exists.
  • Write down why each major piece was chosen, so a later decision can weigh the same trade-offs.
  • Keep the stack small. Every extra tool is another account, bill and thing that can break.

What it is

A tech stack is the list of tools that make a product work, usually described in layers. The front end is what the user sees, built with a framework such as React. The back end holds the logic. The database stores the records. Hosting runs it all on the internet. Around these sit services for sign-in, payments, email and analytics.

The phrase is also used loosely for the software a business runs on: its website platform, CRM and accounting tool. The marketing equivalent is the marketing stack.

Worked example

A two-person software-as-a-service team chooses a hosted Postgres database that already includes sign-in and an API, so neither founder builds those by hand. They keep the marketing site on a visual website builder so either of them can edit a page without touching code. Because everything is mainstream, their AI coding agent produces working code reliably.

  1. Article

    Marketing stack

    The equivalent set of choices on the marketing side.

  2. Article

    Sales tech stack

    The tools a sales team runs on.

  3. Article

    API integration

    How parts of a stack connect to each other.

  4. Article

    Version control

    The discipline every change to a stack runs through.

  5. Article

    Technical debt

    The cost that builds up when stack choices are rushed.