Heroku vs Koyeb
Heroku scores higher on the AgentReady, 63/100 against 57/100. They differ on 10 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Heroku. Heroku is a fully managed cloud application platform (PaaS) for building, deploying, and scaling apps.
Koyeb. Developer-friendly serverless platform designed to let businesses and developers easily deploy reliable and scalable applications globally, with high-performance infrastructure for AI inference, sandboxes, and microservices on CPUs, GPUs, and accelerators
Where Heroku is ahead
Heroku passes clear canonical domain, llms.txt published and llms-full.txt / full agent docs, and Koyeb 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 limits / constraints documented. Koyeb misses those.
And on operate, structured, predictable output. Koyeb misses it.
Where Koyeb is ahead
Koyeb passes pricing understandable, and Heroku does not. That is understand, whether an agent can read the docs and work out how the API behaves before calling it.
It also holds adopt: self-service signup, free trial or free allowance and fast time to first request. Heroku misses those.
What neither does
Both fail openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, programmatic credential creation, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, 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. Heroku leads 100 to 80. Heroku misses nothing; Koyeb misses clear canonical domain, llms.txt published, llms-full.txt / full agent docs.
Understand. Heroku leads 38 to 23. Heroku misses openapi / spec quality, authentication documented, pricing understandable, request examples provided, response examples provided, errors and status codes documented; Koyeb misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.
Adopt is whether an agent can get a key and make its first successful call without a human in the loop. Koyeb leads 90 to 65. Heroku misses self-service signup, programmatic credential creation, free trial or free allowance, fast time to first request; Koyeb misses programmatic credential creation.
Operate. Heroku leads 47 to 35. Heroku misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified; Koyeb misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.
Pricing
Heroku does not publish a machine-readable starting price. Koyeb does not publish one and has a free tier.
Signal by signal
| Signal | Heroku | Koyeb |
|---|---|---|
| AgentReady | 63 | 57 |
| Discovery | 100 | 80 |
| Understanding | 38 | 23 |
| Adoption | 65 | 90 |
| Operability | 47 | 35 |
| Public API | Yes | Yes |
| MCP server | Yes | Yes |
| OpenAPI spec | Yes | Unknown |
| CLI | Yes | Yes |
| llms.txt | Yes | Unknown |
| Self-serve signup | Unknown | Yes |
| Free tier | Unknown | Yes |
Which to pick
Heroku clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Heroku and Koyeb. Alternatives to each: Heroku, Koyeb.
An agent can fetch this as data: POST /v1/compare {"slugs": ["heroku", "koyeb"]}