Operating model · On Call

Reactit On Call.

The continuous-operations engagement. SLAs, monthly reviews, and the engineers who built the system on the rotation. For systems we built — or systems we adopted.

For when the pager has to be ours.
Operating model
01 · About this engagement

What "On Call" actually means.

Reactit On Call is the continuous-operations engagement that follows most Build engagements — and that we occasionally take on for systems we did not build.

A typical On Call arrangement covers a defined surface (one platform, one service, one practice) with a written SLA, a monthly review with the client’s operations leadership, and the same engineers who shipped the system on the on-call rotation.

We currently run On Call for eight production engagements worldwide. The smallest covers a single identity realm; the largest covers an institution’s entire core insurance stack.

02 · What’s in the engagement

The standard shape.

01 / 06

Defined surface

One platform, service or practice, written into the SLA.

02 / 06

Production SLA

Availability, latency, and incident response — measured and reported.

03 / 06

Monthly review

A 90-minute conversation with operations leadership, every month.

04 / 06

Shared rotation

Our engineers on the page rotation alongside yours.

05 / 06

Joint postmortems

Every incident reviewed jointly, written up, and shared back.

06 / 06

Exit on 60 days

Either party may end the engagement with two months notice.

We're selective about the engagements we take.

Talk to us