Skip to content

We build the software that has to keep working.

Most of it is the unglamorous kind. The booking system. The internal tool nobody demos. The service that pages someone at three in the morning when it stops. We build the site that announces it too, and the same people do both.

See the work

What we build

Platforms and servicesThe system the business runs on

Internal toolsThe screen your team lives in all day

Booking and schedulingWhere money and time meet

Data and reportingGetting the number out of the machine

Keeping it runningMonitoring, on-call, the 3am page

The site that announces itSame team, same week

Platforms and servicesThe system the business runs on

Internal toolsThe screen your team lives in all day

Booking and schedulingWhere money and time meet

Data and reportingGetting the number out of the machine

Keeping it runningMonitoring, on-call, the 3am page

The site that announces itSame team, same week

Platforms and servicesThe system the business runs on

Internal toolsThe screen your team lives in all day

Booking and schedulingWhere money and time meet

Data and reportingGetting the number out of the machine

Keeping it runningMonitoring, on-call, the 3am page

The site that announces itSame team, same week

How a job actually goes.

Most jobs start with a call and a spreadsheet somebody is tired of. The first week goes on reading what is already there: Still running, and rarely documented. Usually it is also the thing that takes the money, which is why it gets read before anyone proposes replacing it., the tickets, and The half hour where the person who built it says what the comments do not. Worth more than the repository. nobody wrote down. Then One date, agreed early. Holding it means saying out loud what will not be in the first release, rather than moving the date and telling you later., and the scope moves to protect it rather than the other way round. After it ships someone stays A phone that rings at three in the morning and a person who answers it. For an agreed window, then handed over with the runbook., because the fortnight after launch is when you find out what you actually built.

What it gets built with.

Boring where it counts. The choices worth making are the ones someone else can still hire for in five years, not the ones that look good in a talk.

TypeScriptReactNode.jsGoPythonPostgreSQLRedisDocker
KubernetesTerraformAWSCloudflarePlaywrightOpenTelemetryGrafanaPagerDuty