Riverqueue vs Supabase
Supabase scores higher on the AgentReady, 74/100 against 45/100. They differ on 17 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Riverqueue. Fast and reliable background jobs in Go.
Supabase. Supabase is an open-source Firebase alternative that provides a complete backend platform built on top of Postgres, offering database, authentication, storage, realtime, edge functions, and vector capabilities.
Where Riverqueue is ahead
Riverqueue passes search discoverable, clear canonical domain and public docs discoverable, and Supabase 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 and limits / constraints documented. Supabase misses those.
And on adopt, no mandatory sales call, free trial or free allowance, copyable quickstart, official typescript sdk and official python sdk. Supabase misses those.
Finally, on operate, canonical workflow succeeds and retry behavior documented. Supabase misses those.
Where Supabase is ahead
Supabase passes clear product positioning and mcp discoverable, and Riverqueue does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds understand: structured api reference and authentication documented. Riverqueue misses those.
And on adopt, mcp integration available. Riverqueue misses it.
What neither does
Both fail openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, self-service signup, programmatic credential creation, fast time to first request, structured, predictable output, machine-readable errors, idempotency support, rate-limit behavior predictable, observable execution, agent compatibility verified. 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. Supabase leads 100 to 73. Riverqueue misses clear product positioning, mcp discoverable; Supabase misses search discoverable, clear canonical domain, public docs discoverable.
Understand. Supabase leads 67 to 31. Riverqueue misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented; Supabase misses openapi / spec quality, pricing understandable, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.
Adopt. Supabase leads 63 to 48. Riverqueue misses self-service signup, agent-compatible signup flow, programmatic credential creation, fast time to first request, mcp integration available; Supabase misses self-service signup, 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.
Operate is whether an agent can run against it in production and recover when a call fails. Supabase leads 67 to 29. Riverqueue misses structured, predictable output, machine-readable errors, idempotency support, rate-limit behavior predictable, observable execution, agent compatibility verified; Supabase misses canonical workflow succeeds, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution, agent compatibility verified.
Pricing
Riverqueue does not publish a machine-readable starting price and has a free tier. Supabase does not publish one.
Signal by signal
| Signal | Riverqueue | Supabase |
|---|---|---|
| AgentReady | 45 | 74 |
| Discovery | 73 | 100 |
| Understanding | 31 | 67 |
| Adoption | 48 | 63 |
| Operability | 29 | 67 |
| Public API | Yes | Yes |
| MCP server | No | Yes |
| OpenAPI spec | No | Yes |
| CLI | Yes | Yes |
| llms.txt | Yes | Yes |
| Self-serve signup | Unknown | Unknown |
| Free tier | Yes | Unknown |
Which to pick
Riverqueue clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Riverqueue and Supabase. Alternatives to each: Riverqueue, Supabase.
An agent can fetch this as data: POST /v1/compare {"slugs": ["riverqueue", "supabase"]}