* initial commit; fixed anchor links on internal docs pages * add back in absolute paths for links in code comments * fix: update linkchecker include filter to match server port 1314 PR #1629 changed the Hugo server to port 1314 but forgot to update the --include filter, which still matched port 1313. This caused all links to be excluded, making the checker a no-op (0 checked, 82277 excluded). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Fix url rewrite regex so images are not impacted * Fix links from non-documentation pages * Fix broken links * more broken links * more broken links * broken link * Add srcset width descriptor to .lycheeignore * Ignore URLs that contain a % character * Anchor regex so it matches the entire URL --------- Co-authored-by: kanungle <neil.kanungo@gmail.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Abdon Pijpelink <abdon.pijpelink@qdrant.com>
4.2 KiB
draft, title, short_description, description, preview_image, date, author, featured, tags
| draft | title | short_description | description | preview_image | date | author | featured | tags | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| false | Building real-time multimodal similarity search in Flipkart Trust & Safety with Qdrant | Tackling fraud and abuse with scalable similarity search. | Tackling fraud and abuse with scalable similarity search. | /blog/case-study-flipkart/social_preview_partnership-flipkart.png | 2026-01-09 | Daniel Azoulai | true |
|
Tackling fraud and abuse with scalable similarity search
At Flipkart, the Trust & Safety team is focused on detecting and preventing platform abuse and fraud. A critical part of this work involves running large-scale similarity searches across customer and seller-submitted data, particularly images. This allows the team to identify patterns associated with fraudulent activity, such as repeat returns or duplicate seller claims, before they cause downstream harm.
“Platform integrity is a constant challenge. To stay ahead of fraudulent actors, we needed a system that could compare multimodal data in real time, not just in long-running batch jobs.”
— Sourabh Sarkar, SDE-III, Trust & Safety at Flipkart
Limitations of prior batch-based methods
The team’s earlier approach to similarity search used HBase with Locality-Sensitive Hashing (LSH). While workable for batch analysis, this system was slow and could not keep up with the demands of real-time fraud prevention. In some cases, finding similar images in historical data could take up to nine hours.
Additionally, Flipkart’s embedding models produce high-dimensional vectors (2048 dimensions), which added pressure on indexing performance and made efficient real-time querying more difficult.
Evaluating open-source options and selecting Qdrant
To address these challenges, the team evaluated multiple open-source vector databases through a proof-of-concept. They chose Qdrant because it provided:
• Deployment flexibility with official Debian packaging, which fit well with Flipkart’s internal infrastructure
• Efficient HNSW indexing capable of handling simultaneous reads and writes
• Support for high-dimensional embeddings, critical for the models in production
Building a multi-tenant similarity service
The Trust & Safety team then built a new multi-tenant similarity service. This platform now supports several important use cases:
• Fraud detection: Real-time image similarity checks to identify potentially abusive behavior
• Address clustering: Grouping unstructured customer addresses to improve last-mile delivery routing
• Retrieval-augmented generation (RAG): Serving as the retrieval layer for internal GenAI initiatives
“What used to take hours in our old batch workflows can now be done in under a minute. That change has been crucial in stopping fraud before it impacts customers.”
— Sourabh Sarkar, SDE-III, Trust & Safety at Flipkart
Detection time reduced from 9 hours to 1 minute
The shift from batch processing to real-time search has significantly reduced detection time, from nine hours to under one minute. This improvement enables much earlier intervention against fraud.
From a developer perspective, integration with the Java gRPC SDK and Prometheus metrics endpoint simplified adoption and monitoring. The team also built custom adapters and backup scripts, ensuring the service could be reused by multiple teams without duplicating effort.
Looking ahead: Expanding beyond fraud detection
The Trust & Safety team continues to broaden its capabilities. Upcoming projects include:
• Expanding retrieval use cases for company-wide RAG systems
• Standardizing on a Kubernetes-based Qdrant deployment as the embedding store across different groups at Flipkart
• Exploring integrations with agentic AI frameworks to further automate detection and prevention workflows
“We see vector databases becoming a key part of modern AI infrastructure. It’s not only for fraud detection, but also as a foundation for new AI systems we’re experimenting with.”
— Sourabh Sarkar, SDE-III, Trust & Safety at Flipkart