Skip to main content

Industries

We work with teams infour specific places.

The services are the same. The pain points, traffic shape, and failure modes are not. Pick the closest fit and the page speaks your industry's language.

What does not change

The infrastructure layer is the same everywhere

The four pages below speak in each industry's own terms. Underneath that vocabulary the machinery is identical, which is why the same team can work across all of them.

  1. The failure modes are shared

    A disk fills, a certificate lapses, a deploy takes the site down, a backup turns out never to have been restorable. None of that is particular to an industry, and all of it is what the work is mostly about.

  2. The traffic shape is not

    A shop peaks on a campaign, a SaaS platform climbs steadily, a hosting provider carries other people's spikes. Capacity and cost decisions follow that curve, and it is the one thing worth knowing your industry for.

  3. The vocabulary differs, the questions do not

    What breaks first, what does it cost when it does, and who gets woken up. Those are the same three questions on every one of these pages.

  4. So pick the closest fit, not the exact one

    If none of the four matches, the work is still the same work. The page is there to save you translating your situation into infrastructure terms, nothing more.

None of the four quite fits? Say what you run and it gets read the same way.

Describe your setup

Not one of these four?

The work is industry-agnostic at the infrastructure layer. If your team runs production on AWS or Linux and needs senior engineering, the conversation starts the same way.