NoSQL Database-aaS. Acquired by IBM in 2014. Now IBM Cloud Data…
Turn this teardown into a decision-ready prompt for ChatGPT, Claude, or your agent.
If you only have a few minutes to spare, here’s what investors, operators, and founders should know about Cloudant (S08).
Cloudant turned distributed-data problems from particle physics into a managed document database. Founded in Cambridge in 2008 by MIT physicists Michael Miller, Alan Hoffman, and Adam Kocoloski, the Summer 2008 YC company combined Apache CouchDB compatibility with its distributed BigCouch layer.[1]
IBM announced its acquisition of Cloudant in February 2014 to extend its cloud, analytics, mobile, and big-data portfolio.[2] Terms were not disclosed. This was a strategic purchase of a viable product, not a shutdown. Cloudant remains an active IBM service based on CouchDB-compatible APIs and replication.[3] The acquisition mechanism was cloud-portfolio integration: Cloudant supplied a developer data layer; IBM supplied infrastructure, enterprise distribution, and adjacent analytics.
Miller, Hoffman, and Kocoloski encountered the problem while working with multi-petabyte Large Hadron Collider datasets. Existing research tools did not provide the distributed, fault-tolerant data layer they needed, so they built one.[1]
The leap from physics to company was a recognition that web and mobile developers faced the same class of operating burden at smaller scale. Applications needed data available across machines and locations, but teams did not want to configure servers, networks, load balancers, upgrades, replication, and tuning themselves.
Cloudant joined YC in 2008 and launched its hosted service in 2010. It combined CouchDB's JSON document model and APIs with BigCouch, Cloudant's distributed clustering layer.[4] The service arrived before managed databases became a routine cloud primitive.
No fetched founder interview supplies safe verbatim founder quotations. Rather than reconstruct language from company summaries, this report uses the observed product and transaction record.
Cloudant was a managed JSON document database. Application teams used CouchDB-compatible APIs while Cloudant handled servers, networking, load balancing, upgrades, tuning, resilience, and capacity.[8]
The product combined multi-master distribution with replication, mobile and offline synchronization, search, MapReduce views, and geospatial indexing.[9] BigCouch distributed CouchDB-style storage across nodes, addressing scale and fault tolerance while preserving a familiar application interface.
Open compatibility mattered strategically. Cloudant open-sourced BigCouch and contributed clustering work toward Apache CouchDB.[6] Customers were buying operations and scale rather than accepting an entirely proprietary data model.
IBM's current documentation says Cloudant can replicate continuously with CouchDB-family databases, while warning that replication creates internal calls that can affect performance or cost.[10] Compatibility therefore enables portability but does not guarantee identical indexes, conflict handling, security, attachments, query performance, or operating cost.
Cloudant targeted developers building scalable web and mobile applications who wanted a document model and distributed data without operating database clusters. Enterprise customers also valued support, resilience, and IBM integration.
No audited revenue, margin, churn, retention, customer concentration, or market-size data was observed. Cloudant reported 1,300 users and ten paying customers at launch.[4] YC's current profile says thousands of developers and hundreds of customers used it before acquisition, but those are directory claims rather than audited acquisition-date metrics.[1]
Read the complete post-mortem, the rebuild playbook, and the exact reasons Cloudant is still worth studying now.