Roadmap

Where we're headed.

Overwatch is built in the open. Here's what's coming next — deeper integrations, AI-powered analysis, and support for the infrastructure you actually run.

In Development

Planned

Self-Hosted Workers

In Development

Run checks against internal hosts in private network environments. Deploy lightweight worker agents behind your firewall — they require outbound connections only, so no inbound ports or VPN tunnels needed.

▸Outbound-only connectivity — no firewall holes required
▸Monitor internal services, databases, and APIs
▸Encrypted communication with Overwatch control plane
▸Deploy via Docker, systemd, or Kubernetes DaemonSet
▸Auto-registration and health reporting

┌─────────────────────────────┐
│  PRIVATE NETWORK            │
│  ┌───────┐    ┌───────┐     │
│  │ svc-a │    │ db-01 │     │
│  └───┬───┘    └───┬───┘     │
│      └──────┬─────┘         │
│         ┌───┴───┐           │
│         │WORKER │ ──── outbound ────▶ ▲ OVERWATCH
│         └───────┘           │
└─────────────────────────────┘

OpenTelemetry Ingest

Planned

Ship logs, metrics, and traces from your infrastructure or application directly to Overwatch using the OpenTelemetry standard. Correlate check results with application-level telemetry for full-stack visibility.

▸Native OTLP/gRPC and OTLP/HTTP endpoints
▸Logs, metrics, and traces in a unified timeline
▸Correlate check failures with application errors
▸Compatible with any OTEL SDK or collector
▸Configurable retention and sampling policies

  app ──▶ OTLP ──┐
                  │
  infra ──▶ OTLP ──┼──▶ ▲ OVERWATCH ──▶ correlate
                  │
  k8s ──▶ OTLP ──┘

MCP & AI-First Root-Cause Analysis

Planned

Tie errors and performance issues back to changes in your environment. Ask for root cause in natural language and get a comprehensive view of your stack — where it's breaking down, with service mapping and a query builder.

▸Natural-language root-cause queries via MCP
▸Automatic service dependency mapping
▸Visual query builder for cross-signal investigation
▸Correlate deployments, config changes, and incidents
▸Actionable remediation suggestions

  ┌──────────────────────────────┐
  │  "Why is checkout slow?"     │
  └──────────┬───────────────────┘
             ▼
  ┌──────────────────────────────┐
  │ ▲ OVERWATCH MCP              │
  │  deploy@14:02 ──▶ db p95 ↑   │
  │  svc-payment ──▶ timeout     │
  │  root: connection pool sat.  │
  └──────────────────────────────┘

Windows WMI & VMware Metrics

Planned

Export metrics from Windows WMI, VMware vSphere, and other enterprise infrastructure to Overwatch for continuous monitoring, analysis, and alerting. Bridge traditional infrastructure into your modern observability stack.

▸Windows performance counters via WMI
▸VMware vSphere / ESXi host and VM metrics
▸CPU, memory, disk, network — out of the box
▸Custom metric collectors with plugin API
▸Threshold-based alerting and trend analysis

  ┌─────────┐  ┌─────────┐
  │ WINDOWS │  │ VMWARE  │
  │   WMI   │  │ vSphere │
  └────┬────┘  └────┬────┘
       └──────┬─────┘
              ▼
      ▲ OVERWATCH
    metrics · alerts · trends

  ┌───────────────────────────────────────┐
  │                                       │
  │   Ship with us. Build with us.        │
  │                                       │
  └───────────────────────────────────────┘

— Ship with us. Build with us. —

Want to shape what's next?

We build in the open and prioritize based on real feedback. Tell us what matters most to your team.

Share feedback →Follow on GitHub