Coroot Community Edition

Self-hosted application observability with service maps, logs, metrics, traces and continuous profiling.

14 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Install the Coroot Operator and Community Edition Helm chart on the customer's Kubernetes cluster.

  2. Operated by

    Your team

    The customer manages the operator, image versions, privileged node-agent permissions, storage capacity, telemetry retention, backup and recovery, and access to the UI.

Deployment boundaries by provider
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Coroot on Amazon EKS ↗ · Source checked 2026-11-20

  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Coroot on Azure AKS ↗ · Source checked 2026-11-20

  • Google Cloud: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Coroot on Google GKE ↗ · Source checked 2026-11-20

  • Oracle Cloud: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Coroot on Oracle OKE ↗ · Source checked 2026-11-20

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodInstall the Coroot Operator and Community Edition Helm chart on the customer's Kubernetes cluster.
InfrastructureServers / containers
Coroot and its agents run as Kubernetes workloads. Cluster node agents use eBPF and require compatible Linux kernels and privileged access.
Licensing modelOpen Source / Open Core
Apache-2.0 applies to the published Community code. The Kubernetes guide identifies the separate licensed Enterprise chart.
LicenseApache License 2.0 for Coroot Community Edition. Enterprise Edition has separate subscription terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

12 of 12 fields researched (100%) · 6 documented · 6 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Not confirmedEvidence and scope for Marketplace delivery

The reviewed edition and deployment sources do not establish an exact marketplace offer, seller and delivery artifact that entitle this edition. A vendor SaaS subscription or another edition is insufficient.

Coroot Community Edition: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility

No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately.

Coroot Community Edition: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

Single sign-on
Not availableEvidence and scope for Single sign-on

The authentication guide explicitly reserves native SAML/OIDC single sign-on for Coroot Enterprise. Community has local users with Admin, Editor and Viewer roles. An external authentication proxy would be a separate configuration, not native Community SSO.

Native Coroot Community authentication; Enterprise is a separate edition · Source ↗ · Reviewed 2026-11-20

Explicitly unsupported · Editor reviewed.

SCIM provisioning
Not confirmedEvidence and scope for SCIM provisioning

The reviewed sources do not establish a SCIM endpoint and supported user/group lifecycle for this edition. SSO and just-in-time account creation are not SCIM evidence.

Coroot Community Edition: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

Compliance attestations
Not confirmedEvidence and scope for Compliance attestations

No reviewed independent report establishes certification of this customer-operated deployment and its infrastructure. Publisher or SaaS attestations do not automatically cover the customer installation; obtain scope, validity and shared responsibilities.

Coroot Community Edition: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

Community provides local-user authentication, three predefined roles and API-key service accounts. Set the initial admin password before exposure and review anonymous-mode settings. Node agents need privileged eBPF/host access; review the operator ClusterRole and its optional restriction on global secret access.

Configured Community access controls and privileged collector/operator boundary · Source ↗ · Node-agent privilege requirements ↗ · Inspected operator permissions/configuration ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Air-gapped operation
Not confirmedEvidence and scope for Air-gapped operation

The reviewed sources do not establish a complete disconnected installation, update and licensing workflow. A telemetry opt-out alone does not establish air-gapped support; review registry, package, identity and optional external-service dependencies.

Coroot Community Edition: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

Deployment artifact / IaC
AvailableEvidence and scope for Deployment artifact / IaC

The inspected coroot-ce 0.3.3 chart creates a Community custom resource and requires a separately installed operator; the reviewed operator chart is 0.10.8 (operator application 1.10.8). Neither chart version identifies the Coroot server release. Pin server, node-agent and cluster-agent images to prevent the documented automatic upgrades.

