Neon vs TiDB Cloud
Neon scores higher on the AgentReady, 90/100 against 65/100. They differ on 9 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Neon. The backend for apps and agents, built to scale on Lakebase Postgres.
TiDB Cloud. TiDB Cloud is a cloud-native distributed SQL database service that provides infrastructure for infinite agents and infinite data, with support for AI applications, vector search, and multi-modal data platforms.
Where Neon is ahead
Neon passes clear canonical domain, and TiDB Cloud does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds understand: pricing understandable. TiDB Cloud misses it.
Where TiDB Cloud is ahead
TiDB Cloud passes search discoverable and public docs discoverable, and Neon does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds adopt: no mandatory sales call and official typescript sdk. Neon misses those.
And on operate, canonical workflow succeeds, structured, predictable output and observable execution. Neon misses those.
What neither does
Both fail openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, programmatic credential creation, free trial or free allowance, fast time to first request, copyable quickstart, official python sdk, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable. If your agent needs any of those, you will be building it yourself either way.
Score, pillar by pillar
The AgentReady splits into four pillars, scored separately, because a product can be easy to find and still impossible to adopt.
Discover. Neon leads 100 to 93. Neon misses search discoverable, public docs discoverable; TiDB Cloud misses clear canonical domain.
Understand is whether an agent can read the docs and work out how the API behaves before calling it. Neon leads 83 to 38. Neon misses openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; TiDB Cloud misses openapi / spec quality, pricing understandable, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.
Adopt. Neon leads 100 to 65. Neon misses no mandatory sales call, programmatic credential creation, free trial or free allowance, fast time to first request, copyable quickstart, official typescript sdk, official python sdk; TiDB Cloud misses programmatic credential creation, free trial or free allowance, fast time to first request, copyable quickstart, official python sdk.
Operate. Neon leads 78 to 65. Neon misses canonical workflow succeeds, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution; TiDB Cloud misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable.
Pricing
Neon does not publish a machine-readable starting price. TiDB Cloud does not publish one.
Signal by signal
| Signal | Neon | TiDB Cloud |
|---|---|---|
| AgentReady | 90 | 65 |
| Discovery | 100 | 93 |
| Understanding | 83 | 38 |
| Adoption | 100 | 65 |
| Operability | 78 | 65 |
| Public API | Yes | Yes |
| MCP server | Yes | Yes |
| OpenAPI spec | Yes | Yes |
| CLI | Yes | Yes |
| llms.txt | Yes | Yes |
| Self-serve signup | Yes | Yes |
| Free tier | Unknown | Unknown |
Which to pick
TiDB Cloud clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Neon and TiDB Cloud. Alternatives to each: Neon, TiDB Cloud.
An agent can fetch this as data: POST /v1/compare {"slugs": ["neon", "tidbcloud"]}