Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Compose website screenshot

Compose

Compose (Compose, Inc., compose.io) was a database-as-a-service (DBaaS) provider that offered production-ready, auto-scaling, hosted deployments of open-source databases — MongoDB, PostgreSQL, Redis, Elasticsearch, RabbitMQ, RethinkDB, ScyllaDB, etcd, MySQL, and Disque — each provisioned with high availability, automated backups, and a REST API for programmatic management. Founded in 2010 as MongoHQ and rebranded to Compose in 2014, the company was backed by DCVC (Data Collective) and was acquired by IBM in 2015, after which the offering was folded into IBM Cloud as "IBM Compose" / IBM Cloud Databases. The standalone Compose service and its developer surface (compose.com, compose.io, apidocs.compose.com) have since been deprecated and taken offline. This profile documents the surviving, verifiable first-party artifacts — the archived GitHub organization at github.com/compose, the official Go SDK (gocomposeapi) wrapping the Compose REST API, and the official command-line tools (bach, cocli).

human only

Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.

Kin Score

Compose is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Compose scores 10.0/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 10.0/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 2.6 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

Resources

Every other property we hold for Compose — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Compose is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.

← All providers · Data indexed from github.com/api-evangelist/compose · machine-readable index on apis.io