🚀 EDDI 6.5.0

19 LLM providers, knowledge bases that crawl your site and read your files, and conversations that follow compatible agent versionsWhat's new

Managed Cloud Get Started
All integrations
InfrastructureUBI 10 / Operator

Red Hat OpenShift

EDDI ships a Red Hat certified container image built on UBI 10 that runs non-root on OpenShift 4.12 or newer, plus an Operator for OperatorHub.

ConfigurationDocs ↗

What you get

  • A Red Hat certified image, listed in the Red Hat Ecosystem Catalog
  • Non-root execution as UID 185 on a UBI 10 base with OpenJDK 25
  • An Operator that creates an EDDI instance and a route from a custom resource
  • Certification checked in CI with Red Hat preflight

How it works in EDDI

  1. On OpenShift 4.12 or newer, open OperatorHub and install the EDDI Operator.
  2. Create an Eddi instance from Installed Operators, with the size and storage for MongoDB.
  3. The Operator creates the route automatically.
  4. Add authentication and secrets as you would on any cluster.

Configuration

Taken from the EDDI documentation. Placeholders such as your-agent-id are yours to replace.

Eddi custom resource (OperatorHub operator)An Eddi custom resource from the docs.
apiVersion: labs.ai/v1alpha1
kind: Eddi
metadata:
  name: eddi
spec:
  size: 1
  mongodb:
    environment: prod
    storageclass_name: managed-nfs-storage
    storage_size: 20G

Governance

  • The container runs as a non-root user, and the image carries third-party license files.
  • Releases are checked against Red Hat certification requirements in CI.
  • Production start still requires OIDC unless you opt out explicitly.

Good to know

  • The Operator is being updated for EDDI 6 to support both MongoDB and PostgreSQL. The generic Kubernetes route works on any conformant cluster.
  • A RHEL 8 host is not supported for the UBI 10 image. RHEL 9 or newer is.
Get startedDocs ↗

Need it built and run for you?

EDDI Solutions builds and maintains connectors, runs EDDI as a managed or co-operated instance, and supports you in your own cloud or on-premises.

Talk to EDDI Solutions ↗

Related integrations

InfrastructureKubernetes and HelmRun EDDI on any conformant Kubernetes cluster with a single-file quickstart, a Helm chart or Kustomize overlays, with MongoDB or PostgreSQL.Identity and securitySecrets VaultA built-in, envelope-encrypted secrets vault. Configuration references secrets as ${vault:keyName}, and the value never lands in agent configs, exports or logs.Identity and securityKeycloak / OIDCPut OpenID Connect authentication in front of EDDI with Keycloak or another OIDC provider, with roles for admins, editors, users, viewers and approvers.

Configuration and behavior on this page follow the EDDI documentation, checked on 2026-10-14. Field names and defaults can change between releases, so confirm them in the docs for your version.