Company Historically Provides H-1B Sponsorship
MongoDB builds databases for software teams that need to store and retrieve application data without fitting every record into fixed rows and columns. Its flagship Atlas service runs the database in the cloud and combines it with tools for search, real-time analytics and AI retrieval. Data is stored as flexible documents, letting developers change an application's structure while keeping related information together. Customers pay for cloud resources and usage, or buy Enterprise Advanced subscriptions to run the software themselves with monitoring, management tools and technical support. MongoDB was founded in 2007 and is headquartered in New York City.
Work here?Claim your company
Industries
Company Size
5,001-10,000
Company Stage
IPO
Headquarters
New York City, New York
Founded
2007
See people who can refer or advise you
Help us improve and share your feedback! Did you find this helpful?
Total Funding
$503.1M
Above
Industry Average
Funded Over
9 Rounds
Cerebral Valley's AI Engineering Code Summit Hackathon. News Fri, 06 Nov 2026 21:44:02 UTC 2 hours ago Cerebral Valley's AI Engineering Code Summit Hackathon kicks off tomorrow, with sponsorship from Fetch.ai, Meta, Google DeepMind, and MongoDB. This event highlights the growing intersection of AI and blockchain technologies, emphasizing collaborative innovation in the tech space. Interested... This content is automatically aggregated. Full credit goes to the original publisher (coinfomania.com).
Introducing the MongoDB Vercel AI SDK integration: persistent memory for AI applications. MongoDB Inc. is excited to announce the release of the MongoDB Vercel AI SDK integration, which provides AI applications and agents built with Vercel's SDK with a persistent memory store in MongoDB Atlas. It's now open source and generally available on npm. This integration adds MongoDB Atlas as the memory store in the existing Vercel AI SDK code. Once installed, the package connects Vercel AI SDK applications to MongoDB Atlas and automatically stores the application's memories in documents. This allows the application to retain memories about conversations, user facts, and past events that persist across sessions, users, and restarts. What is the Vercel AI SDK? The Vercel AI SDK is a TypeScript toolkit for building AI applications. It handles calling models, streaming responses, using tools, and running agents that work through multi-step tasks. The SDK doesn't include a database to persist memories between runs. Without memory, an AI application starts every conversation with no knowledge of the last one. It doesn't know who the user is, what they asked yesterday, or what it learned along the way. It doesn't have any context. Today, developers have to build their own tooling to store memories in a layer. That usually means designing a database schema, writing jobs to clear out old data, and setting up vector search so the application can find relevant past information by semantic meaning instead of just keywords. It's a lot of work to build an AI application that can remember context. What types of memory does an AI application need? An AI application needs five kinds of memory, each kept for a different length of time and retrieved differently. This integration automatically categorizes each type of memory and stores it in MongoDB Atlas; here are short definitions of the five memory types: * Session: The conversation an application or agent has in each session. This helps the application follow what the user just said. * Semantic: Facts about people, entities, and preferences, so users don't have to repeat themselves. * Procedural: Workflows and instructions, so the application carries out tasks the way you've defined them. * Episodic: Key events and outcomes, so the application can recall what happened before. Kept for one year of inactivity by default. * Scratchpad: Temporary notes for work in progress. They expire after an hour and can be promoted to episodic memory if they turn out to matter. Semantic and procedural memories are versioned, so history is preserved when a fact changes. The semantic, procedural, and episodic tiers use MongoDB Vector Search, which finds stored memories by semantic meaning rather than by exact keywords. This integration automatically creates the vector indexes and detects embedding dimensions at startup. Developers can use any AI SDK embedding model to create vector indexes, including Voyage AI, OpenAI, Cohere, or Google. Figure 1. How the integration works with MongoDB Atlas and the Vercel SDK interface. How should memory age? Each category of memory has its own retention policy, so short-lived notes expire quickly, and long-term facts are stored for longer. The MongoDB Vercel AI SDK integration ships with defaults for every category, which developers can customize if they desire. Effective memory retention requires a balance. Keeping memories indefinitely can decrease retrieval performance and increase costs, while deleting them too early can cause applications to forget important context. This integration includes features to help developers easily set the right balance: * Retention modes: Choose none (never expire), ttl (expire after a set time), ttl+importance (expire after a set time unless the memory is marked important), or dynamic, where you define your own forgetting time period. * Model-driven forgetting: With memory_forget, the model can delete a specific memory when a user says "forget that." Removal usually happens within about 60 seconds. Because the memory is stored in MongoDB Atlas, application operational data, its memory, and the vector search that retrieves it run on one platform. Developers can secure, monitor, and scale a single database without bolting on a separate vector store or memory service alongside it. What changes when you run the MongoDB Vercel AI SDK Integration in production? This production release gives developers greater controls over their data and flexibility in how they use the integration: * Reliable session history: By default, the model decides when to save and read conversation turns, so it can occasionally skip one. For production, you can use the AI SDK hooks so that the application's own code loads and saves the transcript at every turn. Every user, assistant, and tool message is saved exactly once. * Separate data per customer: Developers can add a filter field, such as tenant_id, to the application's vector indexes to limit each search to a single customer's memories. * Application names and layout: Developers can rename collections and indexes to match the existing application schema or turn off indexing for unused categories. * Open source: The package is licensed under Apache 2.0 and works with any AI SDK model. Get started today. Developers can add memory to an existing Vercel AI SDK project in three steps. This integration works with AI SDK v6 and v7 and requires a MongoDB Atlas cluster. * Install the package and its peer dependencies: npm install @mongodb-developer/vercel-ai-memory ai mongodd * Create a memory instance with an Atlas connection string and an embedding model. * Pass the memory tools to the application, scoped to a user and session. TypeScript const mongodbMemory = createMongoDBMemory({ uri: process.env.MONGODB_URI!, embedder: openai.embedding('text-embedding-3-small'), const agent = new ToolLoopAgent({ model: openai('gpt-4.1'), tools: mongodbMemory({ userId: 'alice', sessionId: 'sess-001'}), From there, the model decides when to save and when to search for memories. Next steps. Ready to add memory to your application? Start with the Vercel AI SDK memory documentation. For more details, see the following resources: @mongodb-developer/vercel-ai-memory on npm: The package. GitHub repository: Source code and examples. MongoDB Resources
MongoDB appoints Alex Newman to lead Australia & New Zealand. Thu, 5th Nov 2026 (Today) MongoDB has appointed Alex Newman as Area Vice President for Australia and New Zealand, where he will lead the company's business. Based in Sydney, Newman joins after serving as Regional Vice President at Salesforce. He has also held senior roles at Informatica, EMC and Macquarie Telecom, and brings more than 20 years of experience leading business and technical teams in the technology sector. The appointment comes as MongoDB looks to expand its presence in Australia and New Zealand, where technology companies and large enterprises use its database software for critical applications. Customers in the region include Heidi, Lendi Group, Pathfinder Labs, Woolworths Group, Bendigo Bank and New Aim. Newman will report to Richard Scott, Senior Vice President, Asia Pacific and Japan, who was recently appointed to lead the broader regional business. Scott said MongoDB is seeing strong demand from organisations looking to move artificial intelligence projects into production. "Every organisation I speak to wants the same thing: AI that works, scales in production, and delivers real business outcomes, on data they can trust," said Richard Scott, Senior Vice President, Asia Pacific and Japan, MongoDB. "Alex brings deep enterprise data and AI experience to MongoDB, as well as a track record of building teams and customer relationships across ANZ. That's exactly what we need as local organisations move into the AI-in-production era, and his leadership will help us deliver it." Regional base Australia is also one of MongoDB's larger engineering centres globally. The local team includes more than 70 engineers working on parts of the company's core architecture, including its global storage engine. Engineers in Australia contributed to the recent launch of MongoDB Atlas Infinite and developed internal AI coding tools to help customers update legacy data systems. Their work supports MongoDB's base of more than 70,000 customers worldwide. Headquartered in New York, MongoDB provides a data platform for operational data, search, analytics and AI-related workloads. The company says millions of developers and about 75% of Fortune 100 businesses use its products for customer-facing applications. Newman said he sees broad opportunity in the local market as companies increase spending on data and AI. "I've never been more optimistic about what organisations in this region will be able to do with AI and data," said Alex Newman, Area Vice President, Australia and New Zealand, MongoDB. "The data layer is where AI succeeds or fails, and I believe MongoDB's intelligent data platform is positioned to become the standard for AI. I'll be focused on growing the talented team we already have in the region and delivering outstanding results for our customers."
MongoDB hires Alex Newman as new A/NZ lead 5 Nov 2026 2 mins
Bring live MongoDB Atlas data into Microsoft 365 Copilot. The federated Copilot connector for MongoDB Atlas gives organizations a governed way to bring live operational data into the flow of work across Copilot experiences. To operate efficiently, businesses require timely information about the systems that underpin their organizations. For example, they need to be able to answer questions like: Which incidents are open? Which orders are delayed? What fields and data types are present in the customer collection? The answers they need often live in operational applications built on MongoDB Atlas, while the questions are asked in the productivity tools people use every day. To help close that gap, MongoDB is excited to introduce a federated Copilot connector for MongoDB Atlas. Now generally available, the connector enables users to ask Microsoft 365 Copilot questions about live data in MongoDB Atlas, bringing operational context into the same experience where people collaborate, analyze information, and make decisions. The connector surfaces MongoDB Atlas data across Microsoft Copilot experiences, including Copilot Chat, Researcher in Copilot, Copilot Cowork, Microsoft Word, Excel, and Teams, with additional experiences planned to follow. MongoDB Inc. is thrilled about what this integration makes possible for customers. By connecting live MongoDB Atlas data to Microsoft Copilot, people can ask questions in their own words and quickly find the operational context behind the work they're doing. Organizations can bring that experience to their teams while maintaining the access and governance controls they depend on. Chantrelle Nielsen, Principal PM Manager, Microsoft Bring operational data into the flow of work. The connector brings MongoDB Atlas to Microsoft Copilot through MongoDB's managed remote Model Context Protocol (MCP) server. When a user asks a relevant question, Copilot can query Atlas in real time - instead of relying on a static copy of the data. This creates a more direct path from a business question to the information needed to answer it, and helps users - who may not have MongoDB expertise - access and analyze live operational data through an AI assistant. Now, business users can use conversational prompts to: * Retrieve live business data without writing database queries. * Find and filter customers, transactions, products, orders, content, or operational events. * Get quick counts and key performance indicators, such as the number of delayed orders or high-value customers. * Summarize and rank data to identify top categories, products, regions, trends, averages, and other business insights. For example, a user might ask Copilot to summarize the open incidents in an Atlas cluster supporting a payments application, identify delayed orders, or describe the fields and data types in the customer collection for a loyalty service. By industry, a supply chain team can investigate inventory, shipment, and warehouse exceptions. A financial services team can explore customer records, fraud alerts, and transaction investigations. And a retailer can ask questions about orders, loyalty, customer service, and personalization. The connector can also help power business copilots and agents. Organizations can ground Copilot and other AI assistants in current MongoDB Atlas data for customer service, sales, operations, and decision support, bringing live operational context into the workflows where teams already work. Connect to live data without migrating or indexing it. Organizations using MongoDB Atlas do not need to migrate their operational data, re-platform their applications, or rebuild their integrations to use the connector. To do so, an administrator simply approves and enables the connector in the Microsoft 365 admin center. Users then sign in, and their existing Atlas permissions carry through to each query. MongoDB Atlas remains the system of record. The connector queries Atlas directly rather than indexing a copy of Atlas data into Microsoft 365, so the information returned to users reflects the current state of the underlying application data. This federated approach helps organizations connect their productivity layer to operational data while keeping that data in the environment where it is managed. Put governance into every interaction. Making operational data more accessible requires controls that organizations can understand and manage. The connector is designed to support that approach through: * Permission-aware access: Each query runs as the signed-in user and honors the permissions already defined in MongoDB Atlas. * Administrator control: Admins approve the connector and can manage deployment through the Microsoft 365 admin center. * Read-only access: The connector is designed for read-only interaction with Atlas data. * Auditability: Administrators can audit connector activity in Microsoft Purview. * No separate search index: The connector queries Atlas on demand instead of indexing a copy of Atlas data in Microsoft 365. Together, these controls give organizations a practical way to make operational information available through Copilot without giving up the governance model around the source data. A foundation for more productive work. AI-powered productivity depends on access to relevant business context. By connecting Microsoft Copilot and other AI assistants to live MongoDB Atlas data through a federated connection, MongoDB and Microsoft are helping organizations make operational information easier to use without adding a data-movement project or another application to maintain. Users can get answers, summaries, and insights from live data through natural language, while technical teams retain control over the underlying systems and permissions. For organizations already running MongoDB Atlas on Azure and Microsoft 365 Copilot, the connector provides a way to build on existing investments. Teams can explore high-value operational questions, validate measurable business outcomes, and develop repeatable patterns for bringing current data into everyday decisions. The result is a simpler path from question to context to action - grounded in the systems organizations already use and governed by the permissions they already have. Next steps. MongoDB Resources
Find jobs on Simplify and start your career today
Don't see your dream role? Check out thousands of other roles on Simplify.Browse all jobs
Industries
Company Size
5,001-10,000
Company Stage
IPO
Headquarters
New York City, New York
Founded
2007
Find jobs on Simplify and start your career today
Don't see your dream role? Check out thousands of other roles on Simplify.Browse all jobs