• Skip to main content
  • Skip to secondary menu
  • Skip to footer
information matters logo

Information Matters - Agentic AI News and Market Forecasts

The Agentic AI Revolution: what it means for business and the rules of competition

  • Home
  • About
    • The Team
    • About Us
    • Our Methodology
  • Contact
  • Subscribe
  • Downloads
  • Agentic AI Company Tracker
  • Agentic AI Sector Analysis

MongoDB Atlas Vector Search

COMPANY PAGE

MongoDB Atlas Vector Search

MongoDB’s vector database feature inside the Atlas managed-database service — native vector indexing and semantic search alongside operational document storage on a single multi-cloud data layer, with Voyage AI embeddings, automated chunking and a unified query surface targeting the 65,200+ MongoDB total customers (Atlas + self-managed) across AWS, Azure and Google Cloud.

Founded 2007 (parent)
Public (NASDAQ: MDB)
AI Infrastructure
mongodb.com/products/platform/atlas-vector-search

Last Updated: 28 May 2026
Fact-checked: 2 June 2026
Coverage: Tracker · Category Report (AI Infrastructure, forthcoming)
← Back to AI Tracker

The Business

MongoDB Atlas Vector Search is MongoDB's vector database feature inside the Atlas managed-database service — native vector indexing (HNSW-based ANN search) and semantic search alongside the document data already stored in an Atlas cluster, on a single managed multi-cloud substrate across AWS, Azure and Google Cloud. The product launched at MongoDB.local NYC in June 2023, reached general availability in June 2024 with dedicated search nodes for production workloads, and became available in MongoDB Community Edition and Enterprise Server (self-managed) from March 2025. The February 2025 Voyage AI acquisition brought the embedding-model and reranker layer in-house and powers the Atlas-native automated embedding pipeline announced in May 2025 with DevRev and Zomato as named launch customers. The parent company MongoDB Inc (NASDAQ: MDB) was founded 2007 by Dwight Merriman, Eliot Horowitz and Kevin Ryan, IPO'd in October 2017, and is led by President and CEO Dev Ittycheria (in role since September 2014) with Chief Product Officer Sahir Azam, Chief Technology Officer Mark Porter and Voyage AI co-founder Tengyu Ma now leading the embedding-model line inside MongoDB. Atlas is approximately 72% of MongoDB's total revenue and grew +29% year-over-year in the most-recent disclosed quarter; Vector Search adoption inside that base is reported as nearly doubled year-on-year.

Customers and Distribution

MongoDB Atlas discloses 65,200+ total customers as of the January 31 2026 fiscal year-end with approximately 2,700 net adds in the quarter, with Vector Search adoption nearly doubled year-on-year inside the Atlas base. Distribution sits across four channels: direct enterprise sales through MongoDB's global field organisation under CRO Cedric Pech (the dominant motion for the multi-million-dollar enterprise-contract scale); the three hyperscaler marketplaces (AWS, Azure, GCP — with Atlas listed and transactable on all three and Azure Cosmos DB MongoDB vCore competing inside the same channel); the open-source and Community Edition surface as the developer-acquisition flywheel (MongoDB Community Edition has been the on-ramp for the Atlas paid-tier upsell since the IPO, and the March 2025 addition of Search and Vector Search to Community and Enterprise Server extended the same playbook into the vector-search workload); and the system-integrator channel (Accenture, Deloitte, Capgemini and the broader services partner base). Named Vector Search production logos disclosed in 2025-26 launch coverage include DevRev and Zomato (Voyage embeddings launch) with a broader long tail of customer-conference and case-study references at MongoDB.local events and the annual MongoDB user-conference cycle.

Model Strategy

