Technologies we build with
The stack, grouped by layer. Every page says where that technology fits — and, just as usefully, where it does not.
Our stack
Technologies and platforms we work with
Grouped by family. Every item links through to a write-up of how we use it, what it is genuinely good for and where it is the wrong choice.
Architecture and orchestration
Cloud technologies
AWS services
Azure services
Google Cloud services
Frontend frameworks
API programming
Mobile programming
Databases — relational
Databases — NoSQL
DevOps — source control
DevOps — automation
Testing and quality
Integrations
Design and UI tools
In depth
Frontend, backend, mobile, data and cloud
We pick per project from your requirements, your existing systems and who will maintain the result afterwards.
Frontend
What runs in the browser
Backend
Application logic and services
Mobile
Android and iOS
Databases
Where the data lives
Cloud and platform services
Hosting, storage and managed services
AWS
Cloud platform
Microsoft Azure
Cloud platform
Google Cloud
Cloud platform
Docker
Containers
Kubernetes
Orchestration
CI/CD
Delivery pipeline
Amazon EC2
Compute
Amazon S3
Object storage
AWS Lambda
Serverless compute
Amazon RDS
Managed database
CloudFront
CDN
Azure App Service
Managed hosting
Azure Functions
Serverless compute
Azure Blob Storage
Object storage
Azure SQL
Managed database
Entra ID
Identity
Compute Engine
Compute
Cloud Storage
Object storage
Cloud Run
Container hosting
Cloud Functions
Serverless compute
BigQuery
Analytics warehouse
DevOps and delivery
Source control, pipelines and releases
Testing and quality
How the work is proved
Integrations
The systems your software must talk to
Design and interface
How it is designed and made usable
From the browser down to the backups
A production system is a set of layers, each with a job. Choosing a technology means choosing it for one of these, not for all of them.
Frontend
React, Next.js or Angular in the browser.
API layer
REST or GraphQL with validation and auth.
Backend
Node.js, Python, Laravel, Java or .NET.
Database
PostgreSQL, MySQL or MongoDB.
Cloud
AWS, Azure or Google Cloud.
Operations
Pipelines, monitoring, backup and recovery.
Tell us what you are trying to build
Describe the problem in plain language and we will tell you what it would take to solve it — the approach, the moving parts and the sensible order to build them in. No obligation either way.