Heroku vs SuperTokens
Heroku scores higher on the AgentReady, 63/100 against 54/100. They differ on 8 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.
SuperTokens. Open source user authentication platform that helps developers build fast, maintain control, and reduce costs.
Where Heroku is ahead
Heroku passes structured api reference and limits / constraints documented, and SuperTokens 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: agent-compatible signup flow. SuperTokens misses it.
And on operate, structured, predictable output and observable execution. SuperTokens misses those.
Where SuperTokens is ahead
SuperTokens passes authentication documented and 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: free trial or free allowance. Heroku 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, 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.
Understand. Heroku leads 38 to 31. Heroku misses openapi / spec quality, authentication documented, pricing understandable, request examples provided, response examples provided, errors and status codes documented; SuperTokens misses structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.
Adopt. Heroku leads 65 to 60. Heroku misses self-service signup, programmatic credential creation, free trial or free allowance, fast time to first request; SuperTokens misses self-service signup, agent-compatible signup flow, programmatic credential creation, fast time to first request.
Operate is whether an agent can run against it in production and recover when a call fails. Heroku leads 47 to 24. Heroku misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified; SuperTokens misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution, agent compatibility verified.
Pricing
Heroku does not publish a machine-readable starting price. SuperTokens starts at $0.02/MAU and has a free tier.
| Heroku plans | SuperTokens plans |
|---|---|
| - | Cloud $0.02 per MAU |
| - | Self-hosted Free and open source |
Signal by signal
| Signal | Heroku | SuperTokens |
|---|---|---|
| AgentReady | 63 | 54 |
| Discovery | 100 | 100 |
| Understanding | 38 | 31 |
| Adoption | 65 | 60 |
| Operability | 47 | 24 |
| Public API | Yes | Yes |
| MCP server | Yes | Yes |
| OpenAPI spec | Yes | Unknown |
| CLI | Yes | Yes |
| llms.txt | Yes | Yes |
| Self-serve signup | Unknown | Unknown |
| 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 SuperTokens. Alternatives to each: Heroku, SuperTokens.
An agent can fetch this as data: POST /v1/compare {"slugs": ["heroku", "supertokens"]}