Skip to content

OpenRemedy

Autonomous SRE platform for Linux fleets — alerts in, classification, diagnosis, gated remediation, audit.

OpenRemedy watches every server continuously and, when something is detected, classifies, decides, and either fixes or escalates. The riskier the fix, the more human approval it needs. Every step is logged.

This site is the operator-facing reference documentation. For the high-level pitch and design philosophy, see the whitepaper.

Get started

The shortest path from zero to a running install:

  1. Installation — requirements, prerequisites, DNS, secrets, smoke test.
  2. Configuration — every environment variable the platform reads, what to override and when.
  3. Architecture — read this once so the rest of the docs make sense in context.

Concepts

The mental model the rest of the docs assume.

  • Architecture — the shape of the system: components, data flows, the agent pipeline.
  • Server modes — live / shadow / audit, the coarsest control over what the platform is allowed to do per server.
  • Security — auth, encryption, HMAC webhooks, rate limits, the trust × risk gate, sandboxes for custom tools.
  • Privacy — exactly what telemetry sends, what it does not, and how to disable it.

Operating

Day-to-day: how to use what's installed.

  • Proactive monitoring — how policy-driven checks become incidents, and how the IncidentWatcher re-invokes agents on operator comments.
  • Integrations — webhooks, outbound notifications, plugins, the API surface for programmatic clients.
  • Recipes — what a recipe is and how to author one.
  • Maintenance plans — the markdown DSL, strategies, the AI editor.
  • Daemon — install + configure the host-side openremedy-client agent.

Dashboard reference

A walkthrough of every page in the operator UI lives under Dashboard reference.

Source

OpenRemedy is licensed under the Functional Source License, version 1.1, Apache 2.0 Future License (FSL-1.1-ALv2). Source lives at github.com/OpenRemedy.