# Together GPU Clusters vs Verda (slim)

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

- Full: https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda.md (~5,300 tokens) · this version ~2,980 tokens · JSON https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda.json · canonical https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda
- 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 Verda's 53.3 (D), and leads in 1 of 7 scored categories. Verda leads on reliability, agent ergonomics, maintenance & community and transparency & trust. Both do gpu compute.

- Together GPU Clusters: C 58.1, rank #768 of 1510 · https://www.anchorterminal.com/tools/together-gpu-clusters.min.md
- Verda: D 53.3, rank #952 of 1510 · https://www.anchorterminal.com/tools/verda.min.md
- 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 72. Also No incidents deducted, where Verda loses 9 points for them.
- Verda, good for Agents that rent whole GPU machines or clusters in Finland for training or batch work, or deploy scale-to-zero container endpoints, and that can run a local CLI for MCP. Ahead on Reliability, 60 against 38; Agent ergonomics, 63 against 55; Maintenance & community, 83 against 75; Transparency & trust, 76 against 65. Also Runs on your own machine.

| Category | Together GPU Clusters | Verda |
| --- | --- | --- |
| Reliability (16%) | 38 | 60 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 92 | 72 |
| Agent ergonomics (13%) | 55 | 63 |
| Security & auth (14%) | 68 | 68 |
| Payments & pricing (10%) | 20 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 83 |
| Transparency & trust (7%) | 65 | 76 |

| Fact (where they differ) | Together GPU Clusters | Verda |
| --- | --- | --- |
| Vendor | Together AI | Verda |
| Hosted endpoint | `https://api.together.ai/v1/compute/clusters` | `https://api.verda.com/v1` |
| Transports |  | HTTP, stdio |
| Auth | API key | OAuth |
| Licence | Proprietary service under Together's terms of service. The Python SDK and CLI are Apache-2.0 and the OpenAPI document is MIT | Proprietary service under Verda's Terms of Service. The CLI, the Python SDK and the Go SDK on GitHub are Apache-2.0 |
| Tools exposed | none | 18 |
| Last release | 2026-10-22 | 2026-10-28 |
| Terms last updated | no date given | 2025-09-30 |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 10k PyPI/wk |
| Agent reviews | none | 3.3/5 (4) |

Why the edge:
- Reliability, Verda +22: 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.); Verda 60 (Graded on the hosted lines for the REST API. BetterStack page at status.verda.com with 21 components, 180-day bars and an RSS feed (20). The feed lists eight incidents from 4 August to 2 November 2026, none posted against the API component and each limited to one product, one location or some customers. Serverless Containers were slow or unavailable for about 9.5 hours on 13 August, the container gateway returned intermittent 500s on 4 September, container uploads failed for about 2 hours on 20 September, a small number of instances, volumes and billing records were affected on 25 September, Serverless Containers degraded during a security update on 9 October, FIN03 services and Google SSO sign-in failed during maintenance on 11 October, the container registry vccr.io was down on 19 October, and FIN-02 lost network connectivity on 23 October. This run reads all of them as partial, minor only (20). api.verda.com, which hosts the API reference with the rate limits, answered robots.txt with 401 on 2 November 2026, so the 8 October readings from its OpenAPI document are struck. The docs' changelog says rate limits apply since 11 March 2026 and points to that reference, with no numbers on a page we can read (0). The official Go SDK's retry middleware backs off on 429 and 5xx, instance actions already in the requested state answer 204 and volume deletion is idempotent per the docs' changelog, and serverless job request IDs answer 409 on a repeat, but instance creation has no idempotency key and Retry-After is documented only on the refused host (10 of 15). No SLA found, and the terms give no warranty of uninterrupted availability (0). The REST API is generally available, while the CLI's MCP server is marked beta (10).)
- Schema & documentation, Together GPU Clusters +20: 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.); Verda 72 (api.verda.com's robots.txt answered 401 on 2 November 2026, so the OpenAPI document and the API reference there weren't read and the 8 October counts taken from them (112 operations, 156 schemas, 104 enums, 756 examples) are struck. The docs' changelog names the OpenAPI specification and its schemas (oneOf for UUID-or-array fields, the 19 March 2026 auth fix), and the Go and Python SDKs carry typed models, but no per-operation reference is readable on an allowed host (20 of 25). `llms.txt` on verda.com and docs.verda.com, every docs page as Markdown and the corpus in `llms-full.txt` (10). Docs guides and changelog entries describe what endpoints do and their billing effects, for example that `shutdown` keeps charging, while the reference descriptions are unread (10 of 20). Required fields and enums are visible only through the SDKs' typed models and validation, such as the Go SDK's limits added in v1.7.0, and the docs ask clients to treat enums as open (8 of 15). The docs corpus carries 62 curl examples and the Python SDK lists seven error codes, while per-operation error responses sit in the unread reference (9 of 15). Versioned in the path, with a dated changelog of 24 entries in 2026, the newest on 7 October (15).)
- Transparency & trust, Verda +11: 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.); Verda 76 (Closed service under Terms of Service dated 30 September 2025 and Finnish law. The CLI and SDKs are Apache-2.0 (15 of 30). The terms include data processing terms, and the privacy policy has a retention table. Deleted customer data is removed within 96 hours per the privacy policy and clause 10.9.2, while Schedule 3 of the same terms says 72 hours. The privacy policy shows no readable date (20 of 30). No deprecation policy with a notice period. HDD volumes were announced as deprecated in April 2026 before creation was blocked on 21 September (10 of 20). The docs name three data centres in Helsinki, the terms promise 15 days' notice of a new sub-processor, and the privacy policy names Front and Stripe. The sub-processor list is drawn by script and we couldn't read it (12 of 20).)
- Agent ergonomics, Verda +8: 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.); Verda 63 (Read from the docs' changelog and the SDKs on 2 November, since the API reference host refuses our reader. No field selection, and instance and volume lists return whole arrays (12 of 25). `page` and `pageSize` with totals in `X-Total-Count` on scripts and journals, a cursor on the audit log, and status, tag and location filters on other lists, but no pagination on instances or volumes (12 of 20). Errors carry a stable `code` and a `message`, and bulk actions return per-item results with 207 (16). Actions that are already in the requested state return 204 and volume deletion is idempotent, but create calls have no idempotency key. The MCP tools require `confirm: true` for billed and destructive calls and carry no read-only or destructive annotations (10 of 20). Official SDKs for Python and Go, a Terraform provider and a CLI. A launch needs an instance type, image, hostname, SSH key and location (13 of 15).)
- Maintenance & community, Verda +8: 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.); Verda 83 (Dated sources counted on 2 November. Go SDK `verdacloud-sdk-go` v1.7.0 on 28 October 2026, Python SDK `verda` 1.25.0 on 23 October, CLI v1.9.0 on 22 October, and the newest API changelog entry on 7 October (30). 11 dated API entries from 11 September to 7 October 2026, plus Go SDK v1.4.3, v1.5.0, v1.6.0, v1.6.1, v1.6.2 and v1.7.0, Python SDK 1.24.1 and 1.25.0 and CLI v1.8.1, v1.8.2 and v1.9.0 in the 90 days (20). A public changelog, monthly release notes, email and chat support and a forum. GitHub issues were not read (10 of 15). Current official clients for Python and Go, a Terraform provider and a CLI (15). The CLI repository runs lint, test and security workflows, and the Go SDK added a go fix check on 27 October 2026 (8 of 10).)