Proven tools, chosen for the job.
We default to well-supported, widely used technology and reach for something specialised only when the problem calls for it. You should be able to hire for, run and extend whatever we build.
Our stack
What we work with, layer by layer
A representative list, not a limit. If your team already uses something else, we work with that.
Frontend
Typed, component-driven web apps that load fast and meet accessibility standards.
- React
- Next.js
- TypeScript
- Tailwind CSS
- Vue 3
Mobile
Shared code across iOS and Android, with native modules where the platform matters.
- React Native
- Expo
- Swift
- Kotlin
Backend
Services and APIs chosen for the workload: fast iteration, raw performance or both.
- Node.js
- Go
- Rust
- Python
- GraphQL
- gRPC
Data
Relational by default, with streams, caches and search added when the access pattern needs them.
- PostgreSQL
- Redis
- Kafka
- PostGIS
- ClickHouse
Cloud & infrastructure
Reproducible infrastructure on the major clouds, defined in code and reviewed like code.
- AWS
- Google Cloud
- Azure
- Kubernetes
- Terraform
Delivery & observability
Pipelines that test and deploy every change, plus the telemetry to see how it behaves in production.
- GitHub Actions
- ArgoCD
- OpenTelemetry
- Prometheus
- Grafana
AI & machine learning
Retrieval, fine-tuning and inference on infrastructure you control, measured with proper evaluations.
- PyTorch
- vLLM
- LangGraph
- pgvector
- Milvus
Quality & security
Automated tests at every level and security checks that run on every merge, not once a year.
- Playwright
- Vitest
- OWASP ASVS
- Dependency scanning
How we choose
Five questions before any new tool
Technology choices outlive projects. We write these answers down in the architecture RFC so you can see why each choice was made.
| Criterion | The question we ask |
|---|---|
| Maturity | Does it have stable releases, active maintainers and a large community? |
| Fit | Does it suit this workload, or are we choosing it because it is familiar or fashionable? |
| Your team | Can your engineers hire for it, run it and change it after we hand over? |
| Total cost | What will licences, hosting and maintenance cost over the next three years? |
| Portability | Does it use open standards so your data and code are not locked to one vendor? |
Stuck with a stack that is holding you back?
We review existing systems too. Get an outside view on what to keep, what to replace and in which order.