Atlas Vector Search is a Plateau-first play under the IM Framework eight-trajectories taxonomy as it applies to vector data and retrieval: the strategic bet is that the document database becomes the default vector store because vectors live next to the operational document data they describe — removing the second-system tax of running a dedicated vector database alongside the system of record, simplifying governance and lineage, and inheriting the multi-cloud distribution surface MongoDB has already won across AWS, Azure and Google Cloud. The secondary trajectory is Verticals: the February 2025 Voyage AI acquisition brought embedding-model and reranker technology in-house and powers the Atlas-native automated embedding pipeline announced in May 2025, positioning MongoDB to compete on retrieval quality through domain-specific embedding-model depth rather than only on the data-layer integration. The platform is multi-cloud by design (AWS, Azure, GCP all live and at material scale) and multi-model on the embedding-and-LLM layer (Voyage embeddings native, OpenAI text-embedding family, Cohere Embed and open-weight embedding models all supported through the Atlas-native pipeline or customer-provided integrations). The supplier-diversity sub-rubric was held at 8 in the v1.6 evidence pass on the strength of multi-cloud optionality plus the March 2025 addition of Vector Search to Community Edition and Enterprise Server (self-managed), which is the portability-and-trust signal that powered the D1c uplift to 7 in the same pass.

Leadership Team

President & CEO (parent)
Dev Ittycheria
President and CEO of MongoDB Inc since September 2014 — 11+ year tenure across the IPO (2017), the Atlas managed-service ramp, the Realm and Voyage AI acquisitions and the Vector Search product launch. Public-facing on every major earnings call and product cycle. Previously founder/CEO of BladeLogic (acquired by BMC for $900M) and a venture partner at OpenView and Greylock.

Chief Product Officer
Sahir Azam
Chief Product Officer; long-tenured at MongoDB (joined 2016) with prior product leadership across the Atlas managed-service ramp and the Vector Search product launch. Public-facing on product keynotes including MongoDB.local and AWS re:Invent partnership announcements.

Chief Technology Officer
Mark Porter
Chief Technology Officer; joined from AWS where he was GM of Amazon RDS. Anchors the platform-engineering organisation across Atlas, the database core, the search-and-vector layer and the multi-cloud substrate.

VP, AI (via Voyage AI)
Tengyu Ma
Joined MongoDB via the February 2025 Voyage AI acquisition where he was co-founder and CEO. Stanford computer-science professor (on leave) with a background in embedding-model research; now leads the Voyage embedding-model line inside MongoDB and the Atlas-native automated embedding pipeline.

MongoDB Inc is a public company (NASDAQ: MDB) with a full executive bench disclosed in proxy filings; the leadership block above is curated to the Vector Search product line specifically rather than the full parent C-suite. CFO is Serge Tanjga (interim through 2025-26); CRO Cedric Pech leads the global field organisation. Atlas Vector Search is operated inside the broader Atlas product organisation rather than as a separate business unit, so the Vector Search product roadmap reports through Sahir Azam's CPO organisation and the platform-engineering organisation under Mark Porter.

IM Framework Scoring

IM’s structured assessment of MongoDB Atlas Vector Search’s competitive position. The summary below is the headline; expand “Show the full analyst-grade analysis” near the bottom for the per-dimension reasoning and evidence. Methodology →

Competitive Position
Established Incumbent
AI Infrastructure sector

The Information Matters Compass

5 7.5 10 5 7.5 10 Defensibility → Disruption Potential →Disruptive Challengers Dominant InnovatorsEmerging Players Established Incumbents MongoDB Atlas Vector Search © Information Matters

Strategic Bet
Plateau wins for enterprise vector data — the document database becomes the default vector store because vectors live next to the operational data they describe, removing the second-system tax of running a dedicated vector database alongside the system of record
Plus: Plus: verticals — the Voyage AI acquisition and the Atlas-native embedding pipeline extend MongoDB into the domain-specific embedding-model layer that determines retrieval quality for enterprise RAG and agent workloads

Watch: The Voyage AI embedding-model line and the Atlas-native automated embedding pipeline as MongoDB's answer to the embedding-model commoditisation; the head-to-head with Pinecone on serverless vector workloads and with PostgreSQL pgvector on the open-source substitute axis; the share of the 65,200+ MongoDB total customers (Atlas + self-managed) that activates Vector Search as a free-attach versus a paid-tier driver; and the MongoDB Atlas growth rate (+29% YoY most-recent quarter) as the rate-limiting variable on the Vector Search trajectory inside the broader Atlas product.

Funding History

Date Round Raised Post-money Lead investor(s)
Feb 2025 Voyage AI acquisition ~$220M — MongoDB Inc (NASDAQ: MDB) — cash and stock consideration
Oct 2017 IPO (parent) $192M ~$1.6B Morgan Stanley, Goldman Sachs, Barclays — NASDAQ listing (MDB)
2007–2016 Seed through Series F (parent) ~$311M cumulative — Sequoia, Union Square Ventures, Flybridge, NEA, T. Rowe Price (late-stage)

