What we do

Platform development

Web applications and the services behind them.

Authentication, permissions, billing, admin surfaces, audit trails — the parts that never get demonstrated and that every operator depends on. We build them to be handed over: the reasoning written down, the failure modes named, the credentials rotatable without a rewrite.

Running today: This platform is one of them. Dealer accounts, licensing, ticketing, per-device API credentials and a full audit trail, running in production.

Server builds and infrastructure

The machines underneath, specified and run properly.

Storage, virtualisation, containers, networking, and backups that somebody has actually restored from rather than merely configured. Sized for the workload in front of us — a system that is twice as complicated as it needs to be is twice as many things to go wrong at three in the morning.

IT consultation

Working out what the system should be, before anyone buys anything.

Sometimes the answer is a new platform. More often it is a smaller change than expected, a vendor not to sign with, or an existing system used properly. We will say so — an honest short engagement is worth more than a long one that solved the wrong problem.

Control4 driver development

DriverWorks drivers, with the licensing and support around them.

Drivers for dealers and integrators, distributed through a portal that handles licence assignment, beta and stable release channels, and support tickets that already carry the controller's context. Built with our own tooling, which lints and packages a driver against the same rules Control4's own do.

Running today: tc-amp3, a multi-zone amplifier driver, shipping today through the dealer portal.