Skip to content

Stack fit

How Cortrix relates to your existing stack: keep, add, replace, or unknown.

When you bring Cortrix into an existing stack, these decision cards show what you keep, what you add, and what you still need to verify yourself.

The cards aren’t replacement guarantees or product rankings. Each card proves only the boundary it states.

Vocabulary

TermMeaning
keepThe existing component or source of truth stays in place
addCortrix is introduced alongside the existing component
replaceA tested substitution exists for the stated boundary
unknownThe evidence isn’t sufficient to choose yet
not_supportedThe current evidence explicitly excludes the path

PostgreSQL with pgcortrix

Note

pgcortrix is in development and not supported yet. This card records what the evidence does and doesn’t establish. It isn’t a recommendation to adopt it now.

Decision fieldWhat the evidence supports
Existing stackPostgreSQL 13 through 17 with plpython3u, plus a separately running Cortrix service
Decisionkeep PostgreSQL as the business-data system. add the pgcortrix SQL-to-HTTP bridge and Cortrix. replace isn’t claimed
Tested identityCortrix 4a6299ca86c7bec21ed7b8989a729a198fe5a42a, with the standalone SQL-contract and helper tests under sql-extensions/pgcortrix/tests/. The repository marks live PostgreSQL load and pg_regress integration as not yet validated
Data movementExplicit SQL functions submit selected content to Cortrix over HTTP. Change data capture, automatic table mirroring, and two-way sync aren’t proven
Who owns syncThe application or operator owns selection, submission, resubmission, deletion, and consistency checks
Query pathPostgreSQL SQL function → plpython3u helper → Cortrix HTTP API → rows returned to SQL
Failure domainExtension installation, PL/Python availability, endpoint policy, network transport, Cortrix health, asynchronous indexing, and query execution are separate failure points
Security responsibilityA PostgreSQL superuser installs the extension. Operators own the endpoint setting, API key handling, Cortrix authentication, namespace permissions, network policy, and tenant boundaries. Security validation on a live PostgreSQL hasn’t been done yet
Exit and rollbackStop calling the SQL functions and remove the extension following PostgreSQL procedures. The source data in PostgreSQL remains authoritative. Namespaces and submitted copies in Cortrix need a separate cleanup decision
EvidenceThe pgcortrix README, SQL contract tests, helper tests, and SQL and helper seam tests

Boundary: this card supports evaluating the bridge locally as an addition. It doesn’t establish compatibility with managed PostgreSQL, live migration, automatic synchronization, production hardening, or a replacement for PostgreSQL.

See pgcortrix.

BGE-M3 embedding plus reranking

Decision fieldWhat the evidence supports
Existing stackAn application with source documents and an existing retrieval path. Compatibility with any named third-party vector database is unknown
Decisionkeep the original source documents and the application’s ownership of them. add Cortrix as a retrieval service. Whether an existing vector database can be replaced is unknown until a test against that specific stack proves data, query, and rollback parity
Data movementSource documents are ingested into Cortrix and indexed with BGE-M3. The measured profile reranks with bge-reranker-v2-m3. This creates a copy and an index managed by Cortrix
Who owns syncThe application or operator owns the initial ingest, propagating updates and deletes, draining tasks, and mapping source-document identity
Query pathApplication → Cortrix /api/v1/query → vector retrieval → reranking → mapping back to source documents. The measured profile sets rerank=true and rag_fusion=false, with LLM stages off
Tested identityBenchmark bundle commit 4b94390c1d5f7be95065e7483362ec7f93774ed7, Cortrix 79a4eb17c62521338d1ac47a9749e6230e87e69b, and public runner 9490520c24a96ed97b80073ed3ebab096b80550b. Full-corpus SciFact, NFCorpus, and FiQA with every judged test query, plus full-corpus Quora with a deterministic 2,000-query subset
Failure domainModel availability, the execution providers for embedding and reranking, ingest tasks, Cortrix storage and indexing, source mapping, and the calling application are separate failure points
Security responsibilityOperators own Cortrix authentication, namespace permissions, model provenance, network exposure, source-data policy, and deletion verification. The benchmark doesn’t prove tenant isolation or production security
Exit and rollbackKeep the original corpus and the previous query path until acceptance. Stop routing queries to Cortrix and delete the test namespaces explicitly. Exporting to a third-party index and zero-downtime cutover aren’t claimed
EvidenceThe pinned bundle README, its manifest, and the per-cell scorecards in the same bundle

Boundary: the measurements this card refers to cover retrieval quality at top_k=10 only. See Benchmark evidence.

Next steps