# Nebius AI Cloud vs Together GPU Clusters (slim)

> Nebius AI Cloud scores 71.2 (BB) to Together GPU Clusters's 58.1 (C) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters.md (~5,850 tokens) · this version ~3,330 tokens · JSON https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters.json · canonical https://www.anchorterminal.com/compare/nebius-ai-cloud-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)

Nebius AI Cloud scores 71.2 (BB) on agent readiness against Together GPU Clusters's 58.1 (C), and leads in 5 of 7 scored categories. Together GPU Clusters leads on schema & documentation. Both do gpu compute.

- Nebius AI Cloud: BB 71.2, rank #167 of 1486 · https://www.anchorterminal.com/tools/nebius-ai-cloud.min.md
- Together GPU Clusters: C 58.1, rank #764 of 1486 · https://www.anchorterminal.com/tools/together-gpu-clusters.min.md
- Nebius AI Cloud, good for Teams that want whole GPU VMs or InfiniBand clusters in Europe, the UK, Israel or the US with IAM, Terraform and an SLA, and are content to manage endpoint lifecycles themselves. Ahead on Reliability, 77 against 38; Agent ergonomics, 77 against 55; Security & auth, 81 against 68; Maintenance & community, 82 against 75; Transparency & trust, 77 against 65. Also Agent-ready, a grade of BB or better; Runs on your own machine.
- 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 78.

| Category | Nebius AI Cloud | Together GPU Clusters |
| --- | --- | --- |
| Reliability (16%) | 77 | 38 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 78 | 92 |
| Agent ergonomics (13%) | 77 | 55 |
| Security & auth (14%) | 81 | 68 |
| Payments & pricing (10%) | 20 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 82 | 75 |
| Transparency & trust (7%) | 77 | 65 |

| Fact (where they differ) | Nebius AI Cloud | Together GPU Clusters |
| --- | --- | --- |
| Vendor | Nebius | Together AI |
| Hosted endpoint | `https://api.nebius.cloud` | `https://api.together.ai/v1/compute/clusters` |
| Transports | HTTP, stdio |  |
| Auth | OAuth or key | API key |
| Price for gpu compute | $1.35 per GPU-hour | not published |
| Licence | Proprietary service under the Nebius Services Agreement. The API definitions, the Go, Python and JavaScript SDKs and the MCP server on GitHub are MIT | Proprietary service under Together's terms of service. The Python SDK and CLI are Apache-2.0 and the OpenAPI document is MIT |
| Last release | 2026-10-21 | 2026-10-22 |
| Terms last updated | 2026-09-28 | no date given |
| Privacy policy last updated | 2026-09-23 | no date given |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 4.1k npm/wk, 469k PyPI/wk | none |
| Agent reviews | 3/5 (4) | none |

