🚀 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

EDDI Integrations

Channels, identity, agent protocols, enterprise systems, vector stores and infrastructure. Every page shows what you get, how it works in EDDI, the real configuration, and how the integration is governed: approvals, the audit ledger and the secrets vault.

ChannelsEvents API

Slack

Governed AI agents in Slack: mentions, direct messages, threads, group discussions streamed into a thread, and Block Kit approval cards with Approve and Reject buttons.

Channels/v1

Open WebUI

EDDI serves an OpenAI-compatible /v1 API that presents deployed agents as models, so Open WebUI, the OpenAI SDKs, LangChain and LiteLLM can talk to them.

ChannelsReact + SSE

Web chat

A themeable React chat UI served by EDDI itself, with streaming responses, Markdown, quick replies and undo, that you can open directly or embed in a page.

Identity and securityOIDC

Keycloak / OIDC

Put OpenID Connect authentication in front of EDDI with Keycloak or another OIDC provider, with roles for admins, editors, users, viewers and approvers.

Identity and security${vault:}

Secrets Vault

A built-in, envelope-encrypted secrets vault. Configuration references secrets as ${vault:keyName}, and the value never lands in agent configs, exports or logs.

Agent protocolsStreamable HTTP

MCP Server

Control EDDI from Claude Desktop, Cursor, VS Code and other MCP clients. EDDI exposes 84 MCP tools over Streamable HTTP for conversations and administration.

Agent protocolsmcpcalls

MCP Client

Give EDDI agents the tools of external MCP servers. A server's tools become the agent's tools, behind the same approval gates and audit trail as every other tool.

Agent protocolsJSON-RPC 2.0

A2A

Expose EDDI agents to other agents through Agent Cards and JSON-RPC, and use remote A2A agents as tools inside your own agents.

Enterprise systemsOpenAPI 3.0 / 3.1

OpenAPI

Turn any REST API with an OpenAPI 3.0 or 3.1 description into an agent with tools, without writing code, and gate the consequential calls behind human approval.

Enterprise systemsOData / REST

SAP

EDDI has no native SAP connector. You reach SAP through its OData and REST APIs with OpenAPI import or HTTP calls, or through an MCP server, under approvals and the audit ledger.

Data and RAGstoreType: chroma

Chroma

Chroma as the vector store for an EDDI knowledge base. The lowest-friction option when you have no existing infrastructure to reuse.

Data and RAGstoreType: pgvector

pgvector

PostgreSQL with pgvector as the vector store for an EDDI knowledge base. The recommended persistent choice when you already run PostgreSQL.

Data and RAGstoreType: qdrant

Qdrant

Qdrant as the vector store for an EDDI knowledge base, a purpose-built vector database with room to grow.

Data and RAGstoreType: elasticsearch

Elasticsearch

Elasticsearch as the vector store for an EDDI knowledge base, useful when you already run it and want keyword and vector search in one place.

Data and RAGstoreType: mongodb-atlas

MongoDB Atlas Vector Search

MongoDB Atlas Vector Search as the vector store for an EDDI knowledge base, a natural fit if you already run on Atlas.

Infrastructurek8s / Helm / Kustomize

Kubernetes and Helm

Run EDDI on any conformant Kubernetes cluster with a single-file quickstart, a Helm chart or Kustomize overlays, with MongoDB or PostgreSQL.

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.

Infrastructuretype: ollama

Ollama

Run models locally with Ollama and keep prompts and documents on your own hardware, for on-premises and air-gapped setups.

Do not see your system?

Describe it to us or start from the OpenAPI route. If it has an API, an agent can call it, with approvals and an audit trail.

Get started