Skip to main content

Technology

Technology that fits your organisation.

Your existing software, standards and internal expertise come first. We work with what is already in place where it remains suitable. If there is no suitable technical environment yet, we establish one using relevant standards and recommend technologies that fit the work and its risks.

From design to production

The technical foundation for building and operating dependable software.

The exact combination depends on your environment and the consequences of failure. These are the technologies and controls we normally use or support.

Applications and APIs

We build interfaces, services and business rules that support the work from user interaction through to system integration.

  • .NET for APIs and client-specific business logic
  • React or Next.js for web applications
  • React Native, .NET MAUI or Flutter for mobile applications, selected according to the customer's requirements

Cloud and on-premises

We deploy software in an environment your organisation can govern, operate and connect to its wider system landscape.

  • Microsoft Azure, AWS and Google Cloud
  • On-premises infrastructure when required

Data and integration

Preserve useful systems and data investments instead of replacing them merely to impose a preferred stack.

  • Existing databases where they remain suitable
  • Cloud-native databases where appropriate
  • PostgreSQL as the preferred general-purpose option

Infrastructure and observability

Keep environments reproducible and make production behaviour visible to the people responsible for operating the system.

  • Terraform for infrastructure as code
  • OpenTelemetry for application telemetry
  • Platform-native monitoring, logging and error tracking, such as Azure Monitor

Identity, access and verification

We match identity and access management, automated testing, code analysis and dependency checks to the system's risks.

  • Cloud-native identity services or Auth0 for on-premises solutions
  • Playwright for browser and end-to-end testing
  • SonarQube, Qodo and OWASP Dependency-Track

Reviewable design and architecture

Give operational and technical stakeholders concrete material to examine before and during implementation.

  • Figma for interfaces, workflows and collaborative prototypes
  • IcePanel for system boundaries and architecture models
  • Visual models do not replace technical verification

How we choose

A deliberate choice, not a fixed stack.

Technology choices should remain explainable to the people funding, using, evaluating and operating the software.

  1. 01

    Your requirements come first

    Client standards, mandated platforms, data location and contractual constraints establish the available choices.

  2. 02

    Review the existing environment

    We consider existing systems, integrations, internal skills and investments before proposing replacement or migration.

  3. 03

    Establish a sound foundation when needed

    If no suitable environment exists yet, we set it up using relevant industry standards for security, maintainability and operation.

  4. 04

    Fit the technology to the work

    Workflows, users, exceptions, volume, failure handling and continuity needs shape the architecture.

  5. 05

    Consider risk and ownership

    Security, compliance, maintainability and the team that will operate the system affect every technical decision.

  6. 06

    Apply our usual defaults when appropriate

    We generally prefer Azure, .NET, React or Next.js, Terraform, OpenTelemetry and PostgreSQL when no requirement or technical constraint points elsewhere.

Your environment

Discuss the systems, standards and constraints already in place.

Share your current platform and the software decision you need to make. We can identify what should remain, what needs to change and which technical questions should be tested first.

Discuss your environment