MongoDB Software / SaaS Israel

Cambium

Fraud Detection

Cambium's Marvad AI examination platform had to detect cheating and plagiarism across tens of thousands of papers, but vector-search latency reached 55 minutes and false positives surged as production volumes approached 15 million vectors.

around 15 million vectors
could take up to 55 minutes
having one come in three minutes
moving to two search nodes at the S60 level, each with 64GB of memory

Reported impact

Business outcome

After tuning Atlas search nodes and vector-search settings, Cambium cut similarity-search latency from up to 55 minutes to about three minutes and got Marvad AI live in time for a national rollout.

  • Risk Reduction
  • Scalability
  • Speed to Market

Solution

Cambium used MongoDB Atlas as the data platform for Marvad AI, a national examination system that scans uploaded exam papers and flags cheating or plagiarism through vector-based similarity search. As production data volumes climbed toward tens of thousands of documents and roughly 15 million vectors, search latency ballooned to 55 minutes and false positives threatened the launch. Working with MongoDB Professional Services, Cambium tuned index sizing, memory, and search-node configuration instead of simply adding servers; the team vertically scaled to two S60 search nodes with 64 GB RAM each and reset vector-search parameters to improve precision. The result was a platform that moved from nearly an hour per query to minutes, restored real-time viability, and gave Cambium repeatable guidance for future large-vector AI projects.

Data flow

Scanned exam papers are uploaded to Marvad AI, embedded into vectors, and stored in MongoDB Atlas for similarity search. Atlas search nodes compare new submissions against the existing corpus, and tuned vector-search parameters drive the alerting workflow that flags likely cheating or plagiarism to the exam platform.

Solution architecture

2 components · 2 layers
  1. Storage
    • MongoDB Atlas Stores embeddings and exam-paper data while running the vector-search workload behind Marvad AI.
  2. Orchestration
    • MongoDB Professional Services Advised Cambium on search-node sizing, memory tuning, and vector-search configuration before launch.

Architecture clues

  • Marvad AI runs vector similarity search over exam-paper embeddings in MongoDB Atlas.
  • MongoDB Professional Services recommended vertical scaling plus parameter resets instead of just adding servers.
  • The production problem centered on oversized indexes, page faults, and memory pressure on search nodes.
  • The tuned deployment uses two S60 search nodes with 64 GB RAM each.

Evidence from the source

Marvad AI's job is to then check each one for duplications, and trigger an alert if a close match is detected
Overnight, we jumped from waiting almost an hour for a search response to having one come in three minutes.
We scaled vertically to larger search nodes with more RAM
around 15 million vectors could take up to 55 minutes
Transparency Evidence & methodology 90/100 reference value · 79% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value90/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. MongoDB

    Cambium customer story

    First-party
    https://www.mongodb.com/solutions/customer-case-studies/cambium
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived May 15, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified May 11, 2026 · MongoDB · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.