AI Agent Platformfor SRE
Specialized AI agents for SRE. Deep investigation by default — read-only, open source.
How It Works
Investigate, learn, repeat
A continuous loop that gets smarter with every incident
Describe
Tell Siclaw what's wrong — any channel
Investigate
4-phase engine: collect, hypothesize, validate in parallel, conclude
Learn
Every investigation feeds memory — next time is smarter
Report
Structured root cause with evidence and confidence scores
Describe
Tell Siclaw what's wrong — any channel
Investigate
4-phase engine: collect, hypothesize, validate in parallel, conclude
Report
Structured root cause with evidence and confidence scores
Learn
Every investigation feeds memory — next time is smarter
Multi-agent
One workspace, many specialists
Each agent owns a domain — Kubernetes, networking, system. Its own scope, skills, knowledge, and memory. They collaborate in Deep Investigation mode to solve issues that span layers.
k8s-agent
Kubernetes domain
Investigates pods, deployments, and cluster events.
Scoped to
network-agent
Networking domain
Traces latency, packet loss, DNS and routing issues.
Scoped to
system-agent
System / OS domain
Inspects CPU, memory, disk, and kernel-level faults.
Scoped to
Isolated by default, collaborative on demand. A pod restart in k8s-agent can hand off to network-agent for latency checks, then to system-agent for kernel signals — one investigation, three specialists.
Capabilities
Built for production
Multi-Agent Workspace
Specialized agents per domain. Each has its own scope, skills, knowledge, and memory.
Skill System
Per-agent diagnostic scripts with mandatory review. Fork and share across teams.
Knowledge Library
Per-agent wiki of runbooks and docs. Each specialist reads only what its domain needs.
Security First
Read-only investigation by default, with controlled execution when needed.
Alert-Driven Channels
Connect Siclaw to team channels and trigger investigations from alerts or operator input.
Cron Patrols
Schedule health checks in natural language. "Check GPU every 6h" just works.
Integrations
Connects to your stack
Built-in channels and Kubernetes. Extend to anything via Model Context Protocol.
Get Started