Heroku vs Ollama
Heroku scores higher on the AgentReady, 63/100 against 59/100. They differ on 11 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.
Ollama. Ollama lets you use open models with your coding agents so you can spend less while keeping your data private.
Where Heroku is ahead
Heroku passes clear canonical domain and mcp discoverable, and Ollama does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds understand: limits / constraints documented. Ollama misses it.
And on adopt, no mandatory sales call and mcp integration available. Ollama misses those.
Finally, on operate, structured, predictable output. Ollama misses it.
Where Ollama is ahead
Ollama 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.
And on operate, agent compatibility verified. Heroku misses it.
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. 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 is whether an agent can find the product at all without being told it exists. Heroku leads 100 to 80. Heroku misses nothing; Ollama misses clear canonical domain, mcp discoverable.
Understand. Both sit at 38/100 here. Heroku misses openapi / spec quality, authentication documented, pricing understandable, request examples provided, response examples provided, errors and status codes documented; Ollama misses openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.
Adopt. Both sit at 65/100 here. Heroku misses self-service signup, programmatic credential creation, free trial or free allowance, fast time to first request; Ollama misses no mandatory sales call, programmatic credential creation, mcp integration available.
Operate. Ollama leads 53 to 47. Heroku misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified; Ollama misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable.
Pricing
Heroku does not publish a machine-readable starting price. Ollama starts at $0/mo and has a free tier.
| Heroku plans | Ollama plans |
|---|---|
| - | Free $0 |
| - | Pro $20/mo or $200/yr ($16.67/mo billed annually) |
| - | Max $100/mo |
| - | Team $500/mo |
| - | Enterprise Custom |
Signal by signal
| Signal | Heroku | Ollama |
|---|---|---|
| AgentReady | 63 | 59 |
| Discovery | 100 | 80 |
| Understanding | 38 | 38 |
| Adoption | 65 | 65 |
| Operability | 47 | 53 |
| Public API | Yes | Yes |
| MCP server | Yes | No |
| OpenAPI spec | Yes | Yes |
| CLI | Yes | Yes |
| llms.txt | Yes | Yes |
| 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 Ollama. Alternatives to each: Heroku, Ollama.
An agent can fetch this as data: POST /v1/compare {"slugs": ["heroku", "ollama"]}