MongoDB Software / SaaS Europe

LekoTech

Enterprise Knowledge Search · Sales Automation

LekoTech needed to digitize millions of unique car parts to promote reuse but faced latency of up to 35 seconds with its existing search system.

LekoTech needed to digitize millions of unique car parts to promote reuse but faced latency of up to 35 seconds with its existing search system.
LekoTech previously struggled with search latencies of up to 35 seconds, a delay that risked losing potential buyers to competitors if they couldn’t instantly confirm a part’s price and availability.
The business has reduced its search latency from 35 seconds to under two seconds, and in many cases, full inventory searches across 300,000 spare parts can be handled in less than 100 milliseconds.

Reported impact

Business outcome

Search times dropped to under two seconds, enabling auto dismantlers to double sales within months and scale the circular economy for auto parts.

  • Customer Experience
  • Revenue Growth
  • Speed to Market

Solution

LekoTech needed to digitize millions of unique car parts to promote reuse but faced latency of up to 35 seconds with its existing search system. Consolidating on MongoDB Atlas and Vector Search allowed LekoTech to manage complex metadata and offer fast natural-language queries. More importantly, LekoTech aimed to advance the circular economy by focusing exclusively on original equipment manufacturer (OEM) parts, which are manufactured to last a lifetime. “LekoTech’s primary aim is to help breakers and dismantlers manage parts and inventories digitally,” said Nikolin Ngjela, CTO and Co-founder at LekoTech. “Dismantlers often don’t have a close connection with technology,” explained Ngjela. “One of our biggest struggles as a startup was to both educate them and make our system easy to use.” To make this vast, fragmented catalog accessible to buyers and fleet operators, speed is paramount.

Data flow

Business documents, tickets, records, and other operational content stay in MongoDB Atlas Vector Search and MongoDB Atlas Search, where search indexes or vector embeddings are built and then queried in real time to supply grounded results to applications, assistants, or discovery features. Upstream and downstream integrations include AWS, APIs.

Solution architecture

3 components · 2 layers
  1. Storage
    • MongoDB Atlas Stores the operational, document, and context data behind LekoTech's AI-powered search and assistant experiences.
  2. Serving
    • MongoDB Atlas Vector Search Retrieves semantically relevant context from LekoTech's data for AI, search, and recommendation workflows.
    • MongoDB Atlas Search Provides relevance-based text retrieval across LekoTech's documents and application data.

Architecture clues

  • AI agents or assistants are layered on top of the MongoDB data platform.
  • The deployment integrates with APIs.
  • The deployment integrates with AWS.
  • Vector search is part of the retrieval layer for semantic or generative-AI use cases.

Evidence from the source

“Dismantlers often don’t have a close connection with technology,”
“LekoTech’s primary aim is to help breakers and dismantlers manage parts and inventories digitally,”
“Our Fleet Management app is a consumer-oriented layer that lets vehicle owners and fleet operators access that data for everyday maintenance and parts sourcing.”
“reduce, reuse, and recycle,”
Transparency Evidence & methodology 100/100 reference value · 89% 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 value100/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 impact25/25
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • 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 provenance10/10
    The publication date comes from the source page or publisher.
  • 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

    LekoTech customer story

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

Date evidence

  • Published on source page May 18, 2026 · MongoDB · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.