Compatibility and status
Check here for the status of each Cortrix capability before you make a production, security, benchmark, or integration decision.
Cortrix is in pre-release. The current version is v1.0.0-rc.2. Nothing in this documentation is a production-readiness commitment yet. Verify it in your own environment before you use it in production.
What each status means
| Status | Meaning |
|---|---|
| Preview | Available and documented. Verify it in your own environment before production use |
| Off by default | Implemented, but not active in the shipped configuration, where authentication is off. Turn on authentication to use it, and read what happens while it’s off |
| In development | Present in part or being built. Not supported yet. Don’t rely on it |
Current status
Preview
| Capability | Documentation |
|---|---|
| Docker quickstart | Quickstart |
| Namespaces, document upload, and processing | Upload documents |
| Query, cross-namespace query, and reranking | Query and rerank |
Writing, listing, editing, and deleting memories. Semantic search over explicit memories doesn’t return results in v1.0.0-rc.2 | Work with memory |
| Correcting a memory by hand: invalidate, restore, and the audit trail | Work with memory |
| Directory watchers | Watch a directory |
| The HTTP API and the OpenAPI spec | HTTP API |
| MCP server (local stdio) | MCP server |
| Python SDK | Python SDK |
| Framework adapters | Framework adapters |
| Fixed-flow chat in the built-in Agent | Built-in Agent |
| The NVIDIA CUDA execution provider on Linux | NVIDIA CUDA |
| OCR and document parsers | — |
Off by default
These work only after you turn on authentication.
| Capability | With authentication off |
|---|---|
| API key permissions (read, write, admin) | Every request has all three |
In development
- Tenants, members, and access control
- Tenant isolation
- Roles (RBAC). Access is decided by an API key’s permissions
- Quotas. Quota values can be read and updated, but requests aren’t checked against them
- Memory extraction, including automatic handling of contradicting memories
- pgcortrix
- Database import
- Log redaction
Using a preview capability
An endpoint that appears in the OpenAPI spec is part of the documented API surface. That doesn’t mean it has been verified in every runtime. When you write client code:
- Take request and response shapes from the OpenAPI spec. This documentation notes where tested behavior differs from the spec.
- Pin the version of your target server, and rerun your smoke tests after you upgrade Cortrix.
Authentication and security
API key permissions are off by default: Cortrix checks them only with authentication on, and with it off anyone who can reach the server’s port acts as an admin. Tenant isolation and access control are in development, and API key authentication itself hasn’t been verified for this documentation. Deploy Cortrix only on a network you control. See Security boundaries.
A namespace is a logical query scope. It isn’t an authentication or tenant-security boundary.
Benchmarks
The published benchmark numbers measure retrieval quality at top_k=10. They say nothing about end-to-end answer quality, production latency or capacity under concurrency, security or compliance, how Cortrix ranks against other products, or business outcomes. For the measurement conditions and data, see Benchmark evidence.
Before production
At a minimum, verify these in your target environment:
- Data persistence and backup strategy
- Deployment topology and resource limits
- Network exposure
- Compatibility of the API, SDK, and MCP server with your target build
- The actual behavior of every preview capability you depend on