EKOS Search workspace

Find the source. Ask with citations.

A research workspace over your governed document estate: policies, procedures, standards, regulations, and evidence. Two modes, one rule: the source is always within reach.

Ranked source passagesCited synthesisMCP for your agents
Two research modes

Direct Search is not Ask EKOS. That is the point.

Sometimes the wording is the work. Sometimes you need understanding fast. EKOS keeps the two modes distinct so you always know what you are reading.

Living Document Dossiers

Every result opens into a governed record.

Search does not end at a snippet. Each document is a living dossier: current and historical versions, processing state, sensitivity, controlled tags, reviewed relationships, and the impact work attached to it.

Scope any search or conversation with corpora and controlled tags, so research runs against the right body of knowledge instead of the whole enterprise estate.

DOSSIER / DOC-2841v3 current

Access Control Policy

Security Policies corpus · classified: internal

  1. v1 2025-11-02
  2. v2 2026-03-14
  3. v3 2026-07-02 · current
receivedextractedclassifiedindexedgraph analysis

Account Provisioning Procedure

implements · approved relationship

Q2 Access Review Export

evidences · cites v3 language

Illustrative product view · versions, processing state, and related records
MCP compatible

Bring your own agents. Keep one source of truth.

EKOS Search is exposed over the Model Context Protocol as well as REST. Your assistants and internal agents call tools like search_knowledge and rag_query through tenant-bound service accounts, and get back the same visibility-scoped passages and cited answers your people see.

Identity comes from the authenticated connection, never from a model-written argument, so an agent cannot talk its way into another tenant.

MACHINE ACCESS / SVC-0042Token active

svc-audit-assistant

active

ekos_sa_9f31… shown once · stored as hash only

expires in 90 daysrevocable per tokentenant bound

Your agent, over authenticated MCP

› search_knowledge("data retention schedule")

‹ 5 source passages, visibility-scoped, with citations

# tenant derived from the connection, tool arguments cannot change it

The same governed layer answers your assistants: bring your own agents over MCP, keep EKOS as the source of cited truth.

Illustrative product view · a scoped machine identity and one MCP call
Next step

Ask your hardest policy question, live.

Bring a real document set and a question your team argues about. We will show both modes, the citations, and the refusal behavior.