Quick answer
A tech stack (technology stack) is the combination of programming languages, frameworks, databases, infrastructure and third-party tools that a team uses to build, run and measure a software product.
What is a tech stack?
A tech stack (technology stack) is the combination of technologies a team uses to build, run and measure a software product: programming languages, frameworks, databases, servers and infrastructure, plus the third-party tools for analytics, support, payments and marketing. It is called a stack because each layer is built on the one beneath it, from the operating system up to what the user sees.
Engineers usually mean the application layers. Product and marketing teams also include the business tools, sometimes called the martech stack. Both views are useful; problems often appear where they meet.
The layers of a tech stack
| Layer | What it does | Examples |
|---|---|---|
| Front end (client) | What runs in the browser or app | HTML, CSS, JavaScript; React, Vue, Svelte; Swift, Kotlin, Flutter |
| Back end (server) | Business logic and APIs | Node.js, Python, Go, Java, PHP, Ruby |
| Database and storage | Stores application data | PostgreSQL, MySQL, MongoDB, Redis, object storage |
| Infrastructure and DevOps | Where and how it runs | AWS, Google Cloud, Azure; Docker, Kubernetes; CI/CD |
| Data and analytics | Collects and analyses behaviour and business data | Event tracking SDKs, data warehouse, BI, product and web analytics |
| Business tools | Run customer-facing operations | Live chat and help desk, CRM, email, billing, feature flags |
Classic stack examples
- LAMP: Linux, Apache, MySQL, PHP. Powers a large share of the web, including WordPress.
- MEAN / MERN: MongoDB, Express, Angular or React, Node.js. JavaScript end to end.
- Jamstack: pre-built static pages served from a CDN, with APIs for dynamic parts.
- Mobile: native Swift (iOS) and Kotlin (Android), or one codebase in Flutter or React Native, with a cloud back end.
An example SaaS stack
A typical early-stage B2B SaaS might run React and TypeScript on the front end, a Node.js or Go API, PostgreSQL and Redis, on one cloud provider with containerised deploys. Around it: payments, transactional email, web and product analytics, live chat, error monitoring and a CRM. That is already a dozen vendors before the first hire in marketing.
How to choose a tech stack
- Product needs. Real-time features, heavy data processing and offline mobile use point to different choices.
- Team skills. The stack your team knows well beats a better stack nobody on the team has shipped.
- Time to market. Mature frameworks with good defaults get you live faster.
- Hiring pool. Popular technologies are easier to hire for; the Stack Overflow Developer Survey is a useful reference.
- Cost. Licences, hosting and the people needed to run it.
- Scale and security. Can it handle ten times today's load? Does it meet your compliance needs?
- Integration. Do the tools share identifiers and send data to each other, or will you maintain glue code?
Tool sprawl: a worked audit
Business tools accumulate one at a time. Each adds a script to the site, a monthly bill and another copy of customer data. Sample data from an audit of a marketing site:
| Before | After | |
|---|---|---|
| Tracking and chat scripts on every page | 5 (two analytics tools, heatmaps, chat widget, a forgotten A/B test snippet) | 2 (one analytics script that also loads chat, plus the ads tag) |
| Third-party JavaScript downloaded | 410 KB | 140 KB |
| Monthly spend on these tools | $2,380 | $1,410 |
| Places customer identifiers are copied | 5 | 2 |
The savings came from removing duplicate tools, not from cheaper ones. The performance gain mattered as much as the money: third-party scripts compete with your own code for the main thread. The HTTP Archive's Web Almanac tracks how widespread third-party scripts are across the web.
Where TapCub fits in a stack
TapCub sits in the data and business-tool layers: web, app and mini-program analytics plus live chat, sharing one visitor ID.
- One web script collects analytics and, with one switch, shows the chat widget; no extra snippet.
- SDKs for iOS, Android, Flutter, React Native, HarmonyOS and WeChat mini programs, and an HTTP API for server-side events.
- AI agents can query your data through MCP; see connect AI agents with MCP.
If you are consolidating, the questions in the checklist above still apply: what each tool is for, who uses it, and whether two tools are answering the same question.
Sources
- Wikipedia, Solution stack.
- Stack Overflow, Developer Survey.
- HTTP Archive, Web Almanac: Third Parties.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.
Technical Engineer
Focuses on tracking code, SDKs, and API integrations, with practical guidance on implementation checks and troubleshooting.