Head to head · GPU compute · October 2026 research run

Koyeb vs Modal

Modal scores 63.9 (B) on agent readiness against Koyeb's 47.8 (D), and leads in 6 of 7 scored categories. Both do gpu compute.

Best GPU and serverless compute for AI workloads · All 256 gpu compute comparisons

Which one, for what

Koyeb D

Best for Teams that want low-cost H100, H200 or B200 containers with scale to zero and an SLA, deployed from Git or an image.

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

Public changelog silent since 27 February 2026, so API changes surface only through CLI and SDK releases

Modal B

Best for Python teams that want GPU functions, batch jobs and HTTP endpoints from one decorator with scale to zero.

Ahead on

  • Reliability, 70 against 50
  • Schema & documentation, 70 against 31
  • Agent ergonomics, 57 against 51
  • Security & auth, 68 against 50
  • Maintenance & community, 85 against 73
  • Transparency & trust, 71 against 64

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 4.0 against 3.5 out of 5

Watch for

No REST API or OpenAPI spec for deploying or invoking Functions

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation Modal +39

Koyeb 31

No downloadable OpenAPI file. The API reference at koyeb.com/docs/reference/api renders only by script, and the generated docs in the Go and Python client repositories aren't a published contract (0, was 10). No llms.txt (www.koyeb.com/llms.txt and /docs/llms.txt both 404) and no Markdown twins (0). Guides on scale to zero and autoscaling say when to use each setting (10, held). Typed parameters with required bodies in the Go client's docs, but service types and statuses are free strings with no listed values (8, held). CLI examples throughout; no documented error responses found (5, held). /v1 paths, but the public changelog stopped on 27 February 2026 (8, held). 0 + 0 + 10 + 8 + 5 + 8 = 31.

Modal 70

No HTTP API for deploying, so no OpenAPI; the contract is the typed Python SDK with a generated reference (10 of 25). llms.txt at modal.com/llms.txt (10). Guides say when to pick a Function, a web endpoint, a Server or an Endpoint, and when to use memory snapshots (15). Python type hints throughout, but GPU names, regions and plan limits are plain strings (10). Large example gallery; errors are typed Python exceptions without a published HTTP error table (10). Dated SDK release notes (15). 10+10+15+10+10+15 = 70.

Reliability Modal +20

Koyeb 50

Graded on the hosted lines for its platform API. Instatus page at status.koyeb.com with components (API, Control Panel, Build / Provisioning and one per region) and history back to 2022 in its feed (20). Since 7 August the feed holds nine incidents and one maintenance. The eight in September each name one region, one GPU type or some customers, or ran 6 to 52 minutes (8, 11, 15, 21, 22 and 23 September and two on 29 September). On 16 October Koyeb posted a separate incident, "The ongoing maintenance is causing API to fail with 500", on the API, Control Panel and Build components for 24 minutes, inside a maintenance window announced the day before for 07:00 to 08:00 UTC with "max 10m unavailability". The status page labels it an incident and the outage ran past the unavailability announced, so it counts as an incident, and the API failing with 500 is errors across the board, one major outage (10). No API rate limits found in the docs we could read (0). No 429 or backoff guidance found (0). The Scale plan lists a 99.9 per cent uptime SLA and Enterprise 99.99, with an SLA document at /docs/legal/sla setting service credits (10). Services and GPUs are generally available; light sleep is a preview (10). 20 + 10 + 0 + 0 + 10 + 10 = 50.

Modal 70