Atlas Vector Search is a feature inside MongoDB Atlas and does not raise external capital separately. The parent company MongoDB Inc is publicly traded on NASDAQ under MDB since the October 2017 IPO; standalone Vector Search economics are not disclosed as a separate segment but are referenced in MongoDB's quarterly earnings cycle as a contributor to Atlas growth. The Voyage AI acquisition (February 2025, ~$220M reported in named press) is the most material recent capital deployment into the Vector Search product line and brought the embedding-model capability in-house.

Competitive Landscape

Atlas Vector Search's competitive set sits in three concentric rings: purpose-built vector databases (Pinecone, Weaviate, Qdrant) competing on greenfield vector-search workloads with developer-grade DX and category-defining mind-share; incumbent search-and-database platforms with native vector indexing (Elasticsearch dense_vector) competing on existing-customer distribution; and the open-source substitute axis (PostgreSQL pgvector) competing as the “we already have a database” default for the Postgres-shop buyer. Atlas Vector Search's structural answer is the same in every ring: vectors live next to the operational document data they describe, on a managed multi-cloud substrate the customer already runs for the system of record — which is a defensibility-first positioning (trust, governance, no second-system tax) rather than a disruption-first one.

Competitor Positioning Distribution edge Threat profile
Pinecone The category-defining purpose-built vector database — serverless-first architecture, ANN-optimised indexing, developer-grade DX and a focused product surface around vector search rather than a feature inside a broader database. Direct developer surface plus AWS, Azure and GCP marketplaces; 5,000+ paying customers and the highest mind-share in the standalone vector-database category. High — the closest direct head-to-head on greenfield vector-search workloads where the buyer has not already standardised on MongoDB for the operational data layer.
Weaviate Open-source vector database with a managed-cloud commercial layer; strong on hybrid search (dense + sparse + metadata filtering) and module-based embedding-and-rerank pipelines. Open-source developer surface plus managed Weaviate Cloud; community-led acquisition with a multi-cloud deployment footprint. Medium-high — open-source distribution and hybrid-search depth give Weaviate a credible technical position on the same RAG-and-agent workloads.
Qdrant Open-source Rust-based vector database with a managed-cloud commercial layer; positioned on performance and cost-efficiency at scale, with a growing enterprise-cloud footprint. Open-source developer surface plus managed Qdrant Cloud; multi-cloud deployment with on-premise self-host as a differentiator. Medium — performance-led positioning and open-source distribution; smaller install base than Pinecone or Weaviate but growing on the cost-efficiency axis.
Elasticsearch (ES|QL + dense_vector)
(Elastic NV (NYSE: ESTC))
The incumbent search platform with native dense-vector indexing and hybrid lexical-plus-semantic search; competes for the same enterprise buyer who already runs Elastic for logs, search or observability. Direct enterprise sales, Elastic Cloud and the three hyperscaler marketplaces; large installed base inside enterprise IT and observability budgets. Medium-high — existing-customer distribution advantage on the search-led buyer; competes with Atlas Vector Search on the same “vectors next to the operational data” positioning when the existing data lives in Elastic rather than MongoDB.
PostgreSQL pgvector Open-source vector indexing extension for PostgreSQL; available across every major managed-Postgres service (AWS RDS, Azure Database for PostgreSQL, Google Cloud SQL, Supabase, Neon, Crunchy Bridge) and the default open-source substitute for buyers who already run Postgres. Available everywhere PostgreSQL runs — the broadest open-source distribution surface in the set; managed-Postgres providers ship pgvector as a standard extension. High — the open-source substitute axis; pgvector is the default “we already have a database, why pay for a second one” answer for the PostgreSQL-shop buyer and the most-cited reason a buyer declines an Atlas Vector Search procurement.

Pricing benchmark: Atlas Vector Search is priced inside the Atlas cluster cost (no separate per-vector or per-query line item on dedicated tiers; serverless tiers price on RPU/WPU consumption) rather than as a standalone SKU — the headline benefit is “no second bill for vectors”. Pinecone, Weaviate and Qdrant price on managed-service consumption (storage, compute, throughput tiers) in the developer-to-enterprise range; PostgreSQL pgvector inherits the cost of the underlying managed-Postgres tier. The competitive frame is the unified data model and managed-service economics (document + vector + search on one cluster, one bill, one operational surface) rather than headline per-query price; the standalone metric MongoDB discloses most consistently is Atlas revenue growth (+29% YoY most-recent quarter) and vector-search adoption (nearly doubled YoY) inside the 65,200+ customer base.

Potential Risks

The case for MongoDB Atlas Vector Search at IM Framework 7.33 rests on the 65,200+ MongoDB total customers (Atlas + self-managed) growing +29% year-on-year, vector-search adoption nearly doubling year-on-year inside that base, the Voyage AI acquisition bringing the embedding-model layer in-house, the unified document+vector data model removing the second-system tax of running a dedicated vector database, and the multi-cloud distribution surface across AWS, Azure and Google Cloud. The case against splits into five risks of differing magnitude — with the feature-versus-standalone ceiling the most structural, the pgvector substitute axis the most active on the open-source side, and the parent-Atlas deceleration the most economically consequential over the medium term.

Feature-inside-a-platform versus standalone-category-leader positioning

Atlas Vector Search is a feature inside the Atlas managed-database service rather than a category-defining standalone product, and the trajectory upside is bounded by the parent product's growth rate. MongoDB Atlas grew +29% year-on-year in the most-recent disclosed quarter — healthy for a public-company managed-database service but materially below the headline growth rates of standalone purpose-built vector databases (Pinecone, Weaviate, Qdrant) competing for the same RAG-and-agent workloads on greenfield procurements. The disruption composite of 6.59 reflects the feature-versus-standalone structural ceiling; the strategic answer is that the unified document+vector data model is more defensible long-term than the standalone-vector-database play, but the bet has to be re-earned each quarter against the standalone-vendor mind-share advantage.

PostgreSQL pgvector as the open-source substitute axis

pgvector ships as a standard extension across every major managed-Postgres service (AWS RDS, Azure Database for PostgreSQL, Google Cloud SQL, Supabase, Neon, Crunchy Bridge) and is the default “we already have a database” answer for the PostgreSQL-shop buyer. The substitute risk is structural rather than competitive — pgvector is good-enough for a large share of small-to-medium vector workloads, and the price ceiling on Atlas Vector Search is set by what a managed-Postgres-plus-pgvector deployment costs for the same workload. MongoDB's answer is the unified document+vector data model (vectors live next to the operational data that already lives in MongoDB), which only binds for buyers who already run MongoDB for the system of record.

Hyperscaler-channel concentration and competitive overlap

Atlas runs on AWS, Azure and Google Cloud, and every one of those three hyperscalers ships a competing vector-database offering on top of their own managed-database stack (AWS OpenSearch Service with k-NN, Amazon Aurora pgvector and DocumentDB vector search; Azure AI Search with vector indexing and Cosmos DB MongoDB vCore vector search; Google Cloud AlloyDB pgvector and Vertex AI Vector Search). The supplier-diversity sub-rubric was held at 8 in the v1.6 evidence pass on the strength of multi-cloud optionality, but the same three hyperscalers are simultaneously the substrate Atlas runs on and competitors on the vector-database layer — particularly Azure Cosmos DB MongoDB vCore, which targets the same MongoDB-API buyer.

Embedding-model dependency and the Voyage AI integration risk

Vector search quality is bounded by embedding quality, and embedding-model technology is moving faster than any single vendor can keep pace with. MongoDB's February 2025 Voyage AI acquisition brought a credible embedding-model line in-house and powers the Atlas-native automated embedding pipeline; the integration risk is that the Voyage model line has to stay competitive with the OpenAI text-embedding family, Cohere Embed, the open-weight embedding models (BGE, E5, GTE) and the Anthropic / Google embedding releases. If Voyage falls behind, Atlas Vector Search becomes a generic vector store with a customer-provided embedding pipeline rather than an integrated retrieval-quality stack.

Parent-company growth deceleration as the rate-limiting variable

