MongoDB, Inc. (MDB)

MongoDB began in 2007 when a New York-based software consulting firm named 10gen was struggling to build scalable applications for its clients. The traditional relational databases that dominated at the time—Oracle, SQL Server, MySQL—organized data into rigid tables and rows, and restructuring that schema when application requirements changed was laborious. The 10gen team decided to build their own database engine optimized for how applications actually work: storing data as flexible documents rather than rigid tables, allowing developers to evolve their schema without painful migrations. That database became MongoDB, and over time it became clear that the database was more valuable than the consulting business that birthed it.

The company released MongoDB as open-source software in 2009, which meant anyone could download it, use it, and modify it without paying MongoDB a cent. This was strategically brilliant. It meant that developers at thousands of startups, enterprises, and organizations large and small could experiment with MongoDB for free. Open-source adoption drove network effects: the more developers used MongoDB, the more tutorials and third-party tools were written for it, which made it easier for new developers to adopt it, which meant more enterprises considered it for production systems. By the mid-2010s, MongoDB had become one of the most popular databases in the world, especially among web and mobile application developers who valued its flexibility and ease of use.

The open-source model created a problem, though: MongoDB was free, and the company was not making money from millions of users. In 2014, MongoDB (then still 10gen) had to articulate a business model that would monetize that massive installed base without betraying the open-source community that had embraced the database. The solution was to position MongoDB as a B2B software company that charged for enterprise features, hosting, and support. The company released MongoDB Enterprise, a version with advanced features like security and compliance capabilities, and offered long-term support. More significantly, it began investing in MongoDB Atlas, a cloud-hosted version of MongoDB that the company manages on behalf of customers. Rather than asking customers to run MongoDB themselves, Atlas meant customers could pay MongoDB monthly to store their data in the cloud, worry-free. This was a fundamentally more profitable model than one-time software licenses.

MongoDB went public in 2017 with the ticker MDB. At the time, it was still very much a growth-stage company burning cash to acquire customers and build features. The investor case was that MongoDB occupied a unique position: it had unmatched adoption among software developers, it was addressing a growing market of organizations moving applications to the cloud, and it had a clear path to profitability through the Atlas subscription model and enterprise services.

Today MongoDB generates revenue from two main sources. The first is the MongoDB Atlas subscription: customers pay monthly fees based on how much data they store, how much compute power they use, and what features they require. The pricing model is consumption-based, which means as a customer’s application grows and stores more data, MongoDB’s revenue from that customer grows automatically. This is a classic software-as-a-service model, and it is highly profitable because once the infrastructure is built, adding more customers costs very little incremental overhead. The second revenue source is MongoDB Enterprise licenses and support: organizations that run MongoDB on their own infrastructure or need advanced security and compliance features pay for licenses and professional support. This is a smaller but still meaningful revenue stream.

MongoDB competes in the database software market against an array of formidable opponents. The old guard—Oracle, IBM, Microsoft—still defend massive installed bases of relational databases and will not yield easily. Newer cloud-native database companies like Elastic and DataStax pursue similar strategies to MongoDB’s. Cloud providers themselves—Amazon AWS, Google Cloud, Microsoft Azure—offer their own database services and have every incentive to guide customers away from MongoDB to proprietary alternatives. Yet MongoDB has advantages that have allowed it to compete: a genuinely large developer base that prefers its flexible schema, a strong open-source community, excellent documentation, and a business model that aligns its interests with its users—MongoDB makes more money as its customers’ applications grow and store more data.

The business model produces durable economics. Each customer that signs up for MongoDB Atlas represents an initial cost (sales and marketing to acquire them, infrastructure to serve them) and then a stream of revenue that typically grows year after year (as their application scales), with a gross margin (revenue minus cost of hosting and serving that customer) that is extremely high—often above 70 percent. That operating leverage is the signature of a successful software company: once you have sold a customer on your product, you can serve them additional volume at minimal marginal cost.

But MongoDB faces real constraints. Cloud-native databases are a competitive category, and the largest technology companies in the world have incentives to offer their own. Amazon’s DynamoDB, Google’s Firestore, and Microsoft’s Cosmos DB all try to capture MongoDB use cases within their own cloud platforms. The rise of artificial intelligence and machine learning has created new database requirements—vector databases for embedding data used in AI training, analytics warehouses for massive datasets—and MongoDB is one of many companies trying to serve these needs. The larger risk is that application development itself may be moving toward different architectural patterns (edge computing, serverless functions) that reduce the share of application logic running on traditional databases.

From a user perspective, MongoDB faces the eternal challenge of any database company: switching costs are real and migration is painful. Once an organization has built applications on MongoDB, moving those applications to a different database is expensive and risky. That is good for MongoDB’s long-term retention of customers but makes it hard to grow by converting existing users from competitors. MongoDB’s growth depends on winning new application projects at new companies, and on existing customers expanding their usage over time.

The financial story that investors track is straightforward. MongoDB reports annual recurring revenue (the annualized value of subscriptions that customers have committed to), net revenue retention (the rate at which existing customers increase their spending year over year), and operating margins (whether the company is profitable or still losing money on an operating basis). For years MongoDB was unprofitable, investing more cash into product development and sales than it earned in revenue. The question was whether subscription growth would eventually produce profits before the company ran out of cash. By 2023 and beyond, the company was approaching profitability, which validated the hypothesis. The investment case is that MongoDB has a durable moat—its popularity with developers—and a path to industry-leading margins if it executes well on product and avoids being undercut by cloud-provider alternatives.

Understanding MongoDB as an investment requires reading the quarterly earnings reports (SEC CIK 0001441816), paying attention to trends in annual recurring revenue and net revenue retention (both indicate the health of the customer base), and tracking the company’s path to profitability or already-achieved profitability. The quarterly earnings calls with management provide color on competitive wins and losses, product roadmap, and how customers are responding to new features. Because MongoDB is a business-to-business software company selling to developers and CIOs, its success is ultimately about whether it can be the database that the smartest development teams choose to build on, and whether those teams’ organizations will continue to pay for the convenience and infrastructure MongoDB provides.