OpenObserve Enterprise Self-Hosted

Self-hosted observability platform for ingesting, searching and analyzing logs, metrics and traces.

15 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 Enterprise Helm chart and CloudNativePG operator, then configure the cluster, object storage and application settings for the selected provider.

  2. Operated by

    Your team

    The customer runs the cluster, configures storage credentials and ingestion endpoints, sizes components, manages backups and retention, and applies chart and application upgrades.

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.

    OpenObserve Enterprise 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.

    OpenObserve Enterprise 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.

    OpenObserve Enterprise on Google GKE ↗ · 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 Enterprise Helm chart and CloudNativePG operator, then configure the cluster, object storage and application settings for the selected provider.
InfrastructureServers / containers
Application services and dependencies run in Kubernetes. The provider-specific examples use object storage and persistent PostgreSQL and NATS workloads.
Licensing modelCommercial Only
The reviewed Enterprise build is proprietary under the vendor EULA. The separate open-source distribution uses AGPL-3.0.
LicenseEnterprise End User License Agreement. The vendor publishes a free tier through 50 GB/day of ingestion, with a license required above that threshold.

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%) · 5 documented · 7 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.

OpenObserve Enterprise Self-Hosted: 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.

OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

Single sign-on
AvailableEvidence and scope for Single sign-on

Enterprise supports SSO through Dex with external identity providers. Configure the Dex client, redirect/callback URLs and provider connector; the EKS guide enables Dex explicitly. The feature is not available in the separate OSS edition.

Configured self-hosted Enterprise authentication and licensed features · Source ↗ · Reviewed 2026-11-20

Documented · 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.

OpenObserve Enterprise Self-Hosted: 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.

OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

Enterprise documentation describes OpenFGA-based RBAC, Dex SSO and configurable secure authentication cookies. The cloud guides scope storage credentials through provider IAM. Operators must configure these controls and review telemetry, external connectors and optional AI/reporting services.

Configurable Enterprise controls, not an independent deployment attestation · Source ↗ · Enterprise access-control features ↗ · Configuration and telemetry opt-out ↗ · 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.

OpenObserve Enterprise Self-Hosted: 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 Enterprise-capable Helm package is openobserve 1.1.7. Its values pin the Enterprise image to v1.1.2; chart, application, report-server and optional AI images have separate versions. Install CloudNativePG and provider storage prerequisites separately.

Helm package and Enterprise image settings; not a complete production approval · Source ↗ · Deployment artifact ↗ (openobserve 1.1.7; Enterprise image v1.1.2; sha256:394886d2c521acfc25012190d99c788814bf0a6f944674febd993ec8be40abe2) · Published chart index ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

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

The vendor-linked EKS example provisions three m7i.xlarge nodes, with desired/minimum count 3 and maximum 6, alongside a managed EKS control plane. PostgreSQL, NATS, storage and enabled application roles also require sizing. This example is not a universal minimum or a measured fit for 100 users/1 TB. The linked EKS cluster example pins Kubernetes 1.30, which is absent from AWS’s currently available EKS versions; select an available version compatible with the application before using the example.

Reviewed AWS example, not a production workload benchmark · Source ↗ · EKS example node configuration ↗ · Capacity planning inputs ↗ · Current EKS version availability and lifecycle ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The Enterprise EULA and licensing guide describe a free tier up to 50 GB/day of ingestion, with registration/licensing above that level and feature-specific entitlements. The guide permits three monthly over-limit occurrences before restricting search. Infrastructure, operating labor and support are separate.

Enterprise software entitlement and documented usage limits, not cloud operating cost · Source ↗ · Enterprise EULA ↗ · 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.

OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

Release snapshot / cadence
Not confirmedEvidence and scope for Release snapshot / cadence

Chart 1.1.7 pins o2cr.ai/openobserve/openobserve-enterprise:v1.1.2. This establishes a reviewed deployable image reference, but not its publication timestamp, a current Enterprise release/support designation or parity with public OSS/prerelease tags. Request the applicable Enterprise release notes and compatibility matrix.

Partial Enterprise package/image evidence; application publication and supported bundle unresolved · Source ↗ · Inspected Enterprise-capable chart ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

Scope & considerations

The documented paths cover Enterprise Edition. Feature access depends on the enterprise entitlement. OpenObserve documents outbound product usage reporting and a ZO_TELEMETRY opt-out. Plan for separate recovery of telemetry objects and PostgreSQL metadata. The reviewed chart 1.1.7 pins Enterprise image v1.1.2; do not substitute an OSS or release-candidate tag by name alone. Dex is optional and must be configured. The EKS node example is a sizing starting point, not an HA workload benchmark. The linked EKS cluster example pins Kubernetes 1.30, which is absent from AWS’s currently available EKS versions; select an available version compatible with the application before using the example.

Category fit

Observability
Collects and analyzes application and infrastructure telemetry, with dashboards and alerts for operational monitoring.

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
  • Coroot Community EditionSelf-hosted application observability with service maps, logs, metrics, traces and continuous profiling.
    • AWS
    • Azure
    • Google Cloud
    • Oracle 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

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.

    • OpenObserve Enterprise on Amazon EKS ↗ · AWS

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

      The vendor walkthrough deploys the Enterprise application to the customer's EKS cluster, with S3 for telemetry and IAM permissions for storage access. The linked cluster sample pins Kubernetes 1.30; verify AWS availability and application compatibility and update that example version before use.

    • OpenObserve Enterprise on Azure AKS ↗ · Azure

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

      The vendor walkthrough deploys the Enterprise application to the customer's AKS cluster, with Azure Blob Storage, CloudNativePG and clustered NATS.

    • OpenObserve Enterprise 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 walkthrough deploys the Enterprise application to a Standard GKE cluster in the customer's Google Cloud project. The documented Cloud Storage configuration uses S3 interoperability and HMAC credentials.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory