MongoDB Software / SaaS South Korea

Syncly

Real-time Analytics

Syncly needed a more efficient way to run semantic analytics on voice-of-customer data as its user base and embedding volumes grew beyond what manual similarity calculations could support.

“If we had to go through more than 10,000 similarity comparisons for a feedback analysis, we can now get the desired results with just one query by setting up a Vector Search index.”
“We are experiencing more than 10 times faster performance with Atlas Vector Search index compared to manual processing.”

Reported impact

Business outcome

Syncly made similarity analytics more than 10x faster, reduced server and cloud-service pressure, and improved both service efficiency and customer insight delivery as it expanded internationally.

  • Customer Experience
  • Productivity Improvement
  • Speed to Market

Solution

Syncly built its voice-of-customer analytics service around MongoDB Atlas and Atlas Vector Search so it could analyze chats, calls, meetings, and other customer-feedback signals with semantic context instead of brittle keyword-only methods. The platform collects structured and unstructured feedback, computes embeddings, and uses Atlas Vector Search to cluster that data by topic and similarity for downstream insights. Before adopting Atlas Vector Search, the team loaded embeddings into backend servers and manually computed similarity, which increased database and server load as adoption grew. By moving vector management into MongoDB Atlas, Syncly unified document and vector data on one platform and automated the indexing and query logic that previously required custom code. This reduces resource consumption while giving the startup a more scalable foundation for global expansion, faster feature delivery, and AI-driven customer-experience insights.

Data flow

Customer feedback from chats, calls, meetings, and related channels is collected into MongoDB Atlas, embedded for semantic analysis, indexed with Atlas Vector Search, and then clustered and queried so Syncly can surface patterns and recommendations back to customer-facing teams.

Solution architecture

2 components · 2 layers
  1. Storage
    • MongoDB Atlas Stores Syncly's customer-feedback records and vector data on one platform for analysis and service delivery.
  2. Serving
    • Atlas Vector Search Performs similarity search and clustering over embedding vectors so Syncly can analyze feedback semantically.

Architecture clues

  • Atlas Vector Search is used for cluster analytics that group feedback by topic.
  • Syncly previously loaded embeddings into backend servers and computed similarity manually.
  • The startup expanded from Korean and U.S. markets toward broader global operations.
  • The unified Atlas platform reduced the need for higher-tier server instances.

Evidence from the source

Syncly uses AI to enable effective similarity analytics even in a mix of structured data and unstructured data such as images and videos.
“Another key benefit of Atlas Vector Search is that it is built on MongoDB Atlas, which allows us to store and manage both document and vector data in a unified platform.”
“Storing vector data in MongoDB Atlas allowed us to focus on developing the data collection and classification services that we had committed to.”
“We are experiencing more than 10 times faster performance with Atlas Vector Search index compared to manual processing.”
Transparency Evidence & methodology 90/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 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 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

    Syncly customer story

    First-party
    https://www.mongodb.com/solutions/customer-case-studies/syncly
    Source type
    Vendor-published customer story
    Published
    Jun 17, 2025
    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 Jun 17, 2025 · 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.