Koyeb vs Northflank
Koyeb scores higher on the AgentReady, 57/100 against 46/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
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
Northflank. The runtime platform for AI-native companies.
Where Koyeb is ahead
Koyeb passes mcp discoverable, and Northflank 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. Northflank misses it.
And on adopt, no mandatory sales call, free trial or free allowance, official typescript sdk and mcp integration available. Northflank misses those.
Where Northflank is ahead
Northflank passes clear canonical domain, and Koyeb does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds operate: structured, predictable output. Koyeb misses it.
What neither does
Both fail llms.txt published, llms-full.txt / full agent docs, structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints 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. Koyeb leads 80 to 73. Koyeb misses clear canonical domain, llms.txt published, llms-full.txt / full agent docs; Northflank misses llms.txt published, llms-full.txt / full agent docs, mcp discoverable.
Understand. Koyeb leads 23 to 15. Koyeb misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; Northflank misses structured api reference, openapi / spec quality, authentication documented, pricing understandable, 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 50. Koyeb misses programmatic credential creation; Northflank misses no mandatory sales call, programmatic credential creation, free trial or free allowance, official typescript sdk, mcp integration available.
Operate. Northflank leads 47 to 35. Koyeb misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified; Northflank misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.
Pricing
Koyeb does not publish a machine-readable starting price and has a free tier. Northflank does not publish one.
Signal by signal
| Signal | Koyeb | Northflank |
|---|---|---|
| AgentReady | 57 | 46 |
| Discovery | 80 | 73 |
| Understanding | 23 | 15 |
| Adoption | 90 | 50 |
| Operability | 35 | 47 |
| Public API | Yes | Yes |
| MCP server | Yes | Unknown |
| OpenAPI spec | Unknown | Unknown |
| CLI | Yes | Yes |
| llms.txt | Unknown | Unknown |
| Self-serve signup | Yes | Yes |
| Free tier | Yes | Unknown |
Which to pick
Koyeb clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Koyeb and Northflank. Alternatives to each: Koyeb, Northflank.
An agent can fetch this as data: POST /v1/compare {"slugs": ["koyeb", "northflank"]}