Atlas Vector Search adoption is reported as nearly doubled year-on-year inside the Atlas customer base, but Atlas itself is decelerating from previous quarters (+29% YoY most-recent versus historically higher rates) and the parent product's growth rate is the rate-limiting variable on the Vector Search trajectory. If the parent Atlas product's growth continues to decelerate, the absolute pool of customers being upsold into Vector Search compresses regardless of the Vector Search attach rate — and the disruption composite of 6.59 already prices in a feature-attached growth profile rather than a standalone-category growth profile.

Recent IM Coverage

  • AI Infrastructure — Category Report (forthcoming) Pending.

Show recent press coverage of MongoDB Atlas Vector Search
  • Feb 2025 — MongoDB to acquire Voyage AI to enable organisations to build trustworthy AI applications.
  • Mar 2026 — MongoDB reports fourth quarter and full year fiscal 2026 financial results — Atlas Q4 revenue grew 29% YoY; share of total revenue ~70-72% per FY26 disclosures (approximate).
  • May 2025 — MongoDB adds automated Voyage embeddings to Atlas Vector Search — named launch customers DevRev and Zomato.
  • Mar 2025 — Search and Vector Search are now available for use in MongoDB Community Edition and Enterprise Server.
  • Apr 2026 — MongoDB faces growth dilemma as AI vector search adoption doubles and total revenue deceleration signals maturing cycle.
  • Jun 2024 — MongoDB Atlas Vector Search generally available with dedicated search nodes for production workloads.
  • Jun 2023 — MongoDB introduces Atlas Vector Search at MongoDB.local NYC — native vector indexing inside the Atlas managed service.

Curated feed of named-source coverage — MongoDB's own investor-relations and newsroom, named-author analyst and business press (Constellation Research, AInvest, Reuters, Bloomberg). Excludes wire-aggregator reposts and unsourced AI round-up pieces. Vector Search is covered inside MongoDB's public-company earnings cycle rather than as a separately disclosed segment; the press feed is anchored by the quarterly Atlas revenue and adoption disclosure and by product-launch milestones on the Vector Search and Voyage AI roadmap.

Show the source register for the figures on this page

IM operates a primary-source-where-possible discipline. The figures above come from:

  • Revenue — Atlas growth and parent disclosure: MongoDB Atlas revenue grew 29% year-over-year and represented approximately 72% of total revenue per MongoDB's fourth quarter fiscal 2026 earnings release. Vector Search is not broken out as a separate segment but is referenced in earnings commentary as a contributor to Atlas growth, with vector-search adoption disclosed as nearly doubled year-on-year. We label this “Atlas revenue (parent-company disclosure)” rather than “Vector Search revenue” because MongoDB does not separately disclose Vector Search GAAP revenue.
  • Customers — Atlas base: 65,200+ total MongoDB customers as of the January 31 2026 fiscal year-end with approximately 2,700 net adds in the quarter, per MongoDB's fourth quarter fiscal 2026 earnings release. Vector Search adoption is reported inside that base — nearly doubled year-on-year per the same disclosure and corroborated by named-press analyst coverage.
  • Voyage AI acquisition: MongoDB announced the acquisition of Voyage AI in February 2025 to bring embedding-model and reranker capabilities in-house and power the Atlas-native automated embedding pipeline; see MongoDB's acquisition announcement and the product-integration coverage in Constellation Research (DevRev and Zomato named as launch customers).
  • Vector Search availability — Community and Enterprise Server: MongoDB Vector Search is available in MongoDB Community Edition and Enterprise Server (self-managed) in addition to the Atlas managed service, per the March 2025 community announcement. Self-managed availability is the portability-and-trust signal that powered the D1c sub-rubric uplift to 7 in the v1.6 evidence pass.

Methodology & Disclaimer

For metric definitions, source-tier hierarchy, and decline-to-publish rules, see the tracker methodology. Confidence dots (• green / • amber / • red) follow the same convention as the AI Tracker.

Spotted a figure you believe is wrong? Send corrections to info@informationmatters.net.

Information Matters Framework scores are the considered opinion of the IM team — human and AI — applied to publicly-available evidence under a disclosed methodology. They are not statements of fact about the companies scored and they are not investment advice.

Footer

  • LinkedIn
  • YouTube

Copyright © 2026 ยท Information Matters

Manage Consent
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
View preferences
  • {title}
  • {title}
  • {title}