Engineering

The technology behind our products.

A pragmatic, modern stack with a strong preference for boring, well-supported tools where they fit, and carefully chosen newer technology where it earns its keep.

Frontend stack

Modern JavaScript and TypeScript on the web, with React-based component systems for product surfaces and lightweight vanilla approaches where simplicity is the better answer. Performance and accessibility are baseline requirements rather than late-stage concerns.

Backend services

Node.js services and well-typed APIs (REST and, where appropriate, GraphQL). We favour explicit service boundaries, well-documented interfaces, and operational simplicity over architectural novelty.

Cloud & hosting infrastructure

Managed cloud hosting in established European regions, with content delivery networks for edge caching, and infrastructure-as-code where it provides genuine repeatability rather than ceremonial complexity.

Analytics pipelines

Privacy-aware analytics built around aggregated, minimally-identifying signals. We measure what helps us improve the product, and not more than that.

Security & privacy posture

Defence-in-depth: managed secrets, encrypted transport and storage, least-privilege access patterns, and structured incident response. Privacy reviews are part of the design process, not a separate stream.

Mobile application architecture

React Native for cross-platform efficiency where it suits the product, and native Kotlin or Swift where the platform deserves a first-class implementation. CI/CD pipelines and staged rollouts are standard.

Principles

The engineering choices we keep coming back to.

Boring where boring works

Mature, well-understood tools win unless there's a concrete reason to reach for something newer.

Observability first

Logging, metrics, and tracing are part of every service's first version, not a later retrofit.

Small reversible changes

Ship in small increments. Feature flags, staged rollouts, and easy rollbacks beat heroic releases every time.

Want to talk specifics?

Happy to dive into stack-level detail if it's useful to you — just let us know what you're trying to build.

Get in touch