Koyeb by Koyeb

# Fix list: Koyeb

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/koyeb, the October 2026 research run, assessed 1 October 2026. Grade D, 47 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on Koyeb: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Payments & pricing, 20 out of 100, up to 10 more on the total

Why it scored 20: No machine payment protocol (0). Per-hour GPU and per-second CPU prices published without a login (20). Starter is closed to new sign-ups and Pro costs $29 a month, so there's no free compute tier; the only free item is a 5-hour Postgres database (0). Signup is a browser flow (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 2. Schema & documentation, 41 out of 100, up to 9.6 more on the total

Why it scored 41: The API reference at koyeb.com/docs/reference/api renders in the browser and the official Go client is generated with docs for every endpoint, but we found no downloadable OpenAPI file (10 of 25). No llms.txt (koyeb.com/docs/llms.txt returns 404) and no Markdown twins (0). Guides on scale to zero and autoscaling say when to use each setting; the API reference wasn't readable to us (10). Typed parameters with required bodies, but service types and statuses are free strings with no listed values (8). CLI examples throughout; no documented error responses found (5). /v1 paths, but the public changelog stopped on 27 February 2026 (8).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 3. Security & auth, 50 out of 100, up to 8.8 more on the total

Why it scored 50: Personal access tokens and organisation tokens sent as Bearer; no scopes found (20). RBAC only on Enterprise; no read-only token (5). Runs your own containers and returns their output (10). Audit logs only on Enterprise (10). SOC 2 and ISO 27001 listed on the pricing page; no security.txt, no disclosure policy or bug bounty found (5).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 4. Reliability, 60 out of 100, up to 8 more on the total

Why it scored 60: Instatus page at status.koyeb.com with 90-day uptime per component (API 99.96, Build 99.75 per cent) and history (20). Five incidents in September 2026, three of them marked major outage by Koyeb but all under an hour (authentication down 6 and 12 minutes on 21 and 22 September, API timing out for 44 minutes on 23 September) and two degraded on 29 September; none in August. Under our rule that a major outage lasts an hour or more, that's minor incidents only (20). No API rate limits found in the docs we could read (0). No 429 or backoff guidance found (0). 99.9 per cent uptime SLA on Pro and Scale, 99.99 on Enterprise (10). Services and GPUs are GA; light sleep is preview (10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 5. Agent ergonomics, 56 out of 100, up to 7.2 more on the total

Why it scored 56: List endpoints take `limit` and `offset` plus filters on name, type, status, region and ID (15). Same filters give pagination and output-size control (20). No error codes or messages documented that we could find (5). `dry_run` on create and update validates a service before anything is deployed; no idempotency keys (8). Sensible scale-to-zero defaults (5 minutes idle), but the only official clients are the CLI and the Go library (8).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 6. Maintenance & community, 23 out of 100, up to 6.7 more on the total

Why it scored 23: The newest CLI release is v5.10.2 on 12 May 2026, 142 days before this check, and the changelog's last entry is 27 February 2026 (10). No releases or changelog entries in the last 90 days (0). Closed service with a stalled changelog and a community forum (5 of 15). Only the CLI and a Go client (5). Package health unknown, no CI status checked (3).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## 7. Transparency & trust, 68 out of 100, up to 2.8 more on the total

Made of editorial 50, provenance 86.

Why it scored 68: Closed service under a French-law MSA; the CLI and Go client are Apache-2.0 (20). An MSA and a DPA are published, but the footer's privacy link points at the DPA and we found no separate privacy policy or retention periods (15). The Mistral agreement was announced on 17 February 2026 with no dated migration or end-of-life notice since (5). Regions are named on the status page (North America, Europe, Asia-Pacific); subprocessors not checked (10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Domain age: koyeb.com, registered 2019-03-11 (7 years) (11 of 15)
- security.txt: not found (0 of 10)

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- The previous listing said CLI v5.12.0 shipped on 10 September 2026; both the CHANGES.md file and the releases page we read end at v5.10.2 on 12 May 2026, so we corrected `lastRelease`.
- We couldn't read the API reference (client-rendered) or find a downloadable OpenAPI file, so rate limits and error formats may exist and be unscored.
- We didn't check whether the DPA lists subprocessors.
- Whether a card is required at signup isn't stated on the pricing page.

## Weaknesses

- Changelog silent since 27 February 2026 and no CLI release since 12 May 2026
- No free compute tier; Starter closed after the Mistral AI agreement
- No llms.txt, no downloadable OpenAPI file, no documented rate limits or error codes
- Audit logs and RBAC only on Enterprise, and tokens have no scopes
- Platform due to fold into Mistral Compute with no dated migration plan

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- Pass `dry_run` on service create or update to validate the definition before anything deploys
- Page service lists with `limit` and `offset` and filter by `statuses` instead of fetching everything
- Expect the first request after deep sleep to take 1 to 5 seconds and retry once with a timeout
- Set `--min-scale 0` on GPU services so idle instances stop billing
- Re-check the Mistral transition before building anything long-lived on it

## What the review panel asked for

- say whether signup needs a card
- publish dated migration terms
- Publish rate limits and error codes
- Publish a downloadable OpenAPI file

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.