Teams

Shift Scheduling for 24/7 SOC & NOC Ops Teams

SOC Rotate is shift-scheduling software for 24/7 Security and Network Operations Centres: tiered coverage, rest rules, a fairness ledger and shift handover.

Security operations is where every feature came from. The shift model underneath it, with tiers, a night watch, a handover and coverage someone has to prove, is the one a NOC runs too. See what the product does →

SOCs

SOC shift scheduling, built here first.

MSSP or in-house, one office or a follow-the-sun chain: this is the rotation the product was designed around, and every screen assumes a SOC floor.

  • Tiered coverage per shift, such as two T2 and one T1 on nights, enforced by the schedule rather than written in a runbook.
  • For an MSSP, clients are first-class: each carries its SLA target, the offices serving it, and a report link the client can open.
  • Handover notes carry open incidents, live hunts and escalations between shifts, and between offices.
  • Working-time policy by jurisdiction (UK, EU, US, Australia, or your own limits) is the floor under every roster.

Read the SOC page →

NOCs

NOC shift scheduling on the same 24/7 rotation.

A NOC runs the shift model a SOC does: tiers, a night watch, a handover, and an SLA someone has to prove was met.

  • Coverage counted per tier per shift, so the escalation path is staffed on nights and weekends rather than on paper.
  • Rule mode or a repeating pattern to build the roster, leave and swaps arrive with the rest check already done.
  • A fairness ledger for nights, weekends and holidays that every engineer can take apart.
  • Handover that names the open incident and who owns it before anyone logs off.

Read the NOC page →

FAQ

Common questions.

Have something specific to your floor? Speak to sales.

Is SOC Rotate only for security operations teams?
No. It was built for SOCs and every screen assumes one, but the shift model underneath it (tiers, a night watch, a handover, coverage someone has to prove) is the one a NOC runs too. Nothing in the product is switched off for a NOC.
What size of team is it for?
A 24/7 team of four is rostered on a whiteboard; the product earns its place once there are enough people that the rotation, the fairness and the cover for leave stop fitting in one head.
We run one team across several offices. Does that work?
Yes. Each office keeps its own time zone, holidays and people, and a client served by several offices is a chain whose combined coverage is measured as one picture. Hand-off gaps show before you save and are swept nightly.
Do you integrate with PagerDuty, Opsgenie or ServiceNow?
Not yet. Notifications reach people in the app, by email, or by Slack webhook, and there is no public API today. Tell us which one matters to you; it informs what gets built next.
Is there a free trial or self-serve sign-up?
There is a 30-day trial, after a demo rather than a sign-up form. You get your own account with the rotation built on your own structure, and if you decide to go ahead, onboarding starts from there.
Running a rotation already?

See it on your own rotation, not a demo tenant.

Tell us how your floor is structured: shifts, tiers, offices, who never rotates. We'll build the rotation, walk through where coverage and fairness land, and answer the questions a generalist scheduling tool can't.

Book a demo →
  • RotationA month of 24/7 coverage in one action.
  • CoverageEvery gap flagged before it reaches a client.
  • ComplianceEvery change logged, every override on record.