What's Next for Leoric Watch

The direction is alert to evidence to action

Leoric Watch is being built around a simple sequence. A monitor detects an external problem. The team needs evidence that helps it understand what changed. Then the agency or operations team needs to communicate clearly with the people affected.

The next phase of the product is about tightening that sequence. We want the distance between an alert and a useful next step to keep getting smaller.

That does not mean adding automation for its own sake. It means making the information around an incident easier to find, easier to trust, and easier to act on.

More useful incident context

External checks are a valuable first signal, but they do not describe the full state of a system. The work ahead for AI Diagnosis is focused on improving the connection between that outward symptom and the operational evidence around it.

That includes expanding and refining the evidence we can bring together from connected services, making the diagnosis easier to inspect, and keeping the reasoning grounded in observable events rather than vague summaries.

The standard is straightforward: when someone opens an incident, the product should help them identify the next investigation step faster than they could by starting with a blank browser tab.

Better workflows for agencies

Agencies need to manage reliability across multiple clients without turning monitoring into a separate, manual routine for every site. We are continuing to improve the workflows that make that possible: monitor organization, practical alerts, status-page profiles, custom domains, and clearer operational history.

The product should work for the person checking a single client site and for the agency that needs to keep a broader service portfolio in view. That requires a useful balance between detail and clarity.

We are also focused on making public communication more deliberate. A status page should be quick to publish, credible to clients, and easy to maintain as an incident changes.

Reliability is a habit, not a report

Monitoring data is most valuable when it helps teams build better habits. That might mean noticing a recurring failure pattern, improving a handoff after an alert, or giving clients clearer expectations during maintenance.

Leoric Watch will keep investing in the parts of the product that support those habits: useful history, practical notifications, evidence-driven diagnosis, and client-facing communication that feels owned rather than borrowed.

Keep the feedback close

The roadmap will stay tied to the problems teams encounter when they are responsible for real services. The most useful feedback is specific: what did you need to know during an incident, what took too long to find, and what did your client need to hear?

We will keep sharing product updates and practical monitoring lessons here as the product develops.

Start monitoring with Leoric Watch and see where the workflow can become clearer for your team.