# Together GPU Clusters > Together GPU Clusters rents multi-node NVIDIA H100, H200, B200 and B300 clusters with InfiniBand and shared storage, run as Kubernetes or Slurm, by the GPU-hour. Clusters are created and scaled from the console, the tg CLI, SDKs or REST API. - Canonical: https://www.anchorterminal.com/tools/together-gpu-clusters - Pricing: https://www.anchorterminal.com/tools/together-gpu-clusters#pricing - Reviews: https://www.anchorterminal.com/tools/together-gpu-clusters#reviews - Markdown: https://www.anchorterminal.com/tools/together-gpu-clusters.md (~7,800 tokens) - Slim: https://www.anchorterminal.com/tools/together-gpu-clusters.min.md (~1,680 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/together-gpu-clusters.json (this page as data, same URL with Accept: application/json) - 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 together-gpu-clusters.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. 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 ## Overview **Grade C · 58.1/100 · rank #764 of 1486 · #10 in GPU & serverless compute · not agent-ready · confidence medium** More from Together AI, listed separately because each is its own product: [Together AI Inference](https://www.anchorterminal.com/tools/together-inference.md) (Model APIs & inference), [Together AI Fine-tuning](https://www.anchorterminal.com/tools/together-fine-tuning.md) (Fine-tuning), [Together Code Sandbox](https://www.anchorterminal.com/tools/together-code-sandbox.md) (Code execution sandboxes). ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Together AI (https://www.together.ai) | | Kind | HTTP API | | Category | GPU & serverless compute (https://www.anchorterminal.com/categories/gpu-compute) | | Endpoint | `https://api.together.ai/v1/compute/clusters` | | Auth | API key · Bearer `TOGETHER_API_KEY`, scoped to a project, revocable and optionally expiring, the same keys as Together's other APIs. Only a project admin's key returns the cluster's admin kubeconfig. Team members can reach the Kubernetes API through OIDC with their own identity provider, and SSH uses OIDC or uploaded keys. | | Pricing | Pay per use (Pay per use) · On-demand from $3.99 per GPU-hour (H100) to $9.99 (B300); reserved 3 to 180 days from $3.19 to $7.99; preemptible (preview) from $1.99. Storage per GiB-month. No ingress or egress fees. Reservations are prepaid and non-refundable, and creation needs enough credit to cover them. | | x402 | No · No x402, MPP or L402 in the GPU clusters docs, billing pages or OpenAPI document (checked 2026-11-06). An exhausted balance returns 402 to scale requests with no payment requirements. | | Licence | Proprietary service under Together's terms of service. The Python SDK and CLI are Apache-2.0 and the OpenAPI document is MIT | | Packages | pypi: `together`; npm: `together-ai` | | Source | https://github.com/togethercomputer/together-py | | Docs | https://docs.together.ai/docs/gpu-clusters-overview | | llms.txt | https://docs.together.ai/llms.txt | | Last release | 2026-10-22 | | Surface listed | Together GPU clusters (Instant Clusters) through the REST API at api.together.ai/v1/compute/clusters, the `tg clusters` CLI and the Python and TypeScript SDKs, read from docs.together.ai (overview, quickstart, concepts, management, automation, pricing, preemptible compute, API reference and changelog) and status.together.ai on 6 November 2026. No account was made and no cluster was created | | Scope | Multi-node GPU clusters for training and batch work. Serverless and dedicated inference, fine-tuning and Code Sandbox have separate Anchor Terminal listings | | Hardware | NVIDIA HGX H100 SXM (80 GB), H200 (141 GB), B200 (180 GB) and B300, in full nodes of 8 GPUs, with 3.2 Tb/s InfiniBand, local NVMe and a shared volume of at least 1 TiB | | Cluster types | Kubernetes, reached with kubectl, or Slurm on Kubernetes through Slinky, reached by SSH to a login node | | Capacity types | On-demand by the hour, reserved for 3 to 180 days, scheduled windows from a project capacity pool, and preemptible nodes (preview) with a five-minute drain | | Access | Project roles admin and editor. Only admins download the admin kubeconfig, which has cluster-admin rights. OIDC gives editors kubectl access under Kubernetes RBAC | | Health | Active and passive health checks, with repair recommendations that can be approved by hand or run fully automatically | | Lifecycle | Reserved clusters are decommissioned at the end of the reservation after emails 7 days, 3 days, 1 day and 4 hours before. Volumes outlive clusters and are deleted 72 hours after credit runs out | | Capabilities | compute.gpu, compute.containers, compute.batch | | Tags | hosted, official, usage, prepaid, openapi, llms-txt, kubernetes, slurm, python, typescript, cli, h100, b200 | | JSON | https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json | ## Score breakdown (methodology v0.7, October 2026 research run) Assessed 2026-11-06 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 38 | 7.6 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 92 | 14.9 | | Agent ergonomics | 13% | 16.2 | 55 | 8.9 | | Security & auth | 14% | 17.5 | 68 | 11.9 | | Payments & pricing | 10% | 12.5 | 20 | 2.5 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 75 | 6.6 | | Transparency & trust (editorial 46, provenance 83) | 7% | 8.8 | 65 | 5.7 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **58.1 → C** | ### Why each score - Reliability 38 (checked 2026-11-06): 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. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 92 (checked 2026-11-06): 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. - Agent ergonomics 55 (checked 2026-11-06): 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. - Security & auth 68 (checked 2026-11-06): 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. - Payments & pricing 20 (checked 2026-11-06): No machine payment protocol (0). Per GPU-hour prices for each capacity type and per GiB-month storage published without a login (20). No free trial, and creation needs credit for the full reservation or a minimum on-demand period (0). Sign-up and credit purchase are browser steps (0). 0+20+0+0 = 20. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 75 (checked 2026-11-06): 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. - Transparency & trust 65 (checked 2026-11-06): 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. Fix list, everything this grade says the listing lacks, the biggest gain first (14 items). What it covers is at https://www.anchorterminal.com/fixes/together-gpu-clusters.md (JSON https://www.anchorterminal.com/fixes/together-gpu-clusters.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "together-gpu-clusters", "plan": "read"}`, free while the beta runs ### What we couldn't check - unchecked: rate limits and 429 behaviour on the clusters API, which the reviewed pages don't state - unchecked: whether the SLA language in Together's terms covers GPU clusters - Together's terms, privacy policy and security.txt were not re-read for this listing; the provenance follows the Together AI Inference check of 1 November 2026 - GitHub's API was rate-limited during this run, so SDK stars and CI status were not read ### Sources - GPU clusters overview: (seen 2026-11-06) - GPU clusters pricing: (seen 2026-11-06) - manage GPU clusters: (seen 2026-11-06) - automate cluster operations: (seen 2026-11-06) - quickstart: (seen 2026-11-06) - concepts: (seen 2026-11-06) - preemptible compute: (seen 2026-11-06) - create cluster API reference with OpenAPI: (seen 2026-11-06) - list clusters API reference: (seen 2026-11-06) - changelog: (seen 2026-11-06) - status page: (seen 2026-11-06) - llms.txt: (seen 2026-11-06) ## Score history Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters/history.json - 2026-11-06: graded 58.1 C (methodology 0.7) ## Who's behind it (provenance 83/100, checked 2026-11-06) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Together Computer, Inc. | 20/20 | | Domain age | together.ai, no registry record we could read | 0/15 | | Endpoint on the vendor's domain | api.together.ai | 15/15 | | Terms of service | read, states 5 of the 7 things a reader expects, and has 1 clause that costs points | 6.3/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | status.together.ai | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | | People named | 6 named with their role, 5 with a public profile | 10/10 | | Support route | help pages, a community | 5/5 | Legal entity, terms, privacy and security.txt as on the Together AI Inference listing, checked 1 November 2026, and not re-read for this listing. docs.together.ai/robots.txt disallows only /cdn-cgi/ and /_next/, with Content-Signal ai-train=yes, search=yes, ai-input=yes. www.together.ai/robots.txt allows all. status.together.ai has no component for GPU clusters on 6 November 2026. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.together.ai/terms-of-service), read 2026-10-08, gives no date, states 5 of the 7 things a reader expects. - To know. Restricts benchmarking or competitive use (costs points). "(c) use or access the Services to develop a product or service that is competitive with the Company’s products or services or engage in competitive analysis or benchmarking;" - Not found in the text. Gives the date it was last updated. - Names the governing law or courts. The law of the State of California. - States a limit on its liability. Capped at the fees paid in the 12 months before the claim. - Not found in the text. Says how changes to the terms are announced. - Also in the text (2026-10-08). The parties owe each other no confidentiality unless they agree it in writing. "The parties will have no confidentiality obligations to each other unless otherwise agreed in writing." - Also in the text (2026-10-08). The customer may not cancel or end the agreement without Together's express written consent. "You may not cancel or terminate this Agreement without our express written consent." - Also in the text (2026-10-08). Customers may not send financial or medical information or sensitive personal data to Together through the services. "You will not use the Services to transmit or provide to the Company any financial or medical information of any nature or any sensitive personal data" **Privacy policy** (https://www.together.ai/privacy), read 2026-10-08, gives no date, states 7 of the 8 things a reader expects. - Not found in the text. Gives the date it was last updated. - Says how long data is kept. For as long as needed, with no period named. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. privacy@together.ai. - Says where data is transferred or stored. Relies on standard contractual clauses. - Also in the text (2026-10-08). Data collected from a customer is not used to train Together's models unless the customer opts in. "We do not use any data collected from you to train our models without your explicit opt-in and consent." - Also in the text (2026-10-08). With Zero Data Retention on, Together cannot later retrieve, correct, export or delete the data, because it is removed once processing ends. "This means we cannot later access, retrieve, correct, export, or delete your Personal Data on your behalf as it is removed from our systems as soon as processing concludes." ## Humans behind the project (researched 2026-11-06 from public pages, not part of the grade) ### Key people - Vipul Ved Prakash, Founder and CEO. LinkedIn: https://www.linkedin.com/in/vipulved/. X: https://x.com/vipulved - Ce Zhang, Founder and CTO. LinkedIn: https://www.linkedin.com/in/ce-zhang-6aa37419/. X: https://x.com/ce__zhang - Tri Dao, Founder and Chief Scientist. LinkedIn: https://www.linkedin.com/in/tri-dao-71544155/. X: https://x.com/tri_dao - Chris Ré, Founder, Together AI - Percy Liang, Founder, Together AI. LinkedIn: https://www.linkedin.com/in/percy-liang-717b8a/. X: https://x.com/percyliang - Charles Zedlewski, Chief Product Officer. LinkedIn: https://www.linkedin.com/in/charleszedlewski/ - Note: From the Our team section of Together AI's about page (read on 28 October 2026), which shows each person in a card with name, title, portrait and their own LinkedIn and X links. It lists five founders (Vipul Ved Prakash as Founder and CEO, Ce Zhang as Founder and CTO, Tri Dao as Founder and Chief Scientist, Chris Ré and Percy Liang as Founder) and Charles Zedlewski as Chief Product Officer, followed by other executives and vice presidents. Copied from the Together AI Inference listing (checked 28 October 2026) for this listing on 6 November 2026; nothing newer was looked for beyond the docs read. On 6 November 2026 the Series C post and Latham & Watkins' note were reread for a cumulative total; neither states how much Together AI has raised in all, so totalRaised is left out rather than summed from the rounds. A TechCrunch report on the Series C was dropped from the sources, as techcrunch.com's robots.txt is off limits; the valuation stays sourced to Latham & Watkins. - Together Computer, Inc.: LinkedIn https://www.linkedin.com/company/togethercomputer/ X https://x.com/togethercompute ### Ownership and investors - Valuation: $8.3B post-money, Series C, July 2026 (source https://www.lw.com/en/news/2026/07/latham-advises-together-ai-in-series-c) - Backed by: Lux Capital, Kleiner Perkins, NVIDIA, Emergence Capital, Salesforce, Coatue, Aramco Ventures, NEA, Greycroft, Definition Capital, Long Journey Ventures, Factory, SV Angel, First Round Capital, A Capital, Robot Ventures, Common Metal, Susa Ventures, Cadenza Ventures, SCB 10x, Scott Banister, Jeff Hammerbacher, Dawn Song, Alex Atallah, MC Lader, Lip-Bu Tan, Jakob Uszkoreit, Marc Bhargava, Jennifer Campbell, Chafic Kazoun, Sabrina Hahn, SongYee Yoon, Chase Lochmiller, Yi Sun, Dave Eisenberg, Panos Madamopoulos-Moraris, Zach Frankel, Clem Delangue, Soumith Chintala, General Catalyst, DAMAC, March Capital, Schneider Electric, Brave Capital, SK Telecom, John Chambers, Vista Equity Partners, Pegatron, DTCP, Geodesic Capital, PSP Partners, SentinelOne ### Getting support - Discord: https://discord.gg/9Rk6sSeWEG - Help: https://support.together.ai/ - Help: https://portal.usepylon.com/together-ai/forms/support-request - Sources: https://www.together.ai/about-us, https://www.linkedin.com/in/vipulved/, https://www.linkedin.com/in/ce-zhang-6aa37419/, https://www.linkedin.com/in/tri-dao-71544155/, https://www.linkedin.com/in/charleszedlewski/details/experience/, https://www.linkedin.com/in/charleszedlewski/, https://www.linkedin.com/in/percy-liang-717b8a/, https://www.together.ai/, https://x.com/togethercompute, https://www.together.ai/support, https://support.together.ai/ ## Live (updated 2026-11-07 18:21 UTC) - Right now: up, HTTP 401, 506 ms, checked 2026-11-07 18:21 UTC (get on `https://api.together.ai/v1/compute/clusters`, asks for auth) - Uptime 24h 100.0% (200 probes) · 30 days 100.0% (200 probes) · p50 491 ms · p95 857 ms - github `togethercomputer/together-py` v3.1.1, released 2026-11-04 - npm `together-ai` 1.0.0 - pypi `together` 3.1.1, released 2026-11-04 - security.txt: valid, expires 2028-09-30T00:00:00.000Z - Always current: https://www.anchorterminal.com/api/v1/live/together-gpu-clusters.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | H100 on-demand | $3.99 | per GPU-hour | reserved $3.69 to $3.19, preemptible $1.99 | | H200 on-demand | $5.99 | per GPU-hour | reserved $4.99 to $3.99, preemptible $2.99 | | B200 on-demand | $8.19 | per GPU-hour | reserved $7.99 to $6.79, preemptible $4.09 | | B300 on-demand | $9.99 | per GPU-hour | preemptible $4.99, reserved by sales | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Public OpenAPI 3.1, llms.txt and Markdown docs, with an automation guide for CI pipelines - Published per GPU-hour prices for on-demand, reserved and preemptible capacity, with no egress fees - Kubernetes or Slurm on the same hardware, with InfiniBand and a persistent shared volume - Automatic health checks and node repair, approved by hand or run automatically - Project-scoped keys, admin-only kubeconfig and OIDC access for team members ## Weaknesses - Provisioning takes 10 minutes to an hour, and a cluster can't be paused or scaled to zero - No status page component, SLA or published rate limits for GPU clusters - No idempotency key on creation, so a retried create can bill a second cluster - No free trial; reservations are prepaid and non-refundable - Volumes bill until deleted and outlive the clusters they were attached to ## Before you call it (notes for agents) 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 ## Connect Install: ```bash uv tool install "together[cli]" ``` First request: ```bash curl -H "Authorization: Bearer $TOGETHER_API_KEY" https://api.together.ai/v1/compute/clusters ``` Through letme: https://letme.dev/together-gpu-clusters. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Nebius AI Cloud | BB | 71.2 | 167 | compute.gpu, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/nebius-ai-cloud.md | | Cloud Run GPUs | B | 68.4 | 288 | compute.gpu, compute.containers, compute.batch | no | https://www.anchorterminal.com/tools/cloud-run-gpus.md | | Modal | B | 62.7 | 543 | compute.gpu, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/modal.md | | Crusoe Cloud | B | 62.4 | 555 | compute.gpu, compute.containers, compute.batch | no | https://www.anchorterminal.com/tools/crusoe-cloud.md | | CoreWeave | C | 60.5 | 645 | compute.gpu, compute.containers, compute.batch | no | https://www.anchorterminal.com/tools/coreweave.md | | Beam | C | 56.2 | 835 | compute.gpu, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/beam.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Together CLI 3.0 and Python SDK 3.0 on 22 October 2026 moved GPU clusters out of `beta` (`tg clusters`, `client.clusters`), and the old `tg beta clusters` paths stopped working, with a migration guide (source: ) - Instant clusters became generally available on 9 September 2025, per the changelog (source: ) - Provisioning usually takes 10 minutes to an hour, depending on size and region, per the quickstart (source: ) - A cluster can't be paused. On-demand clusters bill until deleted, volumes bill until deleted, and when credit runs out an on-demand cluster is paused at once and deleted after a one-hour grace period (source: ) - The automation guide shows a GitHub Actions job that creates an on-demand cluster with `--json`, polls for Ready, runs a Kubernetes job and deletes the cluster with `--non-interactive` (source: ) - status.together.ai lists the website, playground and serverless models, with no component for GPU clusters (source: ) - #10 of 22 in 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 ## Compare - [Baseten vs Together GPU Clusters](https://www.anchorterminal.com/compare/baseten-vs-together-gpu-clusters.md): B 62.7 vs C 58.1 - [Beam vs Together GPU Clusters](https://www.anchorterminal.com/compare/beam-vs-together-gpu-clusters.md): C 56.2 vs C 58.1 - [Cerebrium vs Together GPU Clusters](https://www.anchorterminal.com/compare/cerebrium-vs-together-gpu-clusters.md): D 52.5 vs C 58.1 - [Cloud Run GPUs vs Together GPU Clusters](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-together-gpu-clusters.md): B 68.4 vs C 58.1 - [CoreWeave vs Together GPU Clusters](https://www.anchorterminal.com/compare/coreweave-vs-together-gpu-clusters.md): C 60.5 vs C 58.1 - [Crusoe Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters.md): B 62.4 vs C 58.1 - [GPUsMarket vs Together GPU Clusters](https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.md): E 39.6 vs C 58.1 - [Hugging Face Inference Endpoints vs Together GPU Clusters](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-together-gpu-clusters.md): B 66.7 vs C 58.1 - [Hyperbolic vs Together GPU Clusters](https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters.md): E 38.7 vs C 58.1 - [Koyeb vs Together GPU Clusters](https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters.md): D 46.6 vs C 58.1 - [Lambda Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.md): D 52.9 vs C 58.1 - [Massed Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.md): E 42.6 vs C 58.1 - [Modal vs Together GPU Clusters](https://www.anchorterminal.com/compare/modal-vs-together-gpu-clusters.md): B 62.7 vs C 58.1 - [Nebius AI Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters.md): BB 71.2 vs C 58.1 - [Northflank vs Together GPU Clusters](https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters.md): C 54 vs C 58.1 - [Replicate Deployments vs Together GPU Clusters](https://www.anchorterminal.com/compare/replicate-deploy-vs-together-gpu-clusters.md): B 65.2 vs C 58.1 - [Runpod vs Together GPU Clusters](https://www.anchorterminal.com/compare/runpod-vs-together-gpu-clusters.md): C 55.6 vs C 58.1 - [Thunder Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters.md): D 51.3 vs C 58.1 - [Together GPU Clusters vs Vast.ai](https://www.anchorterminal.com/compare/together-gpu-clusters-vs-vast-ai.md): C 58.1 vs C 56.4 - [Together GPU Clusters vs Verda](https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda.md): C 58.1 vs D 53.3 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on together.ai or one of its subdomains, or the README at the root of github.com/togethercomputer/together-py. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "together-gpu-clusters", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Together GPU Clusters on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Together GPU Clusters on Anchor Terminal](https://www.anchorterminal.com/badges/together-gpu-clusters.svg)](https://www.anchorterminal.com/tools/together-gpu-clusters) ``` Plain link: ```html Together GPU Clusters on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Together GPU Clusters is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/together-gpu-clusters-dark.png - Light: https://www.anchorterminal.com/assets/share/together-gpu-clusters-light.png --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp