Compare

Heroku vs Railway

Railway scores higher on the AgentReady, 87/100 against 63/100. They differ on 16 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.

Railway. Railway is an all-in-one intelligent cloud provider that makes it easy to provision infrastructure, develop locally, and deploy to the cloud.

Where Heroku is ahead

Heroku passes search discoverable and public docs discoverable, and Railway 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. Railway misses those.

And on adopt, no mandatory sales call, copyable quickstart, official typescript sdk and official python sdk. Railway misses those.

Finally, on operate, canonical workflow succeeds, structured, predictable output and observable execution. Railway misses those.

Where Railway is ahead

Railway 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: self-service signup and free trial or free allowance. Heroku misses those.

And on operate, agent compatibility verified. Heroku misses it.

What neither does

Both fail openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, programmatic credential creation, fast time to first request, 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. Heroku leads 100 to 83. Heroku misses nothing; Railway misses search discoverable, public docs discoverable.

Understand is whether an agent can read the docs and work out how the API behaves before calling it. Railway leads 100 to 38. Heroku misses openapi / spec quality, authentication documented, pricing understandable, request examples provided, response examples provided, errors and status codes documented; Railway misses structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.

Adopt. Railway leads 88 to 65. Heroku misses self-service signup, programmatic credential creation, free trial or free allowance, fast time to first request; Railway misses no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, official typescript sdk, official python sdk.

Operate. Railway leads 78 to 47. Heroku misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified; Railway misses canonical workflow succeeds, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution.

Pricing

Heroku does not publish a machine-readable starting price. Railway does not publish one and has a free tier.

Signal by signal

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 Railway. Alternatives to each: Heroku, Railway.

An agent can fetch this as data: POST /v1/compare {"slugs": ["heroku", "railway"]}