Technology stack
What we build with, and when
A stack is a set of decisions. For each technology below we say where it fits and why we would reach for it. Select a category to filter, or a technology to see our reasoning.
Select a technology to see when we use it
Languages
We choose a language for its runtime behaviour, its ecosystem and the team that will maintain the system, not for preference.
Frontend
Frameworks and tools for interfaces that must load fast, remain accessible and stay maintainable as the product grows.
Backend
Server-side frameworks matched to the workload: transactional systems, I/O-heavy APIs, AI services and internal tools.
Data
Storage and messaging systems, each selected for the access pattern and the consistency it has to guarantee.
Cloud
We build on the major public clouds and design to the client's chosen provider, using managed services where they reduce operational load.
Infrastructure
The tooling that makes environments reproducible and releases routine instead of events.
AI
The techniques we use to build AI systems that can be evaluated, observed and operated in production, not only demonstrated.
Web3
Blockchain technology applied as infrastructure, with the same engineering discipline as any system that handles value.
Product names are trademarks of their respective owners. They are listed to show the technologies we work with and do not imply endorsement, certification or a formal partnership.
Working with something that is not listed
The list is where we are deepest, not the limit of what we work with. Tell us about your estate.