Technology
Chosen for the job, not the hype.
We are opinionated by experience rather than stack-agnostic by marketing. A narrow stack we know deeply beats a wide one we know slightly — especially three years in, when someone has to maintain it.
01The ecosystem
What we reach for first.
The core stack sits on the inner ring — these are the tools we are accountable for. The outer ring is what we bring in when a project calls for it.
Of EPI
The ecosystem
One stack, chosen on purpose.
We are deliberately not stack-agnostic. These are the tools we know deeply enough to be accountable for — in production, under load, years after launch.
Select a node to inspect
02Full inventory
The rest of the toolbox.
Everything else we have shipped with. Presence on this list means production experience, not a tutorial.
Frontend
- Vue
- Nuxt
- React
- Next.js
- TypeScript
- Tailwind CSS
Backend
- Node.js
- NestJS
- Nitro
- Python
- FastAPI
- Go
Mobile
- Flutter
- React Native
- Swift
- Kotlin
Data
- PostgreSQL
- MySQL
- Redis
- Prisma
- Drizzle
- Vector DBs
Cloud & DevOps
- AWS
- Cloudflare
- Vercel
- Netlify
- Docker
- Kubernetes
- Terraform
- GitHub Actions
AI
- Claude
- OpenAI
- RAG
- Agents
- Embeddings
- Evals
03Selection criteria
How something gets on this list.
It has to still be here in five years
We weight boring longevity over momentum. A framework with a shrinking maintainer count is a liability you inherit, not a feature.
Someone else has to be able to hire for it
If you cannot recruit engineers who know it, we have handed you a dependency on us. That is good for an agency and bad for a client.
It has to fail in ways we understand
Production experience is mostly about knowing the failure modes. A tool we have only used in a prototype does not qualify for your critical path.
It has to survive the second year
Plenty of stacks are fast to start and painful to extend. We optimise for the point where the codebase is large and the original authors have moved on.
Different stack?
Running somethingnot on this list?
We work inside existing codebases regularly. Tell us what you run and we will be straight about whether we are the right team for it.
Or email us directly — info@techiesofepi.com