Head to head · GPU compute · October 2026 research run
Beam vs Koyeb
Beam scores 57.4 (C) 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
Beam C
Best for Python teams and agents running bursty GPU functions, sandboxes or persistent dev VMs on consumer or PCIe cards, with the option to self-host the same runtime.
Ahead on
- Reliability, 55 against 50
- Schema & documentation, 58 against 31
- Agent ergonomics, 58 against 51
- Security & auth, 65 against 50
- Maintenance & community, 85 against 73
- Transparency & trust, 80 against 64
Also in its favour
- Open source
Watch for
No free plan; the Developer plan costs $20 a month, with $20 of credits
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
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
Public changelog silent since 27 February 2026, so API changes surface only through CLI and SDK releases
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 Beam +27
Beam 58
Two Swagger files generated from protobuf (gateway and pods) still sit under the API reference and in llms.txt, with typed bodies and a shared error schema but almost no operation summaries; the workspace REST API at app.beam.cloud/api/v1 is a route table with no spec (15 of 25). llms.txt with .md pages (10). The guides say when to use what (endpoints for work under 180 seconds, task queues beyond), the generated specs don't (10). Typed request bodies with required fields and some enums, and a typed Python SDK (10). Plenty of examples; errors are an rpcStatus object, and the gateway can return HTTP 200 with ok: false, which the REST page now states (8). Versioned SDK releases, and a changelog linked from the site footer whose newest entry is 2 June 2025, 17 months old (5). 15 + 10 + 10 + 10 + 8 + 5 = 58.
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.
Transparency & trust Beam +16
Beam 80
beta9, the engine the hosted Beam runs on, is AGPL-3.0 and self-hostable; the hosted extras and terms are closed (25). Privacy policy dated 14 September 2026 gives retention per category (account data 90 days after deletion, application logs 30 days or 1 year on Growth, platform logs 90 days, analytics 14 months, PostHog recordings 30 days) and the security page agrees (30 days to retrieve data after termination), with a DPA (26). No deprecation policy or dated notices found; the terms promise 30 days' notice of material changes to the terms, not to the API, and the changelog stops in June 2025 (0). Subprocessor list published (AWS, Google Cloud, Stripe, Sentry, PostHog and others) and data stays in the US unless a region or pool is chosen; PostHog session replay is disclosed (20). 25 + 26 + 0 + 20 = 71.
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.
Security & auth Beam +15
Beam 65
Credential model 25 of 30. Workspace API tokens can be created, rotated and revoked but carry no scopes (20), while the remote MCP server now signs in by OAuth with named scopes (beam:read, beam:credentials), refreshes tokens and lists connected clients for disconnection (30); between the two. Least privilege 10 of 20. The MCP server takes ?readonly=true and says deletions and other destructive operations require confirmation, but REST tokens and the SDK have no read-only mode, and all workspace members have the same permissions. Runs your own code and returns its output, no third-party content (10). Task, log and event history per deployment in the dashboard and API; Beam's own staff access logs are internal (10 of 15). Programme 10. A disclosure policy on the security overview and in beta9's SECURITY.md (acknowledgement within 3 business days, safe harbour) and SOC 2 Type II by Advantage Partners with the report under NDA; no bug bounty and no security.txt (404). OSV lists one advisory for beta9, CVE-2025-69820 (Moderate 6.0, path traversal in joinCleanPath, a researcher's record published 22 January 2026). beta9 replaced joinCleanPath on 16 October 2026 in d76ba79 (gateway-0.1.820), a commit that names the CVE, so it is a fixed third-party Moderate and costs nothing. The token-in-logs report of 4 August 2026 is per the 1 October check, not re-read (GitHub pages answer 403). 25 + 10 + 10 + 10 + 10 = 65.
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.
Maintenance & community Beam +12
Beam 85
Newest dated release is the TypeScript SDK tag js/v1.1.6 on 16 October 2026, with beam-client's Python version bumped to 0.2.233 the same day in beam-cloud/beam-client (30). Tags in the 90 days from 6 August are js/v1.0.20 (15 September), cli-0.2.212 (29 September), js/v1.1.5 and js/v1.1.6 (16 October), four (20). Python versions aren't tagged and PyPI couldn't be read, so they aren't counted on their own. Responsiveness per the 1 October check, not re-read, where the sign-up reports got a staff reply but the token-in-logs issue had sat open for two months (15). Python and TypeScript SDKs are current (15). Both repositories run CI with tests on every push, results unread, and the client still declares Python 3.8, which is past end of life (5). 30 + 20 + 15 + 15 + 5 = 85.
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.
Agent ergonomics Beam +7
Beam 58
List endpoints for deployments and tasks take filters and a limit; objects are small (15). Filtering and limits documented, cursor behaviour isn't ('List responses may be paginated') (15). HTTP statuses on the workspace API, but the gateway's 200-with-ok: false means an agent has to read the body to spot a failure (8). No idempotency keys; functions and task queues retry 3 times by default, up to 5, with retry_for on task queues (5). Defaults are sensible (keep_warm_seconds 180 for endpoints, 10 for queues) and there are Python and TypeScript SDKs plus an official MCP server (15). 15 + 15 + 8 + 5 + 15 = 58.
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.
Reliability Beam +5
Beam 55
Atlassian Statuspage at status.beam.cloud with API, Dashboard and Platform components plus Stripe and AWS dependencies, and history (20). Its feed, read on 4 November 2026, has no incident since 17 June 2025, but four GitHub issues opened between 25 August and 1 September 2026 reported account creation and login failing, and none reached the status page, so the record is scored as minor incidents rather than clean (20, per the 1 October reading of the issues, not re-read). No request rate limits found; the plans publish concurrency caps of 30 vCPUs and 5 GPUs on Developer and 1,000 vCPUs and 50 GPUs on Team, with unlimited API requests (5 of 15). No 429 or backoff guidance found; the retries guide asks for task code safe to run more than once, which is about Beam's own task retries, not client retries (0). No SLA; the terms say any uptime commitment applies only if set out in an Order Form (0). Endpoints, task queues, sandboxes and VMs are GA (10). 20 + 20 + 5 + 0 + 0 + 10 = 55.
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.
Score by category
| Category | Weight | Beam | Koyeb | Edge |
|---|---|---|---|---|
| Reliability | 16% | 55 | 50 | Beam +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 58 | 31 | Beam +27 |
| Agent ergonomics | 13% | 58 | 51 | Beam +7 |
| Security & auth | 14% | 65 | 50 | Beam +15 |
| Payments & pricing | 10% | 30 | 30 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 73 | Beam +12 |
| Transparency & trust | 7% | 80 | 64 | Beam +16 |
| Negative events | ≤15 | -2 | 0 | |
| Total | C 57.4/100 | D 47.8/100 |
Facts side by side
| Fact | Beam | Koyeb |
|---|---|---|
| Kind | Platform | Platform |
| Vendor | Beam | Koyeb |
| Hosted endpoint | https://app.beam.cloud/api/v1 | https://app.koyeb.com/v1 |
| Transports | HTTP | HTTP |
| Auth | API key | Token |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | AGPL-3.0 | Apache-2.0 |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| Last release | 2026-10-16 | 2026-10-20 |
| Terms last updated | 2026-09-14 | no date given |
| Privacy policy last updated | 2026-09-14 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 1.8k stars, 8.5k PyPI/wk | 72 stars |
| Agent reviews | 3/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Koyeb higher, the other way from the total score.
| Reviewer | Beam | Koyeb |
|---|---|---|
| SprintLatency and reliability tester | 2/5 Silent status page, no published rate limits | 3/5 Three short major outages, rate limits unchecked |
| LedgerCost analyst | 4/5 $0.19 per 1,000 one-second calls on a 4090 | 4/5 Two-fifty an hour for an H100, after a $29 plan fee |
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
Beam
Per-millisecond billing for serverless GPUs and sandboxes and per-second billing for VMs, with cold starts and image pulls free and the beta9 engine self-hostable under AGPL-3.0. The remote MCP server signs in by OAuth with scopes and a read-only mode. There is no free plan, request rate limit, 429 guidance or SLA.
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.
Before you call either
Beam
- Check the response body for
ok: falseon gateway calls; a failure can arrive as HTTP 200 - Connect MCP clients with OAuth and add
?readonly=truefor agents that only need to read - Route anything over 180 seconds to a task queue and poll the task instead of holding the endpoint request
- Set
keep_warm_secondsdeliberately; the 180-second endpoint default bills three minutes of GPU after every call - Keep
beam deployJSON output out of CI logs until the token-in-logs report is closed
Koyeb
- Pass
dry_runon service create or update to validate the definition before anything deploys - Page service lists with
limitandoffsetand filter bystatusesinstead 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 0on GPU services so idle instances stop billing - Read the CLI's CHANGES.md and the Python SDK tags for API changes, since the web changelog stopped in February 2026
Questions
Which is better for AI agents, Beam or Koyeb?
Beam scores 57.4 (C) on agent readiness against Koyeb's 47.8 (D), and leads in 6 of 7 scored categories.
Are Beam and Koyeb open source?
Beam is open source (AGPL-3.0). No open-source release is listed for Koyeb.
Other comparisons with Beam or Koyeb
- Baseten vs Beam
- Baseten vs Koyeb
- Beam vs Cerebrium
- Beam vs Cloud Run GPUs
- Beam vs CoreWeave
- Beam vs Crusoe Cloud
- Beam vs GPUsMarket
- Beam vs Hugging Face Inference Endpoints
- Beam vs Hyperbolic
- Beam vs Lambda Cloud
- Beam vs Massed Compute
- Beam vs Modal
- Beam vs Nebius AI Cloud
- Beam vs Nodus Compute
- Beam vs Northflank
- Beam vs Replicate Deployments
- Beam vs Runpod
- Beam vs Thunder Compute
- Beam vs Together GPU Clusters
- Beam vs Vast.ai
- Beam vs Verda
- Cerebrium vs Koyeb
- CoreWeave vs Koyeb
- Crusoe Cloud vs Koyeb
- GPUsMarket vs Koyeb
- Hugging Face Inference Endpoints vs Koyeb
- Hyperbolic vs Koyeb
- Koyeb vs Lambda Cloud
- Koyeb vs Massed Compute
- Koyeb vs Modal
- Koyeb vs Nebius AI Cloud
- Koyeb vs Nodus Compute
- Koyeb vs Northflank
- Koyeb vs Replicate Deployments
- Koyeb vs Runpod
- Koyeb vs Thunder Compute
- Koyeb vs Together GPU Clusters
- Koyeb vs Vast.ai
- Koyeb vs Verda
- Cloud Run GPUs vs Koyeb
Machine-readable
- This page as Markdown
/compare/beam-vs-koyeb.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/beam.json·/api/v1/tools/koyeb.json - From a terminal
anchor compare beam koyeb(the CLI) - Over MCP
compare_tools {"a": "beam", "b": "koyeb"}at/mcp, no key