Technology stack
Also called a tech stack or software stack.
A technology stack is the set of technologies used together to build and run an application, website or IT system. It includes programming languages, frameworks, databases, hosting infrastructure and supporting services.
People also use "tech stack" for a company's collection of business tools, such as its CRM, billing software and analytics platform.
Key takeaways
- A stack is the whole combination, not just a programming language or framework.
- Hosting bills are only part of its cost. Engineering time, maintenance and future migration matter too.
- For a startup, a stack the team can operate reliably is more useful than one chosen to impress investors.
- A list of technologies does not reveal how they connect, where data lives or who maintains them.
How the layers work together
In a web application, the frontend displays the interface. The backend handles business rules and requests. A database stores information, while hosting infrastructure runs the system.
MDN's documentation on server-side frameworks explains how frameworks provide tools for common tasks such as handling requests, accessing databases and authenticating users. They reduce what developers must build themselves, but they are only one part of the stack.
A subscription app could use:
| Part | Technology | Job |
|---|---|---|
| Frontend | React | Display the customer dashboard |
| Backend | Python with Django | Process requests and enforce business rules |
| Database | PostgreSQL | Store accounts and subscription records |
| Hosting | A managed application platform | Run the application |
| Supporting services | Payment processing and error monitoring | Collect payments and report failures |
There is no required number of layers. A mobile app, an internal reporting tool and an AI product will have different combinations.
A $400 hosting bill versus a $150 bill
Consider two hosting approaches for the same subscription app. These are illustrative figures, not market benchmarks. Both approaches meet the product's requirements, and engineering time is valued at an internal cost of $100 per hour.
| Monthly cost | Self-managed hosting | Managed hosting |
|---|---|---|
| Hosting bill | $150 | $400 |
| Infrastructure maintenance | 12 hours | 2 hours |
| Allocated engineering cost | 12 × $100 = $1,200 | 2 × $100 = $200 |
| Total including labor | $1,350 | $600 |
The managed option costs $250 more on the invoice but uses 10 fewer engineering hours. Its labor-inclusive cost is $750 lower: $1,350 − $600.
That does not automatically reduce cash burn by $750 if the engineers are salaried. The immediate benefit is time for product work. For a small startup, that could matter more than the hosting discount.
The result changes if the managed platform cannot meet the workload or its fees rise sharply with usage. Compare both today's costs and the cost of switching later.
What the documentation says
npm's package.json documentation describes how a JavaScript project records its package dependencies and separates development dependencies under devDependencies. Its engines field can specify compatible runtime versions.
These files reveal part of the stack, but not the whole system. They will not necessarily identify external services, hosting arrangements or where customer data is stored.
For technical diligence, pair the technology inventory with an architecture diagram. Name the person responsible for each major component and flag services that would be difficult to replace. Investors need to understand operational dependencies, not just recognize logos.
What to question before choosing
Start with the team's skills and the product's requirements. Question a technology choice if nobody can explain the problem it solves.
Pay particular attention to maintenance responsibility, data export and usage-based pricing. A service that saves development time can still create an expensive dependency. Conversely, building a generic function yourself can consume months without improving what customers buy.
There is no universal "investor-approved" stack. The useful question is whether the company can ship, support and change its product with the people and money available.
Technology stack versus framework
| Term | Scope | Example |
|---|---|---|
| Technology stack | The combination used to build and run a system | React, Django, PostgreSQL and hosting |
| Framework | A structure and tools for one part of development | Django for the backend |
Questions people ask
What is a technology stack?
It is the combination of technologies behind a system. When someone asks about a company's stack, clarify whether they mean the customer-facing product or internal business software. Those are different inventories.
What is another word for tech stack?
"Technology stack" and "software stack" are common alternatives. "Technology architecture" is related but broader: it describes how components connect and why they are arranged that way, not just which technologies are used.
Can you give me an example of a technology stack?
React for the interface, Django for backend logic, PostgreSQL for storage and a managed hosting platform form a web application stack. Payment processing, authentication and monitoring services can also be part of it.
What are the 5 layers of the AI tech stack?
There is no universal five-layer standard. One useful grouping is computing infrastructure, data, models, orchestration and applications. Different descriptions combine or split these layers, so check what the author includes rather than treating the number five as a rule.
