Mandarum Platform Remember · GPU Memory & RAG Engine
Mandarum Cuvex logo

Mandarum Cuvex — RAG and memory at GPU speed.

A unified memory engine that runs embedding, RAPIDS/cuVS vector search, and reranking in one GPU-accelerated path — with permission-aware filtering so retrieval respects per-user and per-agent access, and freshness sync from 200+ connectors.

RAPIDS / cuVS NeMo Retriever Permission-aware
Why Cuvex exists

Why your RAG stack is slow, fragile, and leaking access.

01 · Slow recall

CPU vector search blows tail latency

At production QPS and corpus size, CPU ANN search misses latency budgets. Cuvex runs billion-scale search on GPU in single-digit milliseconds.

02 · Stitched stacks

A DB, an embedder, a reranker

Three services with three hops add latency and cost. Cuvex fuses embed, search, and rerank into one accelerated path co-located with serving.

03 · Permission leakage

RAG ignores access control

Retrieval that bypasses ACLs is a breach. Cuvex enforces row-level access at query time, so an agent recalls only what its caller may see.

Capabilities

What Cuvex does.

01 / Retrieve

Billion-scale GPU vector search via cuVS.

RAPIDS cuVS runs approximate nearest-neighbor search on NVIDIA GPUs at sub-10ms p99 and 100x CPU throughput. Hybrid dense + BM25 with GPU reranking, multi-tenant isolated.

  • RAPIDS cuVS GPU ANN search
  • Sub-10ms p99 at 100M+ vectors
  • Hybrid dense + BM25 + GPU rerank
cuvex · retrieve
cuvex.retrieve({
  query: query,
  model: "nemo-retriever-e5",
  top_k: 10,
  acl: "enforce"
}); // GPU ANN, permission-checked
Docs

Confluence · Notion · Drive

Systems

Salesforce · Jira · Snowflake

Index

cuVS GPU ANN + knowledge graph

Access

Row-level ACL at query time

02 / Ground

NeMo Retriever grounding, org-wide.

Connect documents, tickets, CRM, and warehouses into a NeMo Retriever-indexed fabric. Models ground on authoritative context instead of hallucinating it, freshness-synced from 200+ connectors.

  • NeMo Retriever embedding + reranking
  • Entity resolution across 200+ sources
  • Incremental freshness sync via CDC
03 / Control

Permission-aware by construction.

Every vector and document carries access rules enforced at GPU retrieval time. Recall is scoped to the caller — no exceptions, with right-to-be-forgotten built in.

  • Row-level ACL on GPU retrieval
  • Tenant + user isolation
  • Right-to-be-forgotten built in
retrieve · project-2031acl: user matchgranted
retrieve · payroll-q4acl: no matchwithheld
By the numbers

Cuvex, in production.

0
Connected sources
0
Permission-aware
0
p99 GPU retrieval
0
vs CPU throughput

Give your models memory worth having.

See sub-10ms GPU retrieval, ACL-enforced recall, and NeMo Retriever grounding on your own corpus. Start free, or let the team connect your first data source.