{ "data": { "similar": [ { "grade": "BB", "json": "https://www.anchorterminal.com/tools/nebius-ai-cloud.json", "name": "Nebius AI Cloud", "score": 71.2, "shared": [ "compute.gpu", "compute.batch", "compute.containers" ], "slug": "nebius-ai-cloud" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/cloud-run-gpus.json", "name": "Cloud Run GPUs", "score": 68.4, "shared": [ "compute.gpu", "compute.containers", "compute.batch" ], "slug": "cloud-run-gpus" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/modal.json", "name": "Modal", "score": 62.7, "shared": [ "compute.gpu", "compute.batch", "compute.containers" ], "slug": "modal" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/crusoe-cloud.json", "name": "Crusoe Cloud", "score": 62.4, "shared": [ "compute.gpu", "compute.containers", "compute.batch" ], "slug": "crusoe-cloud" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/coreweave.json", "name": "CoreWeave", "score": 60.5, "shared": [ "compute.gpu", "compute.containers", "compute.batch" ], "slug": "coreweave" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/beam.json", "name": "Beam", "score": 56.2, "shared": [ "compute.gpu", "compute.batch", "compute.containers" ], "slug": "beam" } ], "tool": { "slug": "together-gpu-clusters", "name": "Together GPU Clusters", "vendor": "Together AI", "vendorUrl": "https://www.together.ai", "kind": "http-api", "category": "gpu-compute", "summary": "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.", "url": "https://www.anchorterminal.com/tools/together-gpu-clusters", "markdownUrl": "https://www.anchorterminal.com/tools/together-gpu-clusters.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/together-gpu-clusters.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json", "dns": "together-gpu-clusters.grade.anchorterminal.com", "repo": "https://github.com/togethercomputer/together-py", "license": "Proprietary service under Together's terms of service. The Python SDK and CLI are Apache-2.0 and the OpenAPI document is MIT", "transports": [], "remoteUrl": "https://api.together.ai/v1/compute/clusters", "packages": [ { "registry": "pypi", "name": "together" }, { "registry": "npm", "name": "together-ai" } ], "auth": "api-key", "authNotes": "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": "usage", "pricingNotes": "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.", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "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.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.together.ai/docs/gpu-clusters-overview", "llmsTxt": "https://docs.together.ai/llms.txt", "openapi": "https://github.com/togethercomputer/openapi", "capabilities": [ "compute.gpu", "compute.containers", "compute.batch" ], "tags": [ "hosted", "official", "usage", "prepaid", "openapi", "llms-txt", "kubernetes", "slurm", "python", "typescript", "cli", "h100", "b200" ], "lastRelease": "2026-10-22", "graded": true, "anchor": { "graded": true, "score": 58.1, "grade": "C", "agentReady": false, "rank": 764, "ranked": true, "rankOf": 1486, "categoryRank": 10, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 55, "maintenance": 75, "payments": 20, "reliability": 38, "schema": 92, "security": 68, "transparency": 65 }, "pending": [ "performance", "tasks" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 38, "points": 7.6, "reason": "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.", "checked": "2026-11-06" }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "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." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 92, "points": 14.95, "reason": "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.", "checked": "2026-11-06" }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 55, "points": 8.94, "reason": "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.", "checked": "2026-11-06" }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 68, "points": 11.9, "reason": "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.", "checked": "2026-11-06" }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 20, "points": 2.5, "reason": "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.", "checked": "2026-11-06" }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "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." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 75, "points": 6.56, "reason": "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.", "checked": "2026-11-06" }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 65, "points": 5.69, "note": "editorial 46, provenance 83", "reason": "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.", "checked": "2026-11-06" } ], "assessment": { "date": "2026-11-06", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "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.", "maintenance": "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.", "payments": "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.", "reliability": "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.", "schema": "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": "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": "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." }, "sources": [ { "what": "GPU clusters overview", "url": "https://docs.together.ai/docs/gpu-clusters-overview", "seen": "2026-11-06" }, { "what": "GPU clusters pricing", "url": "https://docs.together.ai/docs/gpu-clusters-billing", "seen": "2026-11-06" }, { "what": "manage GPU clusters", "url": "https://docs.together.ai/docs/gpu-clusters-management", "seen": "2026-11-06" }, { "what": "automate cluster operations", "url": "https://docs.together.ai/docs/gpu-clusters-automation", "seen": "2026-11-06" }, { "what": "quickstart", "url": "https://docs.together.ai/docs/gpu-clusters-quickstart", "seen": "2026-11-06" }, { "what": "concepts", "url": "https://docs.together.ai/docs/gpu-clusters-concepts", "seen": "2026-11-06" }, { "what": "preemptible compute", "url": "https://docs.together.ai/docs/preemptible-compute", "seen": "2026-11-06" }, { "what": "create cluster API reference with OpenAPI", "url": "https://docs.together.ai/reference/clusters-create", "seen": "2026-11-06" }, { "what": "list clusters API reference", "url": "https://docs.together.ai/reference/clusters-list", "seen": "2026-11-06" }, { "what": "changelog", "url": "https://docs.together.ai/docs/changelog", "seen": "2026-11-06" }, { "what": "status page", "url": "https://status.together.ai", "seen": "2026-11-06" }, { "what": "llms.txt", "url": "https://docs.together.ai/llms.txt", "seen": "2026-11-06" } ], "openQuestions": [ "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" ] }, "negative": 0, "verdict": "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.", "bestFor": "Training, fine-tuning and batch jobs that need several 8-GPU nodes with InfiniBand, run by a pipeline that creates and deletes clusters.", "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" ], "agentNotes": [ "Use `tg clusters`, not `tg beta clusters`, which stopped working with CLI 3.0 on 22 October 2026", "Pass `--json` and `--non-interactive`, poll `tg clusters retrieve` until status is Ready, and delete the cluster in a cleanup step", "Check for an existing cluster by name before retrying a create, since creation has no idempotency key", "Read live availability from the regions API and prices from the pricing page; the regions response has no prices", "Use a project admin's key when the task needs the kubeconfig, since other roles get none" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58.1 } ], "editorialScores": { "ergonomics": 55, "maintenance": 75, "payments": 20, "reliability": 38, "schema": 92, "security": 68, "transparency": 46 }, "provenanceScore": 83, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 }, "scoreHistory": [ { "date": "2026-11-06", "grade": "C", "kind": "listed", "method": "0.7", "score": 58.1 } ] }, "connect": { "install": "uv tool install \"together[cli]\"", "http": "curl -H \"Authorization: Bearer $TOGETHER_API_KEY\" https://api.together.ai/v1/compute/clusters" }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/together-gpu-clusters" }, "sameCompany": [ "together-inference", "together-fine-tuning", "together-code-sandbox" ], "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 (https://docs.together.ai/docs/changelog)", "Instant clusters became generally available on 9 September 2025, per the changelog (https://docs.together.ai/docs/changelog)", "Provisioning usually takes 10 minutes to an hour, depending on size and region, per the quickstart (https://docs.together.ai/docs/gpu-clusters-quickstart)", "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 (https://docs.together.ai/docs/gpu-clusters-billing)", "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` (https://docs.together.ai/docs/gpu-clusters-automation)", "status.together.ai lists the website, playground and serverless models, with no component for GPU clusters (https://status.together.ai)" ], "area": "models", "details": [ { "label": "Surface listed", "value": "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" }, { "label": "Scope", "value": "Multi-node GPU clusters for training and batch work. Serverless and dedicated inference, fine-tuning and Code Sandbox have separate Anchor Terminal listings" }, { "label": "Hardware", "value": "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" }, { "label": "Cluster types", "value": "Kubernetes, reached with kubectl, or Slurm on Kubernetes through Slinky, reached by SSH to a login node" }, { "label": "Capacity types", "value": "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" }, { "label": "Access", "value": "Project roles admin and editor. Only admins download the admin kubeconfig, which has cluster-admin rights. OIDC gives editors kubectl access under Kubernetes RBAC" }, { "label": "Health", "value": "Active and passive health checks, with repair recommendations that can be approved by hand or run fully automatically" }, { "label": "Lifecycle", "value": "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" } ], "unitPrices": [ { "item": "H100 on-demand", "unit": "gpu-hour", "usd": 3.99, "note": "reserved $3.69 to $3.19, preemptible $1.99" }, { "item": "H200 on-demand", "unit": "gpu-hour", "usd": 5.99, "note": "reserved $4.99 to $3.99, preemptible $2.99" }, { "item": "B200 on-demand", "unit": "gpu-hour", "usd": 8.19, "note": "reserved $7.99 to $6.79, preemptible $4.09" }, { "item": "B300 on-demand", "unit": "gpu-hour", "usd": 9.99, "note": "preemptible $4.99, reserved by sales" } ], "provenance": { "legalEntity": "Together Computer, Inc.", "domain": "together.ai", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.together.ai/terms-of-service", "privacy": "https://www.together.ai/privacy", "statusPage": "https://status.together.ai", "changelog": "https://docs.together.ai/docs/changelog", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "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." ], "score": 83, "checks": [ { "check": "Legal entity named", "value": "Together Computer, Inc.", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "together.ai, no registry record we could read", "points": 0, "max": 15, "state": "no" }, { "check": "Endpoint on the vendor's domain", "value": "api.together.ai", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "read, states 5 of the 7 things a reader expects, and has 1 clause that costs points", "points": 6.3, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "read, states 7 of the 8 things a reader expects", "points": 9.3, "max": 10, "state": "part" }, { "check": "Status page", "value": "status.together.ai", "points": 10, "max": 10, "state": "ok" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "valid", "points": 10, "max": 10, "state": "ok" }, { "check": "People named", "value": "6 named with their role, 5 with a public profile", "points": 10, "max": 10, "state": "ok" }, { "check": "Support route", "value": "help pages, a community", "points": 5, "max": 5, "state": "ok" } ], "policies": [ { "kind": "terms", "url": "https://www.together.ai/terms-of-service", "state": "read", "readAt": "2026-10-08", "words": 3964, "points": 6.3, "max": 10, "expected": [ { "key": "terms.date", "label": "Gives the date it was last updated", "found": false }, { "key": "terms.law", "label": "Names the governing law or courts", "found": true, "quote": "This Agreement will be governed by the laws of the State of California, exclusive of its rules governing choice of law and conflict of laws.", "says": "The law of the State of California" }, { "key": "terms.liability", "label": "States a limit on its liability", "found": true, "quote": "…even if informed of their possibility in advance, or (b) excluding customer's payment obligations, any aggregate liability in excess of the amounts paid by customer during the twelve (12) months preceding the claim (the \"ordinary cap\").", "says": "Capped at the fees paid in the 12 months before the claim" }, { "key": "terms.termination", "label": "Says how the agreement or account can be ended", "found": true, "quote": "The Company may suspend your access to the Services immediately upon notice if you fail to pay any amounts hereunder at least five (5) days past the applicable due date." }, { "key": "terms.changes", "label": "Says how changes to the terms are announced", "found": false }, { "key": "terms.use", "label": "Lists what users may not do", "found": true, "quote": "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 (e.g., social security numbers, driver’s license numbers, birth dates, personal bank account numbers, passport or visa numbers, and/or credit card numbers)." }, { "key": "terms.sla", "label": "Refers to a service level or uptime commitment", "found": true, "quote": "No guarantees are made with respect to the Services’ quality, stability, uptime, or reliability, unless otherwise agreed between the parties in an order form." } ], "toKnow": [ { "key": "terms.benchmark", "label": "Restricts benchmarking or competitive use", "found": true, "quote": "(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;", "costsPoints": true } ], "notes": [ { "date": "2026-10-08", "text": "The parties owe each other no confidentiality unless they agree it in writing.", "quote": "The parties will have no confidentiality obligations to each other unless otherwise agreed in writing." }, { "date": "2026-10-08", "text": "The customer may not cancel or end the agreement without Together's express written consent.", "quote": "You may not cancel or terminate this Agreement without our express written consent." }, { "date": "2026-10-08", "text": "Customers may not send financial or medical information or sensitive personal data to Together through the services.", "quote": "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" } ] }, { "kind": "privacy", "url": "https://www.together.ai/privacy", "state": "read", "readAt": "2026-10-08", "words": 3751, "points": 9.3, "max": 10, "expected": [ { "key": "privacy.date", "label": "Gives the date it was last updated", "found": false }, { "key": "privacy.collected", "label": "Says what personal data is collected", "found": true, "quote": "Data that we collect, including your Personal Data, will not be used to train the Company’s models without your explicit opt-in and consent." }, { "key": "privacy.retention", "label": "Says how long data is kept", "found": true, "quote": "The Company will retain your Personal Data only for as long as is necessary for the purposes set out in this Policy.", "says": "For as long as needed, with no period named" }, { "key": "privacy.processors", "label": "Says who else receives the data", "found": true, "quote": "We may share your Personal Data with Service Providers, Third-Party Vendors, Consultants, and other Business Partners in order to provide Services on our behalf, monitor and analyze the use of our Services, contact you, and for the reasons stated in our Terms of Service." }, { "key": "privacy.sale", "label": "Says whether personal data is sold or shared for advertising", "found": true, "quote": "The Company does not sell your Personal Data as defined under CCPA.", "says": "Says it does not sell personal data" }, { "key": "privacy.rights", "label": "Says what rights people have over their data", "found": true, "quote": "If, in the future, we do sell your Personal Data, we will notify you, and you may have the right to opt out of such sale." }, { "key": "privacy.contact", "label": "Gives a privacy contact", "found": true, "quote": "In order to exercise any other privacy rights not specifically enumerated here, you may contact privacy@together.ai.", "says": "privacy@together.ai" }, { "key": "privacy.transfers", "label": "Says where data is transferred or stored", "found": true, "quote": "When we share Personal Data of individuals in the EEA, Switzerland, or UK with third parties, we make use of a variety of legal mechanisms to safeguard the transfer, including the European Commission-approved standard contractual clauses as well as additional safeguards where appropriate.", "says": "Relies on standard contractual clauses" } ], "notes": [ { "date": "2026-10-08", "text": "Data collected from a customer is not used to train Together's models unless the customer opts in.", "quote": "We do not use any data collected from you to train our models without your explicit opt-in and consent." }, { "date": "2026-10-08", "text": "With Zero Data Retention on, Together cannot later retrieve, correct, export or delete the data, because it is removed once processing ends.", "quote": "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": { "slug": "together-gpu-clusters", "checked": "2026-11-06", "company": "Together Computer, Inc.", "people": [ { "name": "Vipul Ved Prakash", "role": "Founder and CEO", "founder": true, "linkedin": "https://www.linkedin.com/in/vipulved/", "x": "https://x.com/vipulved", "photo": "/assets/img/people/together-computer-inc-vipul-ved-prakash.webp", "photoSource": "https://www.together.ai/about-us", "bio": "Vipul Ved Prakash is founder and CEO of Together AI. He earlier co-founded the anti-spam company Cloudmark and the social media search company Topsy, which Apple acquired in 2013, and created Vipul's Razor, an open-source anti-spam system.", "bioSources": [ "https://www.together.ai/about-us", "https://en.wikipedia.org/wiki/Vipul_Ved_Prakash" ], "page": "/people/vipul-ved-prakash/" }, { "name": "Ce Zhang", "role": "Founder and CTO", "founder": true, "linkedin": "https://www.linkedin.com/in/ce-zhang-6aa37419/", "x": "https://x.com/ce__zhang", "photo": "/assets/img/people/together-computer-inc-ce-zhang.webp", "photoSource": "https://www.together.ai/about-us", "page": "/people/ce-zhang/" }, { "name": "Tri Dao", "role": "Founder and Chief Scientist", "founder": true, "linkedin": "https://www.linkedin.com/in/tri-dao-71544155/", "x": "https://x.com/tri_dao", "photo": "/assets/img/people/together-computer-inc-tri-dao.webp", "photoSource": "https://www.together.ai/about-us", "bio": "Tri Dao is a founder and chief scientist of Together AI. He is first author of FlashAttention, a fast and memory-efficient exact attention algorithm, and co-authored Mamba, a linear-time sequence model, with Albert Gu.", "bioSources": [ "https://www.together.ai/about-us", "https://en.wikipedia.org/wiki/FlashAttention" ], "page": "/people/tri-dao/" }, { "name": "Chris Ré", "role": "Founder, Together AI", "founder": true, "photo": "/assets/img/people/together-computer-inc-chris-re.webp", "photoSource": "https://www.together.ai/about-us", "bio": "Chris Ré is a founder of Together AI and a professor of computer science at Stanford University. He received a MacArthur Fellowship in 2015 and co-founded Lattice.io, a data mining and machine learning company that Apple acquired in 2017.", "bioSources": [ "https://www.together.ai/about-us", "https://en.wikipedia.org/wiki/Christopher_R%C3%A9" ], "page": "/people/chris-re/" }, { "name": "Percy Liang", "role": "Founder, Together AI", "founder": true, "linkedin": "https://www.linkedin.com/in/percy-liang-717b8a/", "x": "https://x.com/percyliang", "photo": "/assets/img/people/together-computer-inc-percy-liang.webp", "photoSource": "https://www.together.ai/about-us", "bio": "Percy Liang is a founder of Together AI and a professor of computer science at Stanford University, where he is founding director of the Center for Research on Foundation Models. His research covers machine learning, natural language processing and foundation models, and he helped develop CodaLab Worksheets.", "bioSources": [ "https://www.together.ai/about-us", "https://en.wikipedia.org/wiki/Percy_Liang" ], "page": "/people/percy-liang/" }, { "name": "Charles Zedlewski", "role": "Chief Product Officer", "linkedin": "https://www.linkedin.com/in/charleszedlewski/", "photo": "/assets/img/people/together-computer-inc-charles-zedlewski.webp", "photoSource": "https://www.together.ai/about-us", "page": "/people/charles-zedlewski/" } ], "peopleNote": "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 \u0026 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 \u0026 Watkins.", "companySocial": { "linkedin": "https://www.linkedin.com/company/togethercomputer/", "x": "https://x.com/togethercompute" }, "support": { "urls": [ "https://support.together.ai/", "https://portal.usepylon.com/together-ai/forms/support-request" ], "community": [ { "label": "Discord", "url": "https://discord.gg/9Rk6sSeWEG", "kind": "discord" } ], "contactUrls": [ "https://www.together.ai/contact-sales" ] }, "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/" ], "ownership": { "status": "private", "valuation": { "amount": "$8.3B", "basis": "post-money", "round": "Series C", "asOf": "2026-07-01", "source": "https://www.lw.com/en/news/2026/07/latham-advises-together-ai-in-series-c" }, "checked": "2026-10-28", "sources": [ "https://www.together.ai/blog/announcing-our-series-c", "https://www.lw.com/en/news/2026/07/latham-advises-together-ai-in-series-c", "https://www.together.ai/blog/together-ai-announcing-305m-series-b", "https://www.together.ai/blog/series-a2", "https://www.together.ai/blog/series-a", "https://www.together.ai/blog/seed-funding" ] }, "investors": [ { "name": "Lux Capital", "kind": "vc", "rounds": [ "Seed, May 2023", "Series A extension, March 2024", "Series B, February 2025", "Series C, July 2026" ], "lead": true, "url": "https://www.luxcapital.com", "source": "https://www.together.ai/blog/seed-funding", "quote": "our $20M seed round funding round led by Lux Capital", "page": "/investors/lux-capital/" }, { "name": "Kleiner Perkins", "kind": "vc", "rounds": [ "Series A, November 2023", "Series A extension, March 2024", "Series B, February 2025" ], "lead": true, "url": "https://www.kleinerperkins.com", "source": "https://www.together.ai/blog/series-a", "quote": "The round is led by Kleiner Perkins, with participation from an incredible group of investors, including NVIDIA and Emergence Capital.", "page": "/investors/kleiner-perkins/" }, { "name": "NVIDIA", "kind": "corporate", "rounds": [ "Series A, November 2023", "Series B, February 2025", "Series C, July 2026" ], "url": "https://www.nvidia.com", "source": "https://www.together.ai/blog/series-a", "quote": "with participation from an incredible group of investors, including NVIDIA and Emergence Capital", "page": "/investors/nvidia/" }, { "name": "Emergence Capital", "kind": "vc", "rounds": [ "Series A, November 2023", "Series A extension, March 2024", "Series B, February 2025", "Series C, July 2026" ], "url": "https://www.emcap.com", "source": "https://www.together.ai/blog/series-a", "quote": "with participation from an incredible group of investors, including NVIDIA and Emergence Capital", "page": "/investors/emergence-capital/" }, { "name": "Salesforce Ventures", "firm": "Salesforce", "kind": "corporate", "rounds": [ "Series A extension, March 2024", "Series B, February 2025", "Series C, July 2026" ], "lead": true, "url": "https://salesforceventures.com", "source": "https://www.together.ai/blog/series-a2", "quote": "we've raised $106M in a new round of financing led by Salesforce Ventures with participation from Coatue", "page": "/investors/salesforce/" }, { "name": "Coatue", "kind": "vc", "rounds": [ "Series A extension, March 2024", "Series B, February 2025" ], "url": "https://www.coatue.com", "source": "https://www.together.ai/blog/series-a2", "quote": "led by Salesforce Ventures with participation from Coatue", "page": "/investors/coatue/" }, { "name": "Prosperity7 Ventures", "firm": "Aramco Ventures", "kind": "corporate", "rounds": [ "Series A extension, March 2024", "Series B, February 2025" ], "lead": true, "source": "https://www.together.ai/blog/together-ai-announcing-305m-series-b", "quote": "our $305 million Series B funding round, led by General Catalyst and co-led by Prosperity7", "page": "/investors/aramco-ventures/" }, { "name": "NEA", "kind": "vc", "rounds": [ "Series A extension, March 2024" ], "url": "https://www.nea.com", "source": "https://www.together.ai/blog/series-a2", "quote": "existing investors, Lux Capital, Kleiner Perkins, Emergence Capital, Prosperity7 Ventures, NEA, Greycroft, Definition Capital, Long Journey Ventures, Factory, Scott Banister, and SV Angel", "page": "/investors/nea/" }, { "name": "Greycroft", "kind": "vc", "rounds": [ "Series A extension, March 2024", "Series B, February 2025" ], "url": "https://www.greycroft.com", "source": "https://www.together.ai/blog/series-a2", "quote": "existing investors, Lux Capital, Kleiner Perkins, Emergence Capital, Prosperity7 Ventures, NEA, Greycroft, Definition Capital", "page": "/investors/greycroft/" }, { "name": "Definition Capital", "kind": "vc", "rounds": [ "Seed, May 2023", "Series A extension, March 2024", "Series B, February 2025" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "invested along with our leads in this funding round, including Factory, SV Angel, First Round Capital, Long Journey Ventures, A Capital, Robot Ventures, Common Metal, Definition Capital", "page": "/investors/definition-capital/" }, { "name": "Long Journey Ventures", "kind": "vc", "rounds": [ "Seed, May 2023", "Series A extension, March 2024", "Series B, February 2025" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "invested along with our leads in this funding round, including Factory, SV Angel, First Round Capital, Long Journey Ventures", "page": "/investors/long-journey-ventures/" }, { "name": "Factory", "kind": "vc", "rounds": [ "Seed, May 2023", "Series A extension, March 2024" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "invested along with our leads in this funding round, including Factory, SV Angel, First Round Capital", "page": "/investors/factory/" }, { "name": "SV Angel", "kind": "vc", "rounds": [ "Seed, May 2023", "Series A extension, March 2024" ], "url": "https://svangel.com", "source": "https://www.together.ai/blog/seed-funding", "quote": "invested along with our leads in this funding round, including Factory, SV Angel, First Round Capital", "page": "/investors/sv-angel/" }, { "name": "First Round Capital", "kind": "vc", "rounds": [ "Seed, May 2023" ], "url": "https://firstround.com", "source": "https://www.together.ai/blog/seed-funding", "quote": "invested along with our leads in this funding round, including Factory, SV Angel, First Round Capital", "page": "/investors/first-round-capital/" }, { "name": "A Capital", "kind": "vc", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "invested along with our leads in this funding round, including Factory, SV Angel, First Round Capital, Long Journey Ventures, A Capital", "page": "/investors/a-capital/" }, { "name": "Robot Ventures", "kind": "vc", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "invested along with our leads in this funding round, including ... A Capital, Robot Ventures, Common Metal", "page": "/investors/robot-ventures/" }, { "name": "Common Metal", "kind": "vc", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "invested along with our leads in this funding round, including ... Robot Ventures, Common Metal, Definition Capital", "page": "/investors/common-metal/" }, { "name": "Susa Ventures", "kind": "vc", "rounds": [ "Seed, May 2023" ], "url": "https://www.susaventures.com", "source": "https://www.together.ai/blog/seed-funding", "quote": "invested along with our leads in this funding round, including ... Definition Capital, Susa Ventures, Cadenza Ventures, SCB 10x", "page": "/investors/susa-ventures/" }, { "name": "Cadenza Ventures", "kind": "vc", "rounds": [ "Seed, May 2023", "Series B, February 2025" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "invested along with our leads in this funding round, including ... Susa Ventures, Cadenza Ventures, SCB 10x", "page": "/investors/cadenza-ventures/" }, { "name": "SCB 10x", "kind": "corporate", "rounds": [ "Seed, May 2023" ], "url": "https://www.scb10x.com", "source": "https://www.together.ai/blog/seed-funding", "quote": "invested along with our leads in this funding round, including ... Cadenza Ventures, SCB 10x, Scott Banister, the co-founder of PayPal", "page": "/investors/scb-10x/" }, { "name": "Scott Banister", "kind": "angel", "rounds": [ "Seed, May 2023", "Series A extension, March 2024", "Series B, February 2025" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "Scott Banister, the co-founder of PayPal", "page": "/investors/scott-banister/" }, { "name": "Jeff Hammerbacher", "kind": "angel", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "Jeff Hammerbacher, the co-founder of Cloudera", "page": "/investors/jeff-hammerbacher/" }, { "name": "Dawn Song", "kind": "angel", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "Dawn Song, the co-founder of Oasis Labs", "page": "/investors/dawn-song/" }, { "name": "Alex Atallah", "kind": "angel", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "Alex Atallah, the co-founder of OpenSea", "page": "/investors/alex-atallah/" }, { "name": "MC Lader", "kind": "angel", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "MC Lader, the COO of Uniswap", "page": "/investors/mc-lader/" }, { "name": "Lip-Bu Tan", "kind": "angel", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "Lip-Bu Tan, the founder of Cadence Systems", "page": "/investors/lip-bu-tan/" }, { "name": "Jakob Uszkoreit", "kind": "angel", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "Jakob Uszkoreit, the co-inventor of the Transformer architecture", "page": "/investors/jakob-uszkoreit/" }, { "name": "Marc Bhargava", "kind": "angel", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "as well as angel investors Marc Bhargava, Jennifer Campbell, Chafic Kazoun, Sabrina Hahn, SongYee Yoon, Chase Lochmiller, Yi Sun, Dave Eisenberg, Panos Madamopoulos-Moraris, and Zach Frankel", "page": "/investors/marc-bhargava/" }, { "name": "Jennifer Campbell", "kind": "angel", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "as well as angel investors Marc Bhargava, Jennifer Campbell, Chafic Kazoun, Sabrina Hahn, SongYee Yoon, Chase Lochmiller, Yi Sun, Dave Eisenberg, Panos Madamopoulos-Moraris, and Zach Frankel", "page": "/investors/jennifer-campbell/" }, { "name": "Chafic Kazoun", "kind": "angel", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "as well as angel investors Marc Bhargava, Jennifer Campbell, Chafic Kazoun, Sabrina Hahn, SongYee Yoon, Chase Lochmiller, Yi Sun, Dave Eisenberg, Panos Madamopoulos-Moraris, and Zach Frankel", "page": "/investors/chafic-kazoun/" }, { "name": "Sabrina Hahn", "kind": "angel", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "as well as angel investors Marc Bhargava, Jennifer Campbell, Chafic Kazoun, Sabrina Hahn, SongYee Yoon, Chase Lochmiller, Yi Sun, Dave Eisenberg, Panos Madamopoulos-Moraris, and Zach Frankel", "page": "/investors/sabrina-hahn/" }, { "name": "SongYee Yoon", "kind": "angel", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "as well as angel investors Marc Bhargava, Jennifer Campbell, Chafic Kazoun, Sabrina Hahn, SongYee Yoon, Chase Lochmiller, Yi Sun, Dave Eisenberg, Panos Madamopoulos-Moraris, and Zach Frankel", "page": "/investors/songyee-yoon/" }, { "name": "Chase Lochmiller", "kind": "angel", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "as well as angel investors Marc Bhargava, Jennifer Campbell, Chafic Kazoun, Sabrina Hahn, SongYee Yoon, Chase Lochmiller, Yi Sun, Dave Eisenberg, Panos Madamopoulos-Moraris, and Zach Frankel", "page": "/investors/chase-lochmiller/" }, { "name": "Yi Sun", "kind": "angel", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "as well as angel investors Marc Bhargava, Jennifer Campbell, Chafic Kazoun, Sabrina Hahn, SongYee Yoon, Chase Lochmiller, Yi Sun, Dave Eisenberg, Panos Madamopoulos-Moraris, and Zach Frankel", "page": "/investors/yi-sun/" }, { "name": "Dave Eisenberg", "kind": "angel", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "as well as angel investors Marc Bhargava, Jennifer Campbell, Chafic Kazoun, Sabrina Hahn, SongYee Yoon, Chase Lochmiller, Yi Sun, Dave Eisenberg, Panos Madamopoulos-Moraris, and Zach Frankel", "page": "/investors/dave-eisenberg/" }, { "name": "Panos Madamopoulos-Moraris", "kind": "angel", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "as well as angel investors Marc Bhargava, Jennifer Campbell, Chafic Kazoun, Sabrina Hahn, SongYee Yoon, Chase Lochmiller, Yi Sun, Dave Eisenberg, Panos Madamopoulos-Moraris, and Zach Frankel", "page": "/investors/panos-madamopoulos-moraris/" }, { "name": "Zach Frankel", "kind": "angel", "rounds": [ "Seed, May 2023" ], "source": "https://www.together.ai/blog/seed-funding", "quote": "as well as angel investors Marc Bhargava, Jennifer Campbell, Chafic Kazoun, Sabrina Hahn, SongYee Yoon, Chase Lochmiller, Yi Sun, Dave Eisenberg, Panos Madamopoulos-Moraris, and Zach Frankel", "page": "/investors/zach-frankel/" }, { "name": "Clem Delangue", "kind": "angel", "rounds": [ "Series A extension, March 2024" ], "source": "https://www.together.ai/blog/series-a2", "quote": "participation from industry luminaries including Clem Delangue, CEO of HuggingFace, and Soumith Chintala, the creator of PyTorch", "page": "/investors/clem-delangue/" }, { "name": "Soumith Chintala", "kind": "angel", "rounds": [ "Series A extension, March 2024" ], "source": "https://www.together.ai/blog/series-a2", "quote": "participation from industry luminaries including Clem Delangue, CEO of HuggingFace, and Soumith Chintala, the creator of PyTorch", "page": "/investors/soumith-chintala/" }, { "name": "General Catalyst", "kind": "vc", "rounds": [ "Series B, February 2025", "Series C, July 2026" ], "lead": true, "url": "https://www.generalcatalyst.com", "source": "https://www.together.ai/blog/together-ai-announcing-305m-series-b", "quote": "our $305 million Series B funding round, led by General Catalyst and co-led by Prosperity7", "page": "/investors/general-catalyst/" }, { "name": "DAMAC Capital", "firm": "DAMAC", "kind": "corporate", "rounds": [ "Series B, February 2025" ], "source": "https://www.together.ai/blog/together-ai-announcing-305m-series-b", "quote": "participation from a distinguished group of global institutional and strategic investors including Salesforce Ventures, DAMAC Capital, NVIDIA, Kleiner Perkins, March Capital", "page": "/investors/damac/" }, { "name": "March Capital", "kind": "vc", "rounds": [ "Series B, February 2025", "Series C, July 2026" ], "url": "https://www.marchcp.com", "source": "https://www.together.ai/blog/together-ai-announcing-305m-series-b", "quote": "including Salesforce Ventures, DAMAC Capital, NVIDIA, Kleiner Perkins, March Capital, Emergence Capital, Lux Capital, SE Ventures", "page": "/investors/march-capital/" }, { "name": "SE Ventures", "firm": "Schneider Electric", "kind": "corporate", "rounds": [ "Series B, February 2025", "Series C, July 2026" ], "source": "https://www.together.ai/blog/together-ai-announcing-305m-series-b", "quote": "March Capital, Emergence Capital, Lux Capital, SE Ventures, Greycroft, Coatue, Definition, Cadenza Ventures", "page": "/investors/schneider-electric/" }, { "name": "Brave Capital", "kind": "vc", "rounds": [ "Series B, February 2025" ], "source": "https://www.together.ai/blog/together-ai-announcing-305m-series-b", "quote": "Cadenza Ventures, Long Journey Ventures, Brave Capital, Scott Banister, SK Telecom, and technology pioneer John Chambers", "page": "/investors/brave-capital/" }, { "name": "SK Telecom", "kind": "corporate", "rounds": [ "Series B, February 2025" ], "url": "https://www.sktelecom.com", "source": "https://www.together.ai/blog/together-ai-announcing-305m-series-b", "quote": "Brave Capital, Scott Banister, SK Telecom, and technology pioneer John Chambers", "page": "/investors/sk-telecom/" }, { "name": "John Chambers", "kind": "angel", "rounds": [ "Series B, February 2025" ], "source": "https://www.together.ai/blog/together-ai-announcing-305m-series-b", "quote": "SK Telecom, and technology pioneer John Chambers", "page": "/investors/john-chambers/" }, { "name": "Aramco Ventures", "kind": "corporate", "rounds": [ "Series C, July 2026" ], "lead": true, "url": "https://www.aramcoventures.com", "source": "https://www.lw.com/en/news/2026/07/latham-advises-together-ai-in-series-c", "quote": "The round was led by Aramco Ventures, with participation from Vista Equity Partners, General Catalyst, Emergence Capital, NVIDIA, March Capital, Pegatron, S Ventures (SentinelOne), and others.", "page": "/investors/aramco-ventures/" }, { "name": "Vista Equity", "firm": "Vista Equity Partners", "kind": "vc", "rounds": [ "Series C, July 2026" ], "url": "https://www.vistaequitypartners.com", "source": "https://www.together.ai/blog/announcing-our-series-c", "quote": "including Aramco Ventures, NVIDIA, Vista Equity, General Catalyst, Emergence Capital, SE Ventures, Pegatron", "page": "/investors/vista-equity-partners/" }, { "name": "Pegatron", "kind": "corporate", "rounds": [ "Series C, July 2026" ], "source": "https://www.together.ai/blog/announcing-our-series-c", "quote": "Emergence Capital, SE Ventures, Pegatron, Salesforce Ventures, March Capital, DTCP Growth", "page": "/investors/pegatron/" }, { "name": "DTCP Growth", "firm": "DTCP", "kind": "vc", "rounds": [ "Series C, July 2026" ], "source": "https://www.together.ai/blog/announcing-our-series-c", "quote": "Salesforce Ventures, March Capital, DTCP Growth, Lux Capital, Geodesic, PSP Partners, and others", "page": "/investors/dtcp/" }, { "name": "Geodesic", "firm": "Geodesic Capital", "kind": "vc", "rounds": [ "Series C, July 2026" ], "source": "https://www.together.ai/blog/announcing-our-series-c", "quote": "DTCP Growth, Lux Capital, Geodesic, PSP Partners, and others", "page": "/investors/geodesic-capital/" }, { "name": "PSP Partners", "kind": "vc", "rounds": [ "Series C, July 2026" ], "source": "https://www.together.ai/blog/announcing-our-series-c", "quote": "Lux Capital, Geodesic, PSP Partners, and others", "page": "/investors/psp-partners/" }, { "name": "S Ventures", "firm": "SentinelOne", "kind": "corporate", "rounds": [ "Series C, July 2026" ], "url": "https://www.sentinelone.com", "source": "https://www.lw.com/en/news/2026/07/latham-advises-together-ai-in-series-c", "quote": "with participation from Vista Equity Partners, General Catalyst, Emergence Capital, NVIDIA, March Capital, Pegatron, S Ventures (SentinelOne), and others", "page": "/investors/sentinelone/" } ] }, "pageJsonUrl": "https://www.anchorterminal.com/tools/together-gpu-clusters.json", "live": { "slug": "together-gpu-clusters", "probe": { "target": "https://api.together.ai/v1/compute/clusters", "method": "get", "lastAt": "2026-11-07T17:50:12.253269108Z", "lastOk": true, "lastStatus": 401, "lastMs": 578, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 488, "p95ms24h": 861, "samples24h": 195, "samples30d": 195, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 182, "ok": 182 } ] }, "versions": [ { "registry": "github", "name": "togethercomputer/together-py", "version": "v3.1.1", "released": "2026-11-04", "seenAt": "2026-11-07T00:12:15.100983119Z" }, { "registry": "npm", "name": "together-ai", "version": "1.0.0", "seenAt": "2026-11-07T00:12:15.067840103Z" }, { "registry": "pypi", "name": "together", "version": "3.1.1", "released": "2026-11-04", "seenAt": "2026-11-07T00:12:14.921893617Z" } ], "githubStars": 12, "npmWeekly": 99619, "pypiWeekly": 424792, "securityTxt": { "url": "https://together.ai/.well-known/security.txt", "state": "valid", "expires": "2028-09-30T00:00:00.000Z", "checkedAt": "2026-11-07T16:00:47.073630606Z" }, "llmsTxt": { "url": "https://docs.together.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:12.138384896Z" }, "updatedAt": "2026-11-07T17:50:12.253269108Z" } }, "verify": { "accepts": "a page on together.ai or one of its subdomains, or the README at the root of github.com/togethercomputer/together-py", "badgeUrl": "https://www.anchorterminal.com/badges/together-gpu-clusters.svg", "body": { "slug": "together-gpu-clusters", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/together-gpu-clusters", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/together-gpu-clusters\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/together-gpu-clusters.svg\" alt=\"Together GPU Clusters on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![Together GPU Clusters on Anchor Terminal](https://www.anchorterminal.com/badges/together-gpu-clusters.svg)](https://www.anchorterminal.com/tools/together-gpu-clusters)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/together-gpu-clusters\"\u003eTogether GPU Clusters on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/together-gpu-clusters", "json": "https://www.anchorterminal.com/tools/together-gpu-clusters.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/together-gpu-clusters.md", "mcp": "https://www.anchorterminal.com/mcp", "pricing": "https://www.anchorterminal.com/tools/together-gpu-clusters#pricing", "reviews": "https://www.anchorterminal.com/tools/together-gpu-clusters#reviews", "slim": "https://www.anchorterminal.com/tools/together-gpu-clusters.min.md" }, "markdown": "## Overview\n\n**Grade C · 58.1/100 · rank #764 of 1486 · #10 in GPU \u0026 serverless compute · not agent-ready · confidence medium**\n\n\nMore from Together AI, listed separately because each is its own product: [Together AI Inference](https://www.anchorterminal.com/tools/together-inference.md) (Model APIs \u0026 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).\n\n## Assessment\n\nMulti-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.\n\n## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | Together AI (https://www.together.ai) |\n| Kind | HTTP API |\n| Category | GPU \u0026 serverless compute (https://www.anchorterminal.com/categories/gpu-compute) |\n| Endpoint | `https://api.together.ai/v1/compute/clusters` |\n| 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. |\n| 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. |\n| 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. |\n| Licence | Proprietary service under Together's terms of service. The Python SDK and CLI are Apache-2.0 and the OpenAPI document is MIT |\n| Packages | pypi: `together`; npm: `together-ai` |\n| Source | https://github.com/togethercomputer/together-py |\n| Docs | https://docs.together.ai/docs/gpu-clusters-overview |\n| llms.txt | https://docs.together.ai/llms.txt |\n| Last release | 2026-10-22 |\n| 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 |\n| Scope | Multi-node GPU clusters for training and batch work. Serverless and dedicated inference, fine-tuning and Code Sandbox have separate Anchor Terminal listings |\n| 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 |\n| Cluster types | Kubernetes, reached with kubectl, or Slurm on Kubernetes through Slinky, reached by SSH to a login node |\n| 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 |\n| 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 |\n| Health | Active and passive health checks, with repair recommendations that can be approved by hand or run fully automatically |\n| 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 |\n| Capabilities | compute.gpu, compute.containers, compute.batch |\n| Tags | hosted, official, usage, prepaid, openapi, llms-txt, kubernetes, slurm, python, typescript, cli, h100, b200 |\n| JSON | https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json |\n\n## Score breakdown (methodology v0.7, October 2026 research run)\n\nAssessed 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.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 38 | 7.6 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 92 | 14.9 |\n| Agent ergonomics | 13% | 16.2 | 55 | 8.9 |\n| Security \u0026 auth | 14% | 17.5 | 68 | 11.9 |\n| Payments \u0026 pricing | 10% | 12.5 | 20 | 2.5 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 75 | 6.6 |\n| Transparency \u0026 trust (editorial 46, provenance 83) | 7% | 8.8 | 65 | 5.7 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **58.1 → C** |\n\n### Why each score\n\n- 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.\n- 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.\n- Schema \u0026 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.\n- 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.\n- Security \u0026 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.\n- Payments \u0026 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.\n- 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.\n- Maintenance \u0026 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.\n- Transparency \u0026 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.\n\nFix 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\n\n### What we couldn't check\n\n- unchecked: rate limits and 429 behaviour on the clusters API, which the reviewed pages don't state\n- unchecked: whether the SLA language in Together's terms covers GPU clusters\n- 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\n- GitHub's API was rate-limited during this run, so SDK stars and CI status were not read\n\n### Sources\n\n- GPU clusters overview: \u003chttps://docs.together.ai/docs/gpu-clusters-overview\u003e (seen 2026-11-06)\n- GPU clusters pricing: \u003chttps://docs.together.ai/docs/gpu-clusters-billing\u003e (seen 2026-11-06)\n- manage GPU clusters: \u003chttps://docs.together.ai/docs/gpu-clusters-management\u003e (seen 2026-11-06)\n- automate cluster operations: \u003chttps://docs.together.ai/docs/gpu-clusters-automation\u003e (seen 2026-11-06)\n- quickstart: \u003chttps://docs.together.ai/docs/gpu-clusters-quickstart\u003e (seen 2026-11-06)\n- concepts: \u003chttps://docs.together.ai/docs/gpu-clusters-concepts\u003e (seen 2026-11-06)\n- preemptible compute: \u003chttps://docs.together.ai/docs/preemptible-compute\u003e (seen 2026-11-06)\n- create cluster API reference with OpenAPI: \u003chttps://docs.together.ai/reference/clusters-create\u003e (seen 2026-11-06)\n- list clusters API reference: \u003chttps://docs.together.ai/reference/clusters-list\u003e (seen 2026-11-06)\n- changelog: \u003chttps://docs.together.ai/docs/changelog\u003e (seen 2026-11-06)\n- status page: \u003chttps://status.together.ai\u003e (seen 2026-11-06)\n- llms.txt: \u003chttps://docs.together.ai/llms.txt\u003e (seen 2026-11-06)\n\n## Score history\n\nEvery 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\n\n- 2026-11-06: graded 58.1 C (methodology 0.7)\n\n## Who's behind it (provenance 83/100, checked 2026-11-06)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | Together Computer, Inc. | 20/20 |\n| Domain age | together.ai, no registry record we could read | 0/15 |\n| Endpoint on the vendor's domain | api.together.ai | 15/15 |\n| Terms of service | read, states 5 of the 7 things a reader expects, and has 1 clause that costs points | 6.3/10 |\n| Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 |\n| Status page | status.together.ai | 10/10 |\n| Changelog | published | 10/10 |\n| security.txt | valid | 10/10 |\n| People named | 6 named with their role, 5 with a public profile | 10/10 |\n| Support route | help pages, a community | 5/5 |\n\nLegal entity, terms, privacy and security.txt as on the Together AI Inference listing, checked 1 November 2026, and not re-read for this listing.\n\ndocs.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.\n\nstatus.together.ai has no component for GPU clusters on 6 November 2026.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**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.\n\n- 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;\"\n- Not found in the text. Gives the date it was last updated.\n- Names the governing law or courts. The law of the State of California.\n- States a limit on its liability. Capped at the fees paid in the 12 months before the claim.\n- Not found in the text. Says how changes to the terms are announced.\n- 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.\"\n- 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.\"\n- 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\"\n\n**Privacy policy** (https://www.together.ai/privacy), read 2026-10-08, gives no date, states 7 of the 8 things a reader expects.\n\n- Not found in the text. Gives the date it was last updated.\n- Says how long data is kept. For as long as needed, with no period named.\n- Says whether personal data is sold or shared for advertising. Says it does not sell personal data.\n- Gives a privacy contact. privacy@together.ai.\n- Says where data is transferred or stored. Relies on standard contractual clauses.\n- 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.\"\n- 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.\"\n\n## Humans behind the project (researched 2026-11-06 from public pages, not part of the grade)\n\n### Key people\n\n- Vipul Ved Prakash, Founder and CEO. LinkedIn: https://www.linkedin.com/in/vipulved/. X: https://x.com/vipulved\n- Ce Zhang, Founder and CTO. LinkedIn: https://www.linkedin.com/in/ce-zhang-6aa37419/. X: https://x.com/ce__zhang\n- Tri Dao, Founder and Chief Scientist. LinkedIn: https://www.linkedin.com/in/tri-dao-71544155/. X: https://x.com/tri_dao\n- Chris Ré, Founder, Together AI\n- Percy Liang, Founder, Together AI. LinkedIn: https://www.linkedin.com/in/percy-liang-717b8a/. X: https://x.com/percyliang\n- Charles Zedlewski, Chief Product Officer. LinkedIn: https://www.linkedin.com/in/charleszedlewski/\n- 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 \u0026 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 \u0026 Watkins.\n- Together Computer, Inc.: LinkedIn https://www.linkedin.com/company/togethercomputer/ X https://x.com/togethercompute\n\n### Ownership and investors\n\n- 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)\n- 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\n\n### Getting support\n\n- Discord: https://discord.gg/9Rk6sSeWEG\n- Help: https://support.together.ai/\n- Help: https://portal.usepylon.com/together-ai/forms/support-request\n- 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/\n\n## Live (updated 2026-11-07 17:50 UTC)\n\n- Right now: up, HTTP 401, 578 ms, checked 2026-11-07 17:50 UTC (get on `https://api.together.ai/v1/compute/clusters`, asks for auth)\n- Uptime 24h 100.0% (195 probes) · 30 days 100.0% (195 probes) · p50 488 ms · p95 861 ms\n- github `togethercomputer/together-py` v3.1.1, released 2026-11-04\n- npm `together-ai` 1.0.0\n- pypi `together` 3.1.1, released 2026-11-04\n- security.txt: valid, expires 2028-09-30T00:00:00.000Z\n- Always current: https://www.anchorterminal.com/api/v1/live/together-gpu-clusters.json\n\n## Probe metrics\n\nNot 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.\n\n## Prices\n\n| Item | Price | Unit | Note |\n| --- | --- | --- | --- |\n| H100 on-demand | $3.99 | per GPU-hour | reserved $3.69 to $3.19, preemptible $1.99 |\n| H200 on-demand | $5.99 | per GPU-hour | reserved $4.99 to $3.99, preemptible $2.99 |\n| B200 on-demand | $8.19 | per GPU-hour | reserved $7.99 to $6.79, preemptible $4.09 |\n| B300 on-demand | $9.99 | per GPU-hour | preemptible $4.99, reserved by sales |\n\nAcross all listings: https://www.anchorterminal.com/prices/index.md\n\n## Strengths\n\n- Public OpenAPI 3.1, llms.txt and Markdown docs, with an automation guide for CI pipelines\n- Published per GPU-hour prices for on-demand, reserved and preemptible capacity, with no egress fees\n- Kubernetes or Slurm on the same hardware, with InfiniBand and a persistent shared volume\n- Automatic health checks and node repair, approved by hand or run automatically\n- Project-scoped keys, admin-only kubeconfig and OIDC access for team members\n\n## Weaknesses\n\n- Provisioning takes 10 minutes to an hour, and a cluster can't be paused or scaled to zero\n- No status page component, SLA or published rate limits for GPU clusters\n- No idempotency key on creation, so a retried create can bill a second cluster\n- No free trial; reservations are prepaid and non-refundable\n- Volumes bill until deleted and outlive the clusters they were attached to\n\n\n\n## Before you call it (notes for agents)\n\n1. Use `tg clusters`, not `tg beta clusters`, which stopped working with CLI 3.0 on 22 October 2026\n2. Pass `--json` and `--non-interactive`, poll `tg clusters retrieve` until status is Ready, and delete the cluster in a cleanup step\n3. Check for an existing cluster by name before retrying a create, since creation has no idempotency key\n4. Read live availability from the regions API and prices from the pricing page; the regions response has no prices\n5. Use a project admin's key when the task needs the kubeconfig, since other roles get none\n\n## Connect\n\nInstall:\n\n```bash\nuv tool install \"together[cli]\"\n```\n\nFirst request:\n\n```bash\ncurl -H \"Authorization: Bearer $TOGETHER_API_KEY\" https://api.together.ai/v1/compute/clusters\n```\n\nThrough 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\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| Nebius AI Cloud | BB | 71.2 | 167 | compute.gpu, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/nebius-ai-cloud.md |\n| Cloud Run GPUs | B | 68.4 | 288 | compute.gpu, compute.containers, compute.batch | no | https://www.anchorterminal.com/tools/cloud-run-gpus.md |\n| Modal | B | 62.7 | 543 | compute.gpu, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/modal.md |\n| Crusoe Cloud | B | 62.4 | 555 | compute.gpu, compute.containers, compute.batch | no | https://www.anchorterminal.com/tools/crusoe-cloud.md |\n| CoreWeave | C | 60.5 | 645 | compute.gpu, compute.containers, compute.batch | no | https://www.anchorterminal.com/tools/coreweave.md |\n| Beam | C | 56.2 | 835 | compute.gpu, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/beam.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk 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\n\n## Notable\n\n- 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: \u003chttps://docs.together.ai/docs/changelog\u003e)\n- Instant clusters became generally available on 9 September 2025, per the changelog (source: \u003chttps://docs.together.ai/docs/changelog\u003e)\n- Provisioning usually takes 10 minutes to an hour, depending on size and region, per the quickstart (source: \u003chttps://docs.together.ai/docs/gpu-clusters-quickstart\u003e)\n- 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: \u003chttps://docs.together.ai/docs/gpu-clusters-billing\u003e)\n- 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: \u003chttps://docs.together.ai/docs/gpu-clusters-automation\u003e)\n- status.together.ai lists the website, playground and serverless models, with no component for GPU clusters (source: \u003chttps://status.together.ai\u003e)\n\n- #10 of 22 in Best GPU and serverless compute for AI workloads: https://www.anchorterminal.com/best/gpu-compute/index.md\n- All 231 gpu compute comparisons: https://www.anchorterminal.com/compare/gpu-compute/index.md\n\n## Compare\n\n- [Baseten vs Together GPU Clusters](https://www.anchorterminal.com/compare/baseten-vs-together-gpu-clusters.md): B 62.7 vs C 58.1\n- [Beam vs Together GPU Clusters](https://www.anchorterminal.com/compare/beam-vs-together-gpu-clusters.md): C 56.2 vs C 58.1\n- [Cerebrium vs Together GPU Clusters](https://www.anchorterminal.com/compare/cerebrium-vs-together-gpu-clusters.md): D 52.5 vs C 58.1\n- [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\n- [CoreWeave vs Together GPU Clusters](https://www.anchorterminal.com/compare/coreweave-vs-together-gpu-clusters.md): C 60.5 vs C 58.1\n- [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\n- [GPUsMarket vs Together GPU Clusters](https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.md): E 39.6 vs C 58.1\n- [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\n- [Hyperbolic vs Together GPU Clusters](https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters.md): E 38.7 vs C 58.1\n- [Koyeb vs Together GPU Clusters](https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters.md): D 46.6 vs C 58.1\n- [Lambda Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.md): D 52.9 vs C 58.1\n- [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\n- [Modal vs Together GPU Clusters](https://www.anchorterminal.com/compare/modal-vs-together-gpu-clusters.md): B 62.7 vs C 58.1\n- [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\n- [Northflank vs Together GPU Clusters](https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters.md): C 54 vs C 58.1\n- [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\n- [Runpod vs Together GPU Clusters](https://www.anchorterminal.com/compare/runpod-vs-together-gpu-clusters.md): C 55.6 vs C 58.1\n- [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\n- [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\n- [Together GPU Clusters vs Verda](https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda.md): C 58.1 vs D 53.3\n\n## Verify this listing\n\nFor 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\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/together-gpu-clusters\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/together-gpu-clusters.svg\" alt=\"Together GPU Clusters on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![Together GPU Clusters on Anchor Terminal](https://www.anchorterminal.com/badges/together-gpu-clusters.svg)](https://www.anchorterminal.com/tools/together-gpu-clusters)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/together-gpu-clusters\"\u003eTogether GPU Clusters on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor 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.\n\n- Dark: https://www.anchorterminal.com/assets/share/together-gpu-clusters-dark.png\n- Light: https://www.anchorterminal.com/assets/share/together-gpu-clusters-light.png\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "GPU \u0026 serverless compute", "url": "https://www.anchorterminal.com/categories/gpu-compute" }, { "name": "Together GPU Clusters", "url": "" } ], "description": "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.", "facts": [ "rank #764 of 1486", "API key auth", "0 desk reviews" ], "h1": "Together GPU Clusters", "image": "https://www.anchorterminal.com/assets/og/tools-together-gpu-clusters.png", "path": "/tools/together-gpu-clusters", "published": "2026-10-01", "section": "tools", "title": "Together GPU Clusters review (2026): pricing, alternatives and grade C", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/tools/together-gpu-clusters" }, "tokens": { "markdown": 7800, "slim": 1680 }, "version": 1 }