Community custom resource plus separately versioned operator and component images · Source ↗ · Deployment artifact ↗ (coroot-ce 0.3.3; sha256:e6213b27a4e73924d2fe03c12aa815ebd8ec806436c3a5ab9bd4a8801c18e6f3; operator chart 0.10.8 / operator 1.10.8) · Operator package ↗ · Published chart index ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The inspected Community chart defaults to 10 GiB Coroot storage, 10 GiB Prometheus storage and 100 GiB per ClickHouse instance. Its default ClickHouse layout is one shard/replica; the installation guide overrides this to two shards and two replicas. Operator requests are 100m CPU/64 MiB. These are component defaults, not total cluster CPU/RAM minima or an HA capacity guarantee.

Chart-specific storage and operator request baseline; server/agent/database sizing remains workload-dependent · Source ↗ · Separate operator requests ↗ · Installation layout and replica override ↗ · Kernel and orchestrator prerequisites ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Coroot Community v1.29.4 is licensed under Apache-2.0. This establishes the software licence rather than a per-seat subscription; Enterprise features/support, dependencies and infrastructure have separate costs.

Upstream Community code; excludes Enterprise subscriptions · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate

No complete dated operating-cost estimate is established. The AWS us-east-1 baseline of 100 internal users, 1 TB stored data and HA still needs daily telemetry ingestion, retention, monitored infrastructure, query concurrency and commercial entitlements. Human user count does not size the telemetry backend.

Coroot Community Edition: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

The reviewed Coroot Community server snapshot is v1.29.4, published November 18, 2026. Operator, server, agents and charts are independently versioned; this snapshot does not guarantee support or pin the complete installation.

Upstream Community server release · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Scope & considerations

The node agent requires privileged access for eBPF and host inspection, and upstream describes AWS Fargate support as basic. Anonymous usage statistics are enabled by default and can be disabled. The operator updates unpinned Coroot component images automatically. Native SAML/OIDC SSO is Enterprise-only. The Coroot server v1.29.4, Community chart 0.3.3 and operator chart 0.10.8 are separate version tracks; inspect and pin each required image.

Community & maintenance

The upstream project has sustained public contributor history (including def, apetruhin, Split174) and a reviewed dated v1.29.4 release. This establishes maintenance/community participation rather than a production suitability, support or capacity guarantee.

Category fit

Observability
Node and cluster agents collect operational telemetry for application monitoring and troubleshooting.

Compare within Observability

  • AVEVA PI System (BYOL)Commercial industrial data collection, historian and visualization system with an AWS architecture.
    • AWS
    Customer-operated · Commercial Only
  • Cloud Carbon FootprintOpen-source cloud-usage, energy and carbon-estimation application.
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Datadog BYOC LogsDatadog log processing, indexing and storage in the customer's cloud, with search through Datadog Log Explorer.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · vendor control plane · Commercial Only
  • Elastic Cloud EnterpriseCommercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Elastic Cloud on KubernetesElastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Source Available
  • Grafana OSS Self-HostedSelf-hosted dashboards, visualization and alerting for operational data.
    • AWS
    Customer-operated · Open Source / Open Core
  • Langfuse Self-HostedSelf-hosted LLM observability, evaluations and prompt-management platform.
    • AWS
    • Azure
    • Google Cloud
    • Railway
    • Render
    Customer-operated · Open Source / Open Core
  • MLflow Tracking Server Self-HostedSelf-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core

Showing 8 of 20 other listings in Observability. These products address related workflows; read their category-fit notes before comparing scope. See all of Observability →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Coroot on Amazon EKS ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.

      The vendor explicitly names EKS as a supported Kubernetes environment. Use the linked Community Helm instructions to deploy the operator, server and agents. The vendor specifies basic support for Fargate.

    • Coroot on Azure AKS ↗ · Azure

      Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.

      The vendor explicitly names AKS among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster, subject to privileges and Linux requirements.

    • Coroot on Google GKE ↗ · Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.

      The vendor explicitly names GKE among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster.

    • Coroot on Oracle OKE ↗ · Oracle Cloud

      Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.

      The vendor explicitly names OKE among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory