Technology
Boring by default. Novel where it pays.
31 technologies we run in production. Novelty has a carrying cost — a dependency nobody else on the team understands is a liability, not an advantage — so we default to well-supported choices and spend the novelty budget where it changes an outcome.
Interfaces that stay fast on the devices your users actually have.
- React
- Next.js
- Vue
- Angular
- TypeScript
- Tailwind CSS
How we choose
Every significant choice is written down.
Architecture decision records, kept in your repository, stating what we picked, what we rejected, and why. Six months later nobody has to reverse-engineer the reasoning — including us.
Can you hire for it?
A technology with a small talent pool becomes a retention risk. If you cannot replace the person who chose it, it was the wrong choice regardless of merit.
How does it fail?
Every dependency fails eventually. We prefer things whose failure modes are documented and observable over things that are faster when everything works.
Who maintains it?
A single-maintainer package in a critical path is a risk with no mitigation. Funding, release cadence and issue response matter more than benchmarks.
What is the exit?
Before adopting something we ask what replacing it would cost. If the answer is a rewrite, it needs to earn that with a very large advantage.
Categories shown: Frontend · Backend · Data · Cloud · DevOps · Observability. Absent from this list is as deliberate as present — we do not claim expertise in things we have not run in production.
Start here
Tell us the problem.
We'll be honest about the fit.
A first conversation costs nothing and is useful even if you go elsewhere — you'll leave with an architecture opinion and a realistic sense of scope.
- Reply within 24 hours
- No sales sequence