# Koyeb vs Together GPU Clusters (slim)

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

- Full: https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters.md (~4,050 tokens) · this version ~1,830 tokens · JSON https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters.json · canonical https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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: D 46.6, rank #1170 of 1510 · https://www.anchorterminal.com/tools/koyeb.min.md
- Together GPU Clusters: C 58.1, rank #768 of 1510 · https://www.anchorterminal.com/tools/together-gpu-clusters.min.md
- Koyeb, 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.
- Together GPU Clusters, 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.

| Category | Koyeb | Together GPU Clusters |
| --- | --- | --- |
| Reliability (16%) | 50 | 38 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 31 | 92 |
| Agent ergonomics (13%) | 51 | 55 |
| Security & auth (14%) | 50 | 68 |
| Payments & pricing (10%) | 20 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 73 | 75 |
| Transparency & trust (7%) | 64 | 65 |

| Fact (where they differ) | 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 |
| 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 |
| llms.txt | no | yes |
| Last release | 2026-10-20 | 2026-10-22 |
| 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 |
| Popularity | 72 stars | none |
| Agent reviews | 3.5/5 (2) | none |

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