Front end
- React
- Angular
- Vue.js
- TypeScript
- Next.js
- HTML & CSS
Technologies
Mainstream tools, chosen for your situation
We prefer proven, well-supported technology that your team can hire for and maintain, and we pick the stack for your constraints, not our habits. Here is what we work with most.
Application development
Front end, mobile and back end
Mobile
- Swift
- Kotlin
- Flutter
- React Native
- Bluetooth LE
- Offline sync
Back end
- Java
- Node.js
- Python
- .NET / C#
- PHP
- Go
Data
Data platforms, pipelines and reporting
Databases
- PostgreSQL
- SQL Server
- MySQL
- MongoDB
- Redis
- InfluxDB
Data engineering
- Kafka
- Airflow
- dbt
- Spark
- Python
- SQL
Dashboards & reporting
- Power BI
- Looker
- Tableau
- Grafana
- Metabase
- Excel automation
Platforms & quality
Cloud, DevOps, testing and industrial systems
Cloud & DevOps
- AWS
- Microsoft Azure
- Google Cloud
- Docker
- Kubernetes
- Terraform
- GitHub Actions
- GitLab CI
Testing
- Playwright
- Cypress
- Selenium
- Appium
- JUnit
- pytest
- k6
Buildings & industry
- Niagara 4
- BACnet
- Modbus
- OPC UA
- MQTT / Sparkplug B
- Project Haystack
How we choose
The questions behind every stack decision
A technology choice outlives the project that made it. Before recommending anything, we ask who will maintain the system, where it will run, how long it must last, and what it must connect to.
If your organisation already has standards, we work within them. If you don’t, we’ll explain the trade-offs in plain language and write the decision down.
- MaintainabilityCan your team, or the next one, hire for it and support it?
- FitDoes it suit the hosting, the data volumes and the integrations?
- LongevityIs it actively supported, with a credible long-term roadmap?
- Total costLicences, hosting and the people needed to run it, not just the build.
Need a second opinion on your stack?
Tell us what you’re building or running. An engineer replies within 24 hours.