Status page at status.modal.com (Better Stack) with per-component history and RSS (20). The feed, re-read on 2 November 2026, lists eight incidents from 4 August and an announced control plane maintenance (26 October to 2 November). Slow .spawn() calls for some callers for about 15 minutes (19 August), function latency for 11 minutes (26 August), elevated errors on an endpoint that reads application and volume contents for about 2 hours (4 September), a 14-minute dashboard and sandbox outage (16 September), degraded worker networking for functions and sandboxes (5 October), two incidents on the Kimi K3 shared endpoint only (14 October), and a 2-minute period when 30 to 40 per cent of web function requests failed (19 October). Each hit one product or part of the traffic, or degraded it, and none took a core service down for an hour, so minor only, as modal-sandboxes reads the same feed (20). Web Functions and Function calls are rate limited to 200 a second with a 5-second burst, and plans cap containers at 100 and 5,000 and concurrent GPUs at 10 (Starter) and 50 (Team) (15). Excess requests get a 429, with no Retry-After or backoff guidance for callers; Functions take a documented retry policy with exponential backoff through modal.Retries (5). No SLA on the pricing page (0). Functions, web endpoints and Servers are GA (10). 20+20+15+5+0+10 = 70.

Security & auth Modal +18

Koyeb 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). ISO 27001 and SOC 2 listed on the pricing page for Enterprise; www.koyeb.com/.well-known/security.txt is 404 and no disclosure policy, SECURITY.md or bug bounty found, so a bare certification claim (5). 20 + 5 + 10 + 10 + 5 = 50.

Modal 68

Token ID and secret pairs from modal token new, revocable and able to carry a TTL, plus invoke-only proxy tokens for web endpoints and Servers; no scopes on the main token (25). RBAC only on Enterprise, and web endpoints are open to anyone with the URL until you add proxy auth (8). Runs your own code and returns its output (10). Audit logs only on Enterprise (10). Disclosure to security@modal.com with stated response times (24 hours for critical), a private HackerOne programme, SOC 2 Type 2 and a HIPAA BAA on Enterprise; no security.txt (404 on 2 November), and no OSV advisories for the modal PyPI or npm packages on 2 November (15).

Maintenance & community Modal +12

Koyeb 73

The newest release is the Python SDK koyeb-sdk v1.5.6, tagged 20 October 2026, 16 days before this check (30). Five releases since 7 August carry code changes, CLI v5.11.0 (27 August) and v5.12.0 (10 September), and Python SDK v1.5.2 (27 August), v1.5.5 (29 September) and v1.5.6 (20 October) (20). The 1 October check read the CLI as ending at v5.10.2 and missed both. The public changelog still ends on 27 February 2026. A community forum and a stalled web changelog, and GitHub issues weren't readable (5 of 15, held). Current official SDKs in Go (client updated 10 October 2026) and Python (15, was 5). CI workflows exist in both repositories, but package health and CI results weren't readable (3, held). 30 + 20 + 5 + 15 + 3 = 73.

Modal 85

Python SDK 1.6.3 on 27 October 2026 per the release notes (30). Six dated Python SDK releases from 4 August (1.5.4 on 12 August, 1.5.5 on 28 August, 1.6.0 on 28 September, 1.6.1 on 3 October, 1.6.2 on 15 October and 1.6.3 on 27 October) (20). The client is open source in modal-labs/modal-client, but its issues and replies can't be read from a clone and github.com answers 403, so responsiveness stays at the 1 October reading, dated release notes and community Slack (10). Python is current, and the JavaScript and Go SDKs (tagged 0.11.1, beta) are in the same repository (15). CodeQL and unit tests on main per the 1 October check, and the Python package supports current runtimes, Python 3.15 since 1.6.2 (10). 30+20+10+15+10 = 85.

Transparency & trust Modal +7

Koyeb 64

The editorial half. Closed service under the French-law Master Services Agreement of 28 June 2024; the CLI and Go client are Apache-2.0 (20). An MSA and a DPA are published, the MSA deletes customer data at the end of the reversibility period, 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 Starter closed to new sign-ups, and no dated migration or end-of-life notice since (5, held). Regions are named on the status page (North America, Europe, Asia-Pacific); subprocessors not checked (10). 20 + 15 + 5 + 10 = 50.

Modal 71

