What Is a Tech Stack?
A tech stack is the combination of technologies a project is built with. Here is what that means in practice, the different types, and how tools are organized within one.
Contents
"What's your tech stack?" is one of the first questions developers ask each other. It is also one of the more ambiguous ones — depending on context, the answer might be a list of programming languages, a set of cloud services, or a description of someone's personal development environment.
The term means something real and useful. Here is what it covers.
What is a tech stack?
A tech stack is the complete set of software tools and technologies used to build and run a product or project. It includes many layers: the language the code is written in, the framework used to structure it, the database that stores data, the hosting infrastructure it runs on, and the services that handle specific functions like authentication or payments.
The term "stack" reflects the layered nature of modern software: technologies genuinely do stack on top of each other, with each layer depending on the ones below it.
Tech stack types
Not all tech stacks describe the same thing. Depending on who is using the term and what they are describing, "tech stack" can refer to different scopes entirely. Three types cover most of what developers mean.
Project tech stack
A project tech stack is the set of tools a specific product or system is built on. This is what most people mean when they say "our tech stack". It describes the full technical shape of the product: what the frontend is built with, what runs on the server, what database is behind it, how authentication works, and how the whole thing is deployed.
The project stack is what the Tekyous stack builder is primarily designed for (although not limited to). You can start from scratch in Sandbox mode, or let the recommendation engine generate a starting stack based on your project type and experience level in Questionnaire mode.
Developer tech stack
A developer tech stack is the set of tools a developer uses in their personal workflow — the environment in which they build, regardless of what they are building. This typically includes a code editor, an AI coding assistant, version control tooling, and a CI/CD setup.
The same developer might be contributing to multiple different project stacks, but their developer stack might stay the same the whole time. It is the professional toolkit they bring to every project, not the toolkit a specific project depends on.
Infrastructure tech stack
An infrastructure tech stack describes the tools and services used to run and operate a system — distinct from what the system is built with. Containers, servers, reverse proxies, and monitoring services are all infrastructure-layer concerns.
How to differentiate stack types
A clear split between types adds structure, but the separation is not always necessary or practical. A developer building a web app with Claude Code might want to include it in their stack, even though it is a developer tool rather than a direct part of the app itself. Docker can reasonably belong to all three categories at once. An LLM might sit in a developer tech stack, but can equally appear as an external API component within a project stack.
The lines are blurred by design. Tekyous labels predefined stacks by type, but users are free to build a stack that mixes all three at once.
Other tech stack types
The three above are what Tekyous covers. In broader usage, you will also hear:
- Marketing tech stack (or "martech stack") — tools a business uses for marketing: analytics platforms, email services, CRM, advertising. These sit outside the developer tooling scope.
- Productivity or project management stack — tools a team uses to collaborate and manage work: task trackers, communication platforms, documentation tools.
- AI tech stack — all AI tools being used within a project or organisation. Tekyous covers this partially through categories like LLM and AI Coding Agents, but tools like AI video generators fall outside scope.
- Monitoring stack — sometimes mentioned as its own category, but in practice this is a subset of the project or infrastructure stack. Tools for logging, tracing, and error tracking belong in the Observability & Monitoring category.
The distinction matters on Tekyous because the tool catalogue and stack builder are scoped to technical project tooling — the tools you use to build and run software. Marketing and productivity tools are out of scope.
Types of tools within a tech stack
A project tech stack spans multiple layers, each with its own category of tools. Here is how they group:
Languages — the programming languages the codebase is written in. The language choice shapes most of the decisions that follow. Browse Programming Languages.
Frameworks and libraries — the structured environments and reusable packages built on top of a language. This covers frontend frameworks like React, Vue, or Svelte; backend frameworks like FastAPI, Django, or Express; data and ML libraries like pandas or PyTorch; and data apps like Streamlit or Dash. JS metaframeworks like Next.js and Nuxt also fall here.
Databases — where data is stored and retrieved. Options range from relational databases to document stores, key-value caches, and vector databases. Browse Databases, including Backend-as-a-Service platforms like Supabase or Firebase.
Hosting and cloud — the infrastructure your project runs on: cloud providers, managed app hosting, and bare-metal servers. Browse Hosting & Cloud.
Authentication — the services that handle login, sessions, OAuth, and identity. Browse Authentication.
APIs and infrastructure — payment processors, GraphQL engines, and other cross-cutting infrastructure services. Browse APIs & Infrastructure.
DevOps and CI/CD — containers, orchestration, and automated deployment pipelines. Browse DevOps & CI/CD.
Developer tools — the tooling used to write, test, and manage code. This includes IDEs & editors, AI coding agents, and version control. Browse Development Tools.
No-code, AI builders, and automation — tools that let you build products or connect systems without traditional coding. Browse No-Code / Low-Code, AI Builders, and Automation & Integration.
Data engineering and analytics — tools for building data pipelines, transforming data, and visualizing results. Browse Data Engineering & ETL and BI & Analytics.
AI services — LLM providers used for AI-powered features, from chat completions to embeddings and reasoning models. Browse LLM.
Observability and monitoring — logging, monitoring, tracing, and error tracking for your running system. Browse Observability & Monitoring.
If you want to explore how tools across these layers fit together, the Tekyous stack builder is built exactly for that. For a practical guide to making the actual technology decisions, see How to Choose a Tech Stack in 2026.
Related Stacks
Supabase + Next.js
ProjectThe fastest way to launch a modern web app. Next.js handles the frontend and API routes; Supabase provides Postgres, auth, realtime, and storage out of the box.
Project tech stack example.
VS Code + Claude Code + GitHub
DeveloperThe best of both worlds: VS Code stays open for manual editing and file navigation while Claude Code runs autonomously in the terminal for larger tasks. GitHub ties it together for version control. A practical hybrid for developers easing into agentic workflows.
Developer tech stack example.
Development
n8n Self-Hosted + Postgres
InfrastructureSelf-host n8n on your own VPS for complete data ownership and no per-workflow pricing. PostgreSQL stores workflow executions and credentials; Redis queues background jobs for reliable at-least-once execution. Docker keeps the stack reproducible across any Linux host.
Infrastracture tech stack example.
