Technologies
Technologies we work with
We pick technology to fit the problem and the systems you already run, not the other way round. These are the platforms and practices that come up most in our work.
Identity providers
Microsoft Entra ID (formerly Azure AD)
Microsoft's cloud identity service, a natural fit where staff already use Microsoft 365. Supports SAML and OpenID Connect sign-in.
Okta
An independent identity platform that connects to many applications and directories; often chosen when systems span several vendors.
Cloud platforms
Amazon Web Services (AWS)
Amazon's cloud platform, with managed services for compute, storage, databases, messaging and more.
Microsoft Azure
Strong where an organization runs on Microsoft identity, databases and tooling.
Google Cloud (GCP)
Google's cloud platform, with managed services for applications, containers, data and analytics.
Delivery practices
Infrastructure as code
Cloud resources defined in version-controlled files, so environments are repeatable and changes are reviewed.
CI/CD pipelines
Automated build, test and deployment, so every change follows the same checked path to production.
How we choose
The best choice usually follows from what you already have. If your staff sign in with Microsoft 365, Entra ID is the obvious identity provider; if your data already lives in one cloud, building next to it avoids cost and complexity. Where there is a real choice, we set out the options, the trade-offs and our recommendation in writing before anything is built.
Read more in our insights, for example on SAML versus OpenID Connect and REST versus GraphQL.
Let's build something great together
Ready to talk about custom software? Tell us about your project requirements and we will get back to you.