Overview

Compose — originally MongoHQ — was a Database-as-a-Service (DBaaS) company founded in 2010 and backed by Y Combinator (S11). It built managed hosting infrastructure for MongoDB, and later for Elasticsearch, Redis, RethinkDB, and PostgreSQL, letting developers deploy and scale production databases without managing the underlying operations. At its peak, the company served 3,600 paying companies and had spun up over 100,000 databases across AWS, DigitalOcean, and SoftLayer. ^[1]

Compose was not a failure in the conventional sense. It was profitable, growing, and operationally sound when IBM acquired it in July 2015 for an undisclosed sum. The real story is what happened next: IBM absorbed the product into its Cloud Data Services group, failed to scale it as a competitive offering against hyperscaler managed database services, and ultimately deprecated it entirely — disabling all instances on March 1, 2023. ^[2]

The outcome illustrates a structural trap for infrastructure startups: acquisition by a large enterprise is not a preservation strategy when the acquirer lacks the agility to compete in a market being redefined by AWS, Google, and Microsoft. Compose's customer base was extracted, its brand was retired, and its founder left IBM after eight months.

Founding Story

MongoHQ was founded in 2010 by Ben Wyrosdick and Jason McCay, two developers who had encountered firsthand the friction of deploying MongoDB in production. ^[3] Their founding insight was narrow and precise: developers were excited about MongoDB's document model and its promise of faster iteration, but the operational burden of running it reliably — provisioning, replication, backups, scaling — was absorbing engineering time that should have gone toward product. The solution was to take that burden entirely off the developer's plate.

Kurt Mackey came to the company through an unusual path. He was an early MongoHQ customer before he was a co-founder. With a background as technical director at Ars Technica (under Condé Nast) and prior to that as director of research and development at ServerCentral, Mackey brought infrastructure operations experience that was directly relevant to what MongoHQ was building. ^[4] When Wyrosdick and McCay entered Y Combinator's Summer 2011 batch, Mackey joined them as co-founder and CEO. ^[5]

Mackey later described the founding moment with clarity: "We basically started as a MongoDB hosting company at a very interesting time, because all these people were trying out this hot new database that helped them ship stuff faster." ^[6] The timing was not accidental. MongoDB had been released publicly in 2009, and by 2010-2011 it was generating significant developer interest as part of the broader NoSQL movement. The company was positioned at the intersection of two concurrent trends: the adoption of non-relational databases and the migration of infrastructure to cloud providers.

Y Combinator participation in S11 provided approximately $417K in seed capital, early network access, and the validation that comes with acceptance into the batch. ^[7] The company was headquartered in San Mateo, California, with an additional office in Birmingham, Alabama — an unusual geographic split that likely reflected where the founding team was based. ^[8]

The initial product was deliberately narrow: managed MongoDB hosting on AWS. There was no attempt to build a broad platform from day one. The founding team's operational depth — Mackey in particular had run infrastructure at scale for media properties — meant the product was built by people who understood the problem from the inside. This was not a naive bet on a trend but an informed read on a specific developer pain point.

The major strategic inflection came in August 2014, when the company rebranded from MongoHQ to Compose and simultaneously launched Elasticsearch as a service. Mackey explained the name: "In computer science, composition is the process of combining existing functions into a new function that solves new problems." ^[9] The rebrand signaled a recognition that single-database dependency was an existential risk — a pivot that would prove strategically prescient when MongoDB launched its own managed service, Atlas, in 2016.