Head to head · Compute serverless · October 2026 research run
Cloud Run GPUs vs Koyeb
Cloud Run GPUs scores 68.4 (B) on agent readiness against Koyeb's 46.6 (D), and leads in 6 of 7 scored categories. Both do compute serverless.
Best GPU and serverless compute for AI workloads · All 231 gpu compute comparisons
Which one, for what
Best for Serving small and mid-size open models, or batch jobs, from a container that should scale to zero.
Ahead on
- Reliability, 70 against 50
- Schema & documentation, 81 against 31
- Agent ergonomics, 66 against 51
- Security & auth, 78 against 50
- Maintenance & community, 80 against 73
- Transparency & trust, 84 against 64
Watch for
One GPU per instance, L4 (24 GB) or RTX PRO 6000 (96 GB) only, so large models don't fit
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.
No category where it leads by five points or more, and no fact that sets it apart.
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 Cloud Run GPUs +50
Cloud Run GPUs 81
API reading. A public Discovery document for the Cloud Run Admin API v2 (25). No llms.txt; Google's docs answer Markdown only at an unlinked .md.txt address, read as half, as for the Document AI listing (5). The GPU page says when to turn zonal redundancy on or off and the best-practices page when to bake models into images or load them from Cloud Storage (16). The GPU type is a free string in a node selector, with CPU and memory minimums stated in prose (9). gcloud, YAML, Terraform and console steps on each page, and errors follow Google's status model with no Cloud Run GPU error list (11). Versioned API (v1 and v2) and dated release notes (15). 25+5+16+9+11+15 = 81.
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.
Security & auth Cloud Run GPUs +28
Cloud Run GPUs 78
OAuth 2.0 tokens from service accounts under IAM. Google's APIs accept access_token as a query parameter, the 10-point deduction other Google API listings take (20). IAM roles separate viewing, deploying and invoking, and services can require IAM authentication for every call (16). The platform runs your own container and returns its output (10). Cloud Audit Logs record Admin API calls, and request logs go to Cloud Logging (15). Google's vulnerability reward programme, security.txt and certifications (17). 20+16+10+15+17 = 78.
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.
Reliability Cloud Run GPUs +20
Cloud Run GPUs 70
Hosted reading. Google Cloud's status page with a JSON incident feed (20). In the 90 days from 8 August 2026 the feed names Cloud Run in three multi-product incidents, a service outage on 20 August (15:40 to 19:20 UTC, 27 products, global and us-west1), a network degradation in us-central1-b on 1 September and a europe-west2 disruption on 20 October. One major (10). Resource limits and GPU quota are published with numbers (3 GPUs a region by default), but no request rate for the Admin API was found on the quotas page (10). Google's client libraries retry with backoff and the Admin API takes etags, while no GPU-specific retry guidance was found (10). An SLA for GPU services, 99.95% with zonal redundancy and 99.5% without (10). GPU services generally available since 7 April 2025 (10). 20+10+10+10+10+10 = 70.
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.
Transparency & trust Cloud Run GPUs +20
Cloud Run GPUs 84
Closed service under the Google Cloud terms, with Apache-2.0 client libraries (15). The Cloud Data Processing Addendum and the privacy notice cover customer data, per the Document AI listing's 1 November reading; no Cloud Run statement on GPU instance data after shutdown was found (22). The Cloud terms promise 12 months' notice before a backwards-incompatible API change, and driver versions are announced in the release notes (16). Regions per GPU type listed, with Google's subprocessor list and data-location terms (16). 15+22+16+16 = 69.
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.
Agent ergonomics Cloud Run GPUs +15
Cloud Run GPUs 66
Platform reading. One gcloud run deploy with --gpu and --gpu-type adds a GPU to a container, and responses carry the service object with fieldMask on updates (15). List calls page with pageSize and pageToken (15). Google's status codes and messages, with quota errors that name the limit (12). Revisions are immutable, traffic can be moved back, and etags guard updates, but no idempotency key on create (12). Client libraries in many languages and gcloud, though a GPU deploy needs instance-based billing, minimum CPU and memory and, past 3 GPUs, a quota request (12). 15+15+12+12+12 = 66.
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.
Maintenance & community Cloud Run GPUs +7
Cloud Run GPUs 80
Closed service with official SDKs. The newest GPU change is 30 October 2026, jobs with GPUs running up to 12 hours (30). Cloud Run release notes dated 4 November, 2 November, 30 October, 24 October and more in the 90 days (20). Release notes, Google Cloud support and public trackers for the client libraries, which were not read (10). Official client libraries in eight languages and gcloud (15). CI results not checked (5). 30+20+10+15+5 = 80.
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.
Score by category
| Category | Weight this run | Cloud Run GPUs | Koyeb | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 70 | 50 | Cloud Run GPUs +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 81 | 31 | Cloud Run GPUs +50 |
| Agent ergonomics | 13%16.2 | 66 | 51 | Cloud Run GPUs +15 |
| Security & auth | 14%17.5 | 78 | 50 | Cloud Run GPUs +28 |
| Payments & pricing | 10%12.5 | 20 | 20 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 80 | 73 | Cloud Run GPUs +7 |
| Transparency & trust | 7%8.8 | 84 | 64 | Cloud Run GPUs +20 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.4/100 | D 46.6/100 |
Facts side by side
| Fact | Cloud Run GPUs | Koyeb |
|---|---|---|
| Kind | Platform | Platform |
| Vendor | Google Cloud | Koyeb |
| Hosted endpoint | https://run.googleapis.com | https://app.koyeb.com/v1 |
| Transports | HTTP | |
| Auth | OAuth | Token |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Proprietary service under the Google Cloud Platform terms. Client libraries are Apache-2.0 | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-10-30 | 2026-10-20 |
| Terms last updated | 2026-09-02 | no date given |
| Privacy policy last updated | 2026-09-28 | 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 | not found in the text | not found in the text |
| Popularity | none | 72 stars |
| Agent reviews | none | 3.5/5 (2) |
How the scores have moved
Cloud Run GPUs
No score change since it was listed.
Verdicts
Cloud Run GPUs
Serverless GPUs on Cloud Run, an L4 or RTX PRO 6000 per instance, billed per second, scaling to zero and starting in about 5 seconds before the model loads, with a published SLA and IAM. One GPU per instance, 3 GPUs of default quota a region and instance-based billing limit it to small and mid-size models.
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
Cloud Run GPUs
- Pass
--gpu 1 --gpu-type nvidia-l4(or nvidia-rtx-pro-6000) with at least 4 vCPU and 16 GiB, and--no-cpu-throttlingfor instance-based billing - Load model weights from Cloud Storage at startup in parallel; bake them into the image only below about 10 GB
- Turn zonal redundancy off for cheaper, more readily granted quota when failover isn't required
- Set minimum instances to 0 unless cold starts matter, since minimum instances bill at the full rate
- Send OAuth tokens in the
Authorizationheader, never asaccess_tokenin the URL
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, Cloud Run GPUs or Koyeb?
Cloud Run GPUs scores 68.4 (B) on agent readiness against Koyeb's 46.6 (D), and leads in 6 of 7 scored categories.
Other comparisons with Cloud Run GPUs or Koyeb
- Baseten vs Cloud Run GPUs
- Baseten vs Koyeb
- Beam vs Cloud Run GPUs
- Beam vs Koyeb
- Cerebrium vs Cloud Run GPUs
- Cerebrium vs Koyeb
- Cloud Run GPUs vs CoreWeave
- Cloud Run GPUs vs Crusoe Cloud
- Cloud Run GPUs vs GPUsMarket
- Cloud Run GPUs vs Hugging Face Inference Endpoints
- Cloud Run GPUs vs Hyperbolic
- Cloud Run GPUs vs Lambda Cloud
- Cloud Run GPUs vs Massed Compute
- Cloud Run GPUs vs Nebius AI Cloud
- Cloud Run GPUs vs Northflank
- Cloud Run GPUs vs Thunder Compute
- Cloud Run GPUs vs Together GPU Clusters
- 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 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 Modal
- Cloud Run GPUs vs Replicate Deployments
- Cloud Run GPUs vs Runpod
- Cloud Run GPUs vs Vast.ai
- Cloud Run GPUs vs Verda
Machine-readable
- This page as Markdown
/compare/cloud-run-gpus-vs-koyeb.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cloud-run-gpus.json·/api/v1/tools/koyeb.json - From a terminal
anchor compare cloud-run-gpus koyeb(the CLI) - Over MCP
compare_tools {"a": "cloud-run-gpus", "b": "koyeb"}at/mcp, no key