Skip to content

Overview

What Cortrix is, what it’s made of, and where it stands today.

Cortrix is open source semantic storage built for AI agents. It’s agent-native storage for retrieval, memory, and API-driven AI applications.

It provides a semantic storage server with namespaces, documents, blocks, hybrid search, memory APIs, and agent-oriented access paths. It’s designed for agents and applications that need a programmable retrieval layer rather than a one-off vector database wrapper.

Important

Cortrix is in active pre-release. The current version is v1.0.0-rc.2. Interfaces and features are at different levels of maturity, and authentication, authorization, and production readiness are not established. See Compatibility and status.

What is semantic storage?

Semantic storage connects information with the context an application needs to use it. Cortrix does this through retrieval, memory records, and links back to sources.

That maps to three needs in agent work:

NeedWhat it means
Agent workflowsAn agent needs to read source material, use tools, and keep track of what happened
Context for a taskA useful answer needs relevant material at the right moment. Storage keeps that material available, and retrieval decides which passages belong in the prompt
Memory across tasksSome experience is worth carrying into the next task. Storage preserves it, but the system still needs to check whether an old observation applies

Design

  • Agent-native: designed around agent data workflows. Semantic processing, memory, and traceability are shared storage concerns rather than scattered integration code.
  • Semantic storage: documents are parsed, chunked, embedded, and indexed in a shared semantic layer, so agent workflows can query meaning and source context together.
  • Built to fit existing stacks: works with your existing databases, tools, and agent workflows while giving retrieval, memory, and audit a shared semantic layer.

Building blocks

Building blockWhat it covers
Semantic Processing Chain (SPC)Parsing, OCR fallback, chunking, enrichment, embedding, and indexing
Hybrid query and rerankerVector search, BM25, rank fusion, and reranking
AI interaction memoryMemory APIs and typed memory records
Agent observabilitySession, trace, and agent identity
Source-level traceabilityInspectable source context across chunks, documents, and turns
Namespaces and cross-namespace queryLogical query scope for projects and workflows
Local embeddingONNX Runtime and BGE-M3
Access pathsHTTP, MCP, the Python SDK, framework adapters, data import, and PostgreSQL
Note

A namespace is a logical query scope. It is not an authentication, authorization, access-control, or tenant-security boundary.

Components in the repository

ComponentLocationRole
cortrix-serversrc/The C++ backend and HTTP API
OpenAPI specapi/openapi.yamlThe public HTTP API contract
MCP servercortrix-mcp/An MCP server for IDE and agent clients
Python SDKsdk/python/The Python client
Built-in Agentcortrix-agent/A fixed-flow RAG chat service
Web UIweb/The local web interface

Access paths

PathBest for
HTTP APIYour own services, or direct calls from an agent
MCP serverIDE agents and MCP-compatible clients
Python SDKPython applications and RAG pipelines
Built-in AgentLocal fixed-flow chat over Cortrix storage

To pick one, see Choose an access path.

Current status

Cortrix is in pre-release. To see whether a capability is in preview or in development, see Compatibility and status.

License

Cortrix Core is licensed under Apache-2.0. That applies to v1.0.0-rc.2 and later. The historical v1.0.0-rc.1 release remains under AGPL-3.0-only. Third-party material keeps its own license.

Next steps