The SideStep

Infrastructure

We run our own: the servers, the pipeline that ships every change, and the alerts that tell us when something's wrong. It's what lets a small team ship often and still sleep.

How a change ships

Run a release, or send a broken one and watch the checks stop it before production.

  1. Merge

    A change lands on the main line once its checks pass.

  2. Build

    One image is built from that exact commit, and only that image ships.

  3. Staging

    It runs on staging first, a copy of production.

  4. Checks

    Health checks and smoke tests must pass before it goes any further.

  5. Production

    It takes over from the old version while connections drain, so nobody is cut off.

  6. Watched

    Metrics and alerts watch it, and a bad release is rolled back.

Every stage passed: the release is live, and nobody was cut off.

What we run

What runs on it

KOL Blaster, CampusGains and this site, each released the same way.

Next: how we work

A small studio, end to end.