Closed service; the Python client is Apache-2.0 (20). Retention is spelled out per product on the security page. Function inputs and outputs up to 7 days, logs 1 day on Starter and 30 on Team, function memory snapshots 30 days, sandbox memory snapshots 7 days, metadata for the account's lifetime, zero retention on inference Endpoints, and volumes and images until you delete them. A DPA sits in the trust centre (25). The 1.1.0 release notes say breaking changes for outstanding deprecations come only in 1.Y.0 releases, and releases give deprecation warnings first (1.6.2 deprecates .update_autoscaler()), with no stated notice period (15). The data residency guide says where each product runs and stores data and which regions can be pinned. The security page says the subprocessor list is in the trust centre at trust.modal.com, which didn't render for us (10). 20+25+15+10 = 70.

Agent ergonomics Modal +6

Koyeb 51

List endpoints take limit and offset plus filters on name, type, status, region and ID, per the Go client's docs (15). The same filters give pagination and output-size control (20). No error codes or messages documented that we could find (0, was 5 with nothing behind it). dry_run on create and update validates a service before anything deploys; no idempotency keys (8, held as partial). Sensible scale-to-zero defaults (5 minutes idle) and official clients in Go and Python, but required parameters weren't readable in the script-drawn reference (8, held as partial). 15 + 20 + 0 + 8 + 8 = 51.

Modal 57

No MCP server or REST list endpoints to size; the CLI's modal app list and modal function stats are compact (10). Filtering is per app and per function in the CLI, with no pagination contract (10). Typed exceptions in the SDK, but web endpoints return your own status codes (12). .spawn() returns a call ID to poll, and Functions accept a retry policy; no idempotency keys (10). Scale to zero and a 60-second scale-down by default, and official SDKs in Python, JavaScript and Go (15).

Score by category

CategoryWeightKoyebModalEdge
Reliability16%5070Modal +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3170Modal +39
Agent ergonomics13%5157Modal +6
Security & auth14%5068Modal +18
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7385Modal +12
Transparency & trust7%6471Modal +7
Negative events≤1500
TotalD 47.8/100B 63.9/100

Facts side by side

FactKoyebModal
KindPlatformPlatform
VendorKoyebModal
Hosted endpointhttps://app.koyeb.com/v1no (local only)
TransportsHTTP
AuthTokenAPI key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-202026-10-27
Terms last updatedno date given2026-05-01
Privacy policy last updatedno date given2023-05-17
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity72 stars514 stars, 941k npm/wk, 10.1M PyPI/wk
Agent reviews3.5/5 (2)4/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Modal higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Koyeb

Koyeb publishes per-second GPU prices without a login, from $0.50 an hour for an RTX 4000 SFF Ada to $2.50 for an H100, with an SLA document from the Scale plan. It has no downloadable OpenAPI file, documented rate limits or error codes, and no free compute plan, and its public changelog has been silent since 27 February 2026.

Modal

Scale to zero by default, per-second billing and about one-second container boots from a Python decorator, with retention stated per product. There's no REST API or OpenAPI spec for deploying or invoking Functions, web endpoints are public until proxy auth is added, and a payment method must be on file even for the $30 monthly credit.

Before you call either

Koyeb

  1. Pass dry_run on service create or update to validate the definition before anything deploys
  2. Page service lists with limit and offset and filter by statuses instead of fetching everything
  3. Expect the first request after deep sleep to take 1 to 5 seconds and retry once with a timeout
  4. Set --min-scale 0 on GPU services so idle instances stop billing
  5. Read the CLI's CHANGES.md and the Python SDK tags for API changes, since the web changelog stopped in February 2026

Modal

  1. Create a proxy token and require it on every web endpoint before sharing the URL; endpoints are public by default
  2. Pass a list to gpu= (for example ["H100", "A100-80GB"]) so a job still runs when the first choice is unavailable
  3. Set scaledown_window and min_containers explicitly; the defaults are 60 seconds and 0
  4. Use .spawn() and poll the call ID for long work instead of holding a web request open
  5. Keep web endpoint traffic under 200 requests a second or ask Modal to raise the limit

Questions

Which is better for AI agents, Koyeb or Modal?

Modal scores 63.9 (B) on agent readiness against Koyeb's 47.8 (D), and leads in 6 of 7 scored categories.

Other comparisons with Koyeb or Modal

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.