Skip to content
Why this page exists

Most of the systems we are asked to take over were built without any of this. There are no tests, so nobody knows what a change will break; there is no documentation, so the knowledge left when the developer did; and there is no deployment process, so releases happen by hand on a Friday.

We work the opposite way, and we publish the standards so you can hold us to them. They are the same standards this website is built to.

How we build
Frontend
React, TypeScript, modern CSS — accessible interfaces that perform on low-end devices.
Backend
Node.js, Python, PostgreSQL, REST and GraphQL APIs.
AI
Custom models where they earn their cost, established providers where they do not. Every AI feature can hand the task to a person.
Infrastructure
Docker, CI/CD, cloud or on-premise deployment with monitoring and backups from day one.
Practice
Code review on every change, automated tests, written documentation, handover as a deliverable.
Standards

Six commitments you can check against the work we deliver.

Code review on every change

Nothing reaches the main branch without a second pair of eyes.

Automated tests as a deliverable

Coverage on the logic that matters, run on every commit.

Accessibility to WCAG 2.2 AA

Checked before handover, with known limitations stated.

Performance budgets agreed up front

A number in the contract, enforced in the build.

Documentation for the next team

Architecture, decisions and runbooks, not just comments.

Handover as a phase

Planned and funded, not assumed to happen for free.

Hold us to this.

If you are evaluating us as a vendor, ask how each of these applies to your project. We will answer specifically.