coroot.com valid

Coroot

Coroot is an open-source observability platform. It uses eBPF to collect metrics, logs, traces, and profiles with zero code changes, and applies AI-powered root cause analysis to explain what broke and why.

For agents: Open-source eBPF observability platform with metrics, logs, traces, profiling and AI root cause analysis, with installation docs and pricing.

observabilityebpfdistributed tracingroot cause analysisopen source monitoring

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T11:51:30.914Z. Cached copy · Source on coroot.com

# Coroot

> Coroot is an open-source observability platform. It uses eBPF to collect metrics, logs, traces, and profiles with zero code changes, and applies AI-powered root cause analysis to explain what broke and why.

Coroot is self-hosted: telemetry stays on your own infrastructure, including air-gapped environments. It runs on Kubernetes and on plain VMs, ingests OpenTelemetry over OTLP, and stores data in ClickHouse and Prometheus. The Community edition is free and open source (Apache 2.0); the Enterprise edition adds AI root cause analysis, SSO, RBAC, and support, priced per CPU core with no charge for data volume.

## Start here

- [Coroot](https://coroot.com/): eBPF-powered, AI-guided observability with no code changes.
- [Product overview](https://coroot.com/overview): The full feature set — zero-instrumentation monitoring, distributed tracing, logs, continuous profiling, cloud cost insights, risk detection, and AI root cause analysis.
- [Documentation](https://docs.coroot.com/): Installation, configuration, and operation guides.
- [Source code](https://github.com/coroot/coroot): The Coroot repository on GitHub.
- [Pricing](https://coroot.com/pricing): $1 per CPU core with scale discounts, and no data-volume fees.
- [Editions](https://coroot.com/editions): What the free Community edition includes versus Enterprise.

## Capabilities

- [eBPF observability](https://coroot.com/ebpf): Automatic service maps, CPU profiling, and golden-signal SLIs for every service, with no instrumentation.
- [AI root cause analysis](https://coroot.com/ai): Correlates every telemetry signal to identify the cause of an incident, with the supporting evidence shown.
- [Agentic-ready observability](https://coroot.com/agentic-observability): Read-only, RBAC-enforced access to live topology and historical telemetry for any MCP-compatible AI client.
- [OpenTelemetry](https://coroot.com/opentelemetry): OTLP ingestion, trace storage in ClickHouse with optional S3, latency/error heatmaps, and flamegraphs.
- [Continuous profiling](https://coroot.com/continuous-profiling): Always-on eBPF CPU profiling for any language, Go heap profiling, and async-profiler for Java.
- [Kubernetes](https://coroot.com/kubernetes): Zero-code cluster monitoring, log correlation, network monitoring, and cost insights.
- [GitOps](https://coroot.com/gitops): Argo CD and Flux sync status, drift detection, and deployment-to-impact correlation.

## Database observability

- [PostgreSQL](https://coroot.com/postgres): Query performance, replication, backups, autovacuum, bloat, and wraparound, across Kubernetes, RDS, Aurora, and Cloud SQL.
- [MySQL](https://coroot.com/mysql): Query performance, locks and deadlocks, InnoDB internals, replication, Galera, and binary log growth.
- [MongoDB](https://coroot.com/mongodb): Query performance, replication and oplog, WiredTiger internals, connections, and fragmentation.

## Comparisons

- [Self-hosted Datadog alternative](https://coroot.com/datadog-alternative)
…

Related sites

Other listed sites in DevOps and observability. See the whole category →

Machine-readable: GET /v1/resolve?q=coroot.com · GET /v1/domain/coroot.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for coroot.com:
1. POST https://agentwebmap.com/v1/sites/coroot.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://coroot.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/coroot.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/coroot.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.