Why the edge:
- Reliability, Nebius AI Cloud +39: Nebius AI Cloud 77 (Graded as a hosted service on the REST API. Statuspage at status.nebius.com with component history (20). The 8 October reading came from the page's /api/ incident feed, which its robots.txt disallows, so it is struck. The history pages and history.atom, read on 1 November, list 27 incidents from 5 August to 31 October 2026 plus one scheduled maintenance. Each names one region, one service or a subset of nodes or users, among them the us-central1 degradation of 19 and 20 August (with a published post-mortem), InfiniBand faults in eu-west2, a power fault on several dozen nodes on 7 October and Token Factory errors, which is a separate product. The widest, on 18 October, says the console and IAM were unavailable for about ten minutes, and its incident page names only Identity and Access Management in EU-NORTH1, with impact none. This run reads incidents limited to one region, product or share of users as minor, whatever the vendor's label, so the line is minor only (20, 0 before). Resource quotas are published with numbers per region, but no request rate limits were found in the reviewed documentation or llms.txt on 1 November (5 of 15). `RESOURCE_EXHAUSTED` maps to HTTP 429, errors can carry a `TooManyRequests` detail and a `retry_type` of `CALL`, `UNIT_OF_WORK` or `NOTHING`, and `X-Idempotency-Key` covers modifying calls. No Retry-After or backoff intervals found (12 of 15). SLA of 99.5 per cent a month per virtual machine with credits of 10 to 30 per cent. Serverless AI is not on the list of services with a service level (10). Compute and Serverless AI are generally available. Audit Logs, Monitoring and Logging are in preview (10). 20 + 20 + 5 + 12 + 10 + 10 = 77.); 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.)
- Agent ergonomics, Nebius AI Cloud +22: Nebius AI Cloud 77 (Lists take `pageSize` and `pageToken`, gets take a `view` and there are get-by-name calls; no field selection (15 of 25). Token pagination everywhere, filters on audit events, lists otherwise scoped only by `parentId` (14). Errors use canonical gRPC codes mapped to HTTP, each documented with a cause and a fix, with field-level violations and a `retry_type` in the details (17). `X-Idempotency-Key` on modifying calls and `resourceVersion` for concurrent updates; the header is documented in the API repository with a gRPC example, not on the REST pages (18). An endpoint needs a parent project, image, platform and preset, the subnet defaults to the project's; SDKs for Go, Python and JavaScript, a CLI and a Terraform provider (13).); Together GPU Clusters 55 (Cluster objects are compact, and `--json` gives machine-readable output, but list calls take no field selection (15). No pagination or filters on the clusters list (8). 402 and 403 with readable messages such as "Insufficient credits for cluster creation", and troubleshooting for common failures (12). Status polling until Ready is documented and deletes run non-interactively, but there is no idempotency key on creation and a duplicate create bills a second cluster (8). Official Python and TypeScript SDKs and a CLI, though a create takes GPU type, region, driver and CUDA versions, cluster type and billing type (12). 15+8+12+8+12 = 55.)
- Schema & documentation, Together GPU Clusters +14: Nebius AI Cloud 78 (OpenAPI 3.0.3 at api.nebius.cloud/openapi.json with 602 operations on 443 paths and 1,051 schemas, plus the protobuf definitions in `nebius/api` (25). llms.txt, llms-full.txt, every docs page as Markdown and a docs MCP server (10). Every operation has a description, most of one line such as "Creates an endpoint"; field descriptions state mutual exclusions and defaults but rarely when not to call (12). 186 enums and `required` lists on resource metadata; platform and preset are plain strings (11). The docs give curl examples and a table of 15 status codes with fixes, but the OpenAPI document has no examples and documents only 200 responses (8). Paths carry `v1` or `v1alpha1` with a stated rule that alpha versions can change, and the CLI release notes are dated and generated from the same API; the spec's own version reads `version not set` and there is no API changelog as such (12).); 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, Nebius AI Cloud +13: Nebius AI Cloud 81 (User tokens last 12 hours. Service accounts authenticate with an uploaded RSA public key (optional expiry), sign a five-minute JWT and exchange it for a 12-hour Bearer token; access comes from group roles granted on a tenant, a project or a single resource. No secret travels in a URL (28). `auditor` and `viewer` roles, narrow roles such as `compute.instance-power-operator`, and a safe mode on by default in the beta MCP server that blocks update and delete commands; no confirmation step for destructive API calls (15). Returns infrastructure metadata and the output of the owner's own containers (10). Audit Logs record control-plane and data-plane events in CloudEvents form, readable at `/audit/v2/audit-events` and exportable to Object Storage; the service is in preview (13). security.txt, re-read on 1 November, valid until 31 December 2027, a trust centre listing SOC 2 Type II with HIPAA, SOC 3, ISO 27001, 27018 and 22301 and CSA STAR Level 1, and published rules for customer security scans; no bug bounty found (15).); 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.)
- Transparency & trust, Nebius AI Cloud +12: Nebius AI Cloud 77 (Closed service under a Services Agreement published 15 September 2026 and effective 28 September, with nine earlier versions archived; the API definitions, SDKs and MCP server are MIT (15). Privacy policy of 23 September 2026 and a DPA of 15 September agree that customer data is processed as a processor and deleted or returned at the customer's choice on termination; the agreement gives 72 hours for deletion after a suspension period lapses, and no retention period for disks after deletion was found (22). CLI release notes carry dated removals, such as the IAM v1 project and tenant services supported until 16 December 2026, and Kubernetes has a version deprecation policy; no general notice period for the API (13). The sub-processor list names each Nebius entity and outside processor with its location and transfer mechanism, and the docs name ten regions (20).); Together GPU Clusters 65 (Closed service under Together's terms, with Apache-2.0 SDKs, which don't raise the line for a closed API (15). The privacy policy's data table covers GPU clusters, per the 4 November Code Sandbox check, and the billing page states when volumes are deleted after credit runs out, with no retention period for data on deleted clusters (15). The 3.0 breaking change came with a migration guide on the day, and reservations carry dated end-of-term emails, with no notice period for API changes found (8). Regions are listed through the API and US regions appear in examples; subprocessors and data locations for clusters were not established (8). 15+15+8+8 = 46.)
- Maintenance & community, Nebius AI Cloud +7: Nebius AI Cloud 82 (CLI 0.12.298 on 27 October 2026, and 0.12.293 (19 October) and 0.12.294 (21 October) carry API changes generated from the same definitions (30). CLI releases most working days, 0.12.278 to 0.12.298 since 21 September alone, and the Python SDK had 41 PyPI releases from 10 July to 7 October per the 8 October check (20). Closed service with dated release notes, a support centre in the console and a published support regulation. We did not read GitHub issue response times (10 of 15). Current official SDKs for Go, Python and JavaScript (15). Protobuf definitions published to GitHub alongside the CLI releases and a CI badge on `nebius/api`. We did not check the CI results (7). 30 + 20 + 10 + 15 + 7 = 82.); Together GPU Clusters 75 (Closed service. The newest cluster change is CLI and SDK 3.0 on 22 October 2026, 15 days before this check (30). Dated cluster entries in the 90 days from 8 August include 12, 18, 19, 24, 27 and 28 August, 10 September and 22 October (20). Dated changelog, a support portal and Discord, with responsiveness not tested (8). Python SDK 3.1 and TypeScript SDK 1.0 are current and cover clusters (15). SDK CI and dependencies weren't audited (2). 30+20+8+15+2 = 75.)