Kordane CortexPrivate knowledge, documents & speech

Put your knowledge to work.

Find the answer in your own information. Turn documents into structured data, search internal knowledge and make speech useful, with the source always close at hand.

Assist, Extract and Voice available in pilots · additional capabilities planned

Answers with a source.

Ask a question across approved knowledge. Open the material behind an answer and see where it came from.

Documents ready for work.

Extract the fields your workflow needs. Review the source, correct uncertain values and pass structured information to the next step.

More from every conversation.

Turn audio into searchable transcripts, speaker turns and useful summaries, inside an approved environment.

Assist / Extract / Voice

Three ways in.
A clearer view out.

Ask your knowledge. Structure your documents. Search your conversations. Explore each experience below.

Cortex Assist

Grounded answer with sources

A private knowledge base answers with evidence you can open and check.

Available in pilots
Cortex AssistPolicy: Private knowledge only

What was regional revenue in Q2?

Regional revenue for Q2 was €24.7 million, led by the northern region.

Q2 Operating Report · Example Holdings (fictional)

Page 14 · Regional performance

Highlighted evidence: Regional revenue: €24.7M (previous quarter: €22.8M). Northern region contributed 41% of the total.
  • Private environment model
  • Citation attached

Cortex Assist answers from approved private knowledge and returns evidence that can be reviewed.

Illustrative grounded answer · Synthetic data

Explore distributed retrieval and the product roadmap

Product roadmap

Cortex Governed Distributed Retrieval

PlannedPlanned architecture. Not implemented, and not available in pilots today.

Query approved private sources across multiple controlled environments. Retrieval remains local, while only policy-authorised evidence, excerpts, structured facts or local answers may return.

  1. Cortex receives a question

    An analyst or a workflow asks something that may need evidence held in more than one controlled environment.

  2. BoundSense determines which environments may participate

    The question itself is classified. BoundSense decides which nodes and sources are eligible, and what the query must look like before it travels.

  3. The query reaches approved nodes only

    An environment that was not authorised for this question never sees it.

  4. Retrieval executes locally

    Each node searches its own sources under its own access controls. Nothing is pooled into a central index to answer the question.

  5. Raw document collections remain in place

    The corpora themselves stay inside their approved environments, with their own retention and deletion rules.

    Source corpora contained locally

  6. Only policy-authorised evidence returns

    Excerpts, structured facts, a local answer, or a provenance reference: whichever the node’s policy permits, and nothing beyond it.

    Permitted to leaveExcerpts · structured facts · local answers · provenance references

  7. Cortex reconciles what came back

    Duplicate findings, contradictions between nodes, unavailable nodes and source provenance are resolved before anything is composed.

  8. The answer cites the evidence that supports it

    Each factual claim points to evidence that actually supports it, with its node and source provenance attached.

    Answer released with citations

  9. Missing required evidence produces a limitation or a refusal

    A required node that did not answer, or evidence too thin to carry the claim, is stated plainly rather than filled in.

    Required node unavailable · answer qualified

  10. BoundSense and Cortex evidence contribute to one record

    The query decision, node participation, citations and stated limitations are recorded together with the answer.

A roadmap preview of retrieval across approved private sources.

BoundSense-authorised nodesPlanned

The same control plane, placed in each customer-controlled environment rather than only in front of one.

  • What may enter. Which evaluation package or query is allowed to reach this environment at all.
  • What may execute. Which candidate model may run locally, from the set already permitted for the task.
  • What may participate. Which local dataset or source is eligible for this specific run.
  • What may leave. Which metrics, excerpts, structured facts or local answers policy authorises out of the node.
  • What record remains. The crossing record each node keeps locally, and the identity it contributes to the combined record.

A node is a placement of BoundSense, not a separate product. Nothing here adds a product family or a navigation entry.

See this scenario in the interactive system diagram

Information controls with BoundSense

A first conversation

Start with
one workflow.

Tell us the task and where the information must stay. We'll show a relevant example and discuss whether a scoped pilot makes sense.

Request a demo