ChronOps is the war-room layer that sits beside your ITSM. It won't replace your ticketing system — and it won't replace your people. It removes the busywork around a live incident so your experts can understand faster, resolve sooner, and improve every time.
We're in active development and heading to market soon. Join the early-access list to shape it and get in first.
Semi-automation, by design. The expert stays in command — ChronOps does the drafting, timing, and comms.
Chasing on-call numbers. Copy-pasting updates into three places. Reconstructing the timeline afterward from memory and Slack or MS Teams scrollback. The tooling that's meant to help mostly gets in the way.
ChronOps is built around the real shape of incident work — not a ticket state machine. Understand what's happening, resolve it with the right people and clean comms, then close the loop so the next one is shorter.
Attach the incident to the affected services and ChronOps surfaces the SLA, the support teams, the escalation chain and who's on-call — scoped to this incident.
Draft once. ChronOps maps incident data into a short SMS and a branded, bulletproof email, sends to a reviewed recipient list, and publishes to the public status page.
At hand-over, ChronOps generates the Post-Incident Report and opens a numbered RCA record — the narrative pre-filled, the metrics computed, ready for your Problem Manager and your ITSM.
The foundation is real and working today — authentication, the service catalogue, communications, scheduling and automated post-incident reporting. We're finishing the live incident workspace now, with Change Management next to complete the ITIL triangle.
Auth & roles, service catalogue with SLAs, teams, contacts & vendors, public status page.
SMS + email + status comms, on-call scheduling, and automated PIR / RCA generation with AI drafting.
The live incident editor UI and notification dispatch — the operator's command surface during an incident.
Structured root-cause analysis — resolved incidents hand over to tracked problem records with a pre-filled PIR.
Completing the Incident → Problem → Change triangle, plus deeper ITSM ticket pairing.
Early-access partners help prioritise this order — the roadmap is a direction, not a promise of dates.
The capabilities below are built and working in the current development build.
One people directory. Teams and third-party vendors with per-severity notification rules and ordered escalation.
Shift, on-call and holiday codes with regional bank-holiday handling. Answers "who do I call" in one glance.
A projected, cache-served board that shows stakeholders what's happening — and never leaks internal data.
Timeline, updates, escalations, engagements and evidence are write-once. The record is defensible by construction.
A dual-auth /api/v1 with an OpenAPI contract — connect Teams, Power BI, scripts or your ITSM.
Role-based access with lockout and password policy, designed for AD / LDAP / OIDC single sign-on.
ChronOps doesn't ask you to migrate off ServiceNow, Remedy or Jira. It runs the live incident, then pairs the resulting RCA record back to your ITSM Problem ticket — so your system of record stays your system of record.
ServiceNow, Remedy, Jira SM — wherever incidents are logged today. Nothing changes here.
Comms, escalation, on-call, timeline and the auto-generated PIR — the whole live response, in one workspace.
The numbered RCA record pairs to your Problem ticket. Reporting flows to Power BI. Nothing is lost.
We're finalising pricing with our early-access partners. The shape is set — a predictable base, an included allowance for AI and evidence storage, transparent overage, and the option to bring your own AI provider. The numbers are still being confirmed.
Runs inside your network. Your data, your disk, your model. Built for security-conscious IT functions and MSPs.
Fully hosted and managed. Nothing to run. Includes a monthly AI and storage allowance sized for normal use.
ChronOps uses AI to draft post-incident narratives — a human always approves before anything is saved, and every draft is logged. You choose who pays for it: use ChronOps-hosted AI and consume from your included monthly allowance (overage billed per draft), or connect your own AI provider and pay us only the platform fee. Evidence — images, logs, documents attached to incidents — counts toward an included storage tier on SaaS; on-premises it lives on your own disk and isn't metered at all.
Join the early-access list to get a first walkthrough, help shape the roadmap, and lock in founding pricing. We'll only email you about ChronOps.
Prefer to talk? Add your email and note "on-prem" — we'll reach out about a pilot.