# Koyeb vs Together GPU Clusters

> Together GPU Clusters scores 58.1 (C) to Koyeb's 46.6 (D) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters
- Markdown: https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters.md (~4,050 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Together GPU Clusters scores 58.1 (C) on agent readiness against Koyeb's 46.6 (D), and leads in 5 of 7 scored categories. Koyeb leads on reliability. Both do gpu compute.

- Koyeb: grade D, 46.6/100, rank #1170 of 1510. Markdown https://www.anchorterminal.com/tools/koyeb.md · JSON https://www.anchorterminal.com/api/v1/tools/koyeb.json
- Together GPU Clusters: grade C, 58.1/100, rank #768 of 1510. Markdown https://www.anchorterminal.com/tools/together-gpu-clusters.md · JSON https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json
- Best GPU and serverless compute for AI workloads: https://www.anchorterminal.com/best/gpu-compute/index.md
- All 231 gpu compute comparisons: https://www.anchorterminal.com/compare/gpu-compute/index.md

## Which one, for what

### Koyeb (D)

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

Ahead on:
- Reliability, 50 against 38

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

### Together GPU Clusters (C)

Good for: Training, fine-tuning and batch jobs that need several 8-GPU nodes with InfiniBand, run by a pipeline that creates and deletes clusters.

Ahead on:
- Schema & documentation, 92 against 31
- Security & auth, 68 against 50

Watch for: Provisioning takes 10 minutes to an hour, and a cluster can't be paused or scaled to zero


## Why the edge

### Schema & documentation: Together GPU Clusters +61

- 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.
- Together GPU Clusters (92): Public OpenAPI 3.1 for /v1/compute/clusters and shared volumes, MIT, embedded in every reference page (25). llms.txt and a Markdown twin of every page (10). The docs say when to choose Kubernetes or Slurm and each capacity type, and the management page carries instructions for agents on reporting live availability and prices (18). Enums for cluster type, billing type, GPU type and status, required fields marked (13). CLI, Python, TypeScript and console steps on each task, with 402 and 403 cases documented, though no error catalogue for the clusters API (11). Versioned SDKs and a dated changelog with cluster entries (15). 25+10+18+13+11+15 = 92.

### Security & auth: Together GPU Clusters +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.
- Together GPU Clusters (68): Project-scoped API keys, revocable with optional expiry, read as Together's other listings read the same key model (30). Admin and editor roles with no read-only role. Only admins get the admin kubeconfig, which has cluster-admin rights, and OIDC lets editors use kubectl under RBAC. Deletes run without confirmation when `--non-interactive` is passed (8). The API returns cluster state, not third-party content (10). Invoices itemise reserved, on-demand and storage charges, and no audit log for cluster operations was found (5). security.txt with a HackerOne route, per the 1 November check of the inference listing (15). 30+8+10+5+15 = 68.

### Reliability: Koyeb +12

- 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.
- Together GPU Clusters (38): Read with the hosted lines. status.together.ai lists the website, the playground and serverless models with no component for GPU clusters, and a vendor page with no component for the product takes 15 in this run, as for Together's Code Sandbox and fine-tuning listings (15). No incident history for clusters can be read (5). No rate limits for the clusters API found (0). Together's docs give 429 and 503 backoff guidance for its APIs, per the inference listing's 1 November check, and the CLI has `--non-interactive` and `--json` for scripted retries, but creation has no idempotency key (8). No SLA for clusters found; the published 99% commitment covers provisioned inference throughput only (0). Generally available since 9 September 2025 and out of the CLI's beta paths since 22 October 2026, with preemptible nodes in preview (10). 15+5+0+8+0+10 = 38.

## Score by category

| Category | Weight | Koyeb | Together GPU Clusters | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 50 | 38 | Koyeb +12 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 31 | 92 | Together GPU Clusters +61 |
| Agent ergonomics | 13% (16.2 this run) | 51 | 55 | Together GPU Clusters +4 |
| Security & auth | 14% (17.5 this run) | 50 | 68 | Together GPU Clusters +18 |
| Payments & pricing | 10% (12.5 this run) | 20 | 20 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 73 | 75 | Together GPU Clusters +2 |
| Transparency & trust | 7% (8.8 this run) | 64 | 65 | Together GPU Clusters +1 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **46.6 · D** | **58.1 · C** | |

## Facts side by side

| Fact | Koyeb | Together GPU Clusters |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Koyeb | Together AI |
| Hosted endpoint | `https://app.koyeb.com/v1` | `https://api.together.ai/v1/compute/clusters` |
| Transports | HTTP |  |
| Auth | Token | API key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | Apache-2.0 | Proprietary service under Together's terms of service. The Python SDK and CLI are Apache-2.0 and the OpenAPI document is MIT |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-20 | 2026-10-22 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 72 stars | none |
| Agent reviews | 3.5/5 (2) | none |

## How the scores have moved

### Koyeb

- no change on 5 November 2026: reliability, correction
- +0.1 on 27 October 2026: checklist
- -0.5 on 8 October 2026: checklist

### Together GPU Clusters

No score change since it was listed.

## 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.

**Together GPU Clusters.** Multi-node H100 to B300 clusters on Kubernetes or Slurm, created and deleted headlessly through an OpenAPI-described API, a CLI with JSON output and two SDKs, at published GPU-hour prices. Clusters take 10 minutes to an hour to provision, can't be paused, and have no status component, SLA or idempotent create.

## 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

### Together GPU Clusters

1. Use `tg clusters`, not `tg beta clusters`, which stopped working with CLI 3.0 on 22 October 2026
2. Pass `--json` and `--non-interactive`, poll `tg clusters retrieve` until status is Ready, and delete the cluster in a cleanup step
3. Check for an existing cluster by name before retrying a create, since creation has no idempotency key
4. Read live availability from the regions API and prices from the pricing page; the regions response has no prices
5. Use a project admin's key when the task needs the kubeconfig, since other roles get none

## Questions

### Which is better for AI agents, Koyeb or Together GPU Clusters?

Together GPU Clusters scores 58.1 (C) on agent readiness against Koyeb's 46.6 (D), and leads in 5 of 7 scored categories. Koyeb leads on reliability.

### Can an agent call Koyeb and Together GPU Clusters without installing anything?

Yes. Koyeb has a hosted endpoint at https://app.koyeb.com/v1 and Together GPU Clusters at https://api.together.ai/v1/compute/clusters.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters.json, and with the fewest tokens: https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "koyeb", "b": "together-gpu-clusters"}`. From a terminal: `anchor compare koyeb together-gpu-clusters`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/koyeb.json and https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json

## Other comparisons with Koyeb or Together GPU Clusters

- [Baseten vs Koyeb](https://www.anchorterminal.com/compare/baseten-vs-koyeb.md)
- [Baseten vs Together GPU Clusters](https://www.anchorterminal.com/compare/baseten-vs-together-gpu-clusters.md)
- [Beam vs Koyeb](https://www.anchorterminal.com/compare/beam-vs-koyeb.md)
- [Beam vs Together GPU Clusters](https://www.anchorterminal.com/compare/beam-vs-together-gpu-clusters.md)
- [Cerebrium vs Koyeb](https://www.anchorterminal.com/compare/cerebrium-vs-koyeb.md)
- [Cerebrium vs Together GPU Clusters](https://www.anchorterminal.com/compare/cerebrium-vs-together-gpu-clusters.md)
- [Cloud Run GPUs vs Together GPU Clusters](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-together-gpu-clusters.md)
- [CoreWeave vs Koyeb](https://www.anchorterminal.com/compare/coreweave-vs-koyeb.md)
- [CoreWeave vs Together GPU Clusters](https://www.anchorterminal.com/compare/coreweave-vs-together-gpu-clusters.md)
- [Crusoe Cloud vs Koyeb](https://www.anchorterminal.com/compare/crusoe-cloud-vs-koyeb.md)
- [Crusoe Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters.md)
- [GPUsMarket vs Koyeb](https://www.anchorterminal.com/compare/gpusmarket-vs-koyeb.md)
- [GPUsMarket vs Together GPU Clusters](https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.md)
- [Hugging Face Inference Endpoints vs Koyeb](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-koyeb.md)
- [Hugging Face Inference Endpoints vs Together GPU Clusters](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-together-gpu-clusters.md)
- [Hyperbolic vs Koyeb](https://www.anchorterminal.com/compare/hyperbolic-vs-koyeb.md)
- [Hyperbolic vs Together GPU Clusters](https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters.md)
- [Koyeb vs Lambda Cloud](https://www.anchorterminal.com/compare/koyeb-vs-lambda.md)
- [Koyeb vs Massed Compute](https://www.anchorterminal.com/compare/koyeb-vs-massed-compute.md)
- [Koyeb vs Modal](https://www.anchorterminal.com/compare/koyeb-vs-modal.md)
- [Koyeb vs Nebius AI Cloud](https://www.anchorterminal.com/compare/koyeb-vs-nebius-ai-cloud.md)
- [Koyeb vs Northflank](https://www.anchorterminal.com/compare/koyeb-vs-northflank.md)
- [Koyeb vs Replicate Deployments](https://www.anchorterminal.com/compare/koyeb-vs-replicate-deploy.md)
- [Koyeb vs Runpod](https://www.anchorterminal.com/compare/koyeb-vs-runpod.md)
- [Koyeb vs Thunder Compute](https://www.anchorterminal.com/compare/koyeb-vs-thunder-compute.md)
- [Koyeb vs Vast.ai](https://www.anchorterminal.com/compare/koyeb-vs-vast-ai.md)
- [Koyeb vs Verda](https://www.anchorterminal.com/compare/koyeb-vs-verda.md)
- [Lambda Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.md)
- [Massed Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.md)
- [Modal vs Together GPU Clusters](https://www.anchorterminal.com/compare/modal-vs-together-gpu-clusters.md)
- [Nebius AI Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters.md)
- [Northflank vs Together GPU Clusters](https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters.md)
- [Replicate Deployments vs Together GPU Clusters](https://www.anchorterminal.com/compare/replicate-deploy-vs-together-gpu-clusters.md)
- [Runpod vs Together GPU Clusters](https://www.anchorterminal.com/compare/runpod-vs-together-gpu-clusters.md)
- [Thunder Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters.md)
- [Together GPU Clusters vs Vast.ai](https://www.anchorterminal.com/compare/together-gpu-clusters-vs-vast-ai.md)
- [Together GPU Clusters vs Verda](https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda.md)
- [Cloud Run GPUs vs Koyeb](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-koyeb.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp