What we do

Four kinds of problem. If yours isn't one of them, ask anyway.

Everything we build is software or hardware doing a specific job for a specific business. These are the four shapes that job usually takes.

integration

Systems that talk to each other

Middleware between systems that were never designed to meet. Orders from the website into whatever fulfils them, invoices into accounts, status back to the customer, a supplier's feed into your own database. Mapped, validated, routed, logged, and still running at 3am.

Typical for: any business running two or more systems that don't share data, from ecommerce and distribution to field services and manufacturing. Anyone re-keying between screens.

Integration
shop ↔ accounts ↔ crm ↔ ops rest · sftp · edi · webhooks field mapping · rejection handling · audit log
software

Software built for the job

The tool your team has wanted for years that no vendor sells, because only you need it. Internal apps, operational dashboards, portals for your customers or suppliers, the spreadsheet that should have been a system a long time ago.

Typical for: operations teams with a process nothing off the shelf fits, businesses outgrowing spreadsheets.

Bespoke software
internal tools · portals · dashboards go · php · postgres specified with you · documented · maintained
hardware

Hardware and the physical world

Where the software meets the physical world. Sensors, controllers and displays. Remote monitoring of equipment, environments and sites you can't be at. Industrial kit, pick walls and light-directed systems where they're needed, and the integration that gets all of that data somewhere useful.

Typical for: production sites, warehouses, workshops, plant rooms, anyone who needs to know what a machine or a space is doing without walking over to look.

Industrial solutions
sensors · controllers · displays remote monitoring · industrial control · pick walls physical → software → people
infrastructure

Infrastructure that stays up

The layer everything else depends on. Servers and cloud, deployment pipelines, monitoring, backups, security. Built so it doesn't need thinking about, and looked after so it stays that way.

Typical for: anyone running software they depend on, migrating off an old server, or who last thought about backups when they set them up.

Infrastructure
linux · caddy · managed databases ci/cd · monitoring · backups migrations · hardening · on-call

Something else

If it can be built, it's probably in scope.

Automation, AI agents, data pipelines, odd bits of electronics, the thing you're not sure anyone does. Describe the problem and we'll tell you whether we're the right people for it, and who is if we're not.

Describe the problem