marp: true theme: warble-design-system class: lead
The Warble Blueprint
A Reference Architecture for Autonomous Operations
Stop renting black boxes. Own your operational journey.
Why a Blueprint?
- The Problem: Modern "AIOps" platforms are proprietary black boxes. You rent their intelligence, lose control of your telemetry, and get locked into their pricing models.
- The Solution: An open-core, self-healing infrastructure architecture that you can read, fork, and run entirely inside your own VPC.
The Three Pillars of Autonomy
- Perceive: Ingest OpenTelemetry traces, logs, and metrics. We don't force proprietary collectors. Your existing OTel pipeline is the data plane.
- Reason: An LLM grounded by RAG over Postgres + pgvector. It retrieves prior incident patterns and proposes a remediation plan.
- Act: Execution via OpenTofu (infra) and Knative (workload), securely gated by OPA policy.
SRE Watchmens: Human-in-the-Loop
- Propose-Critic Loop (Reflexion): Every remediation plan must cite at least one retrieved precedent. The "Critic" agent rejects ungrounded plans before they ever reach the policy gate.
- Custom Guardrails: You define the boundaries. Every action is reversible, audited, and strictly governed by your custom playbooks.
Adapt Opensource: Zero Rip-and-Replace
- Integrates natively with Datadog, Prometheus, Honeycomb, and Grafana.
- You provide the data. We provide the action.
- Build your own LLM trained exclusively on your incident data and your monitoring tools.
The Results
- 77% Faster MTTR: Rapid, AI-assisted root cause analysis and remediation.
- 95% Lower Cost: Compared to proprietary AIOps. You bring the compute and the LLM; we provide the orchestration.
- Zero Vendor Egress: Your incident memory and telemetry never leave your VPC.
Get the Blueprint
Access the open architecture, fork the codebase, and start your journey.
github.com/warble-tech/warble-oss