{ "data": { "a": { "slug": "crusoe-cloud", "name": "Crusoe Cloud", "vendor": "Crusoe", "vendorUrl": "https://www.crusoe.ai", "kind": "http-api", "category": "gpu-compute", "summary": "Crusoe Cloud rents NVIDIA and AMD GPU virtual machines with managed Kubernetes and Slurm, and runs hosted model inference, dedicated deployments and LoRA fine-tuning. Resources are managed through a REST API, a CLI, a Terraform provider and a Go client.", "url": "https://www.anchorterminal.com/tools/crusoe-cloud", "markdownUrl": "https://www.anchorterminal.com/tools/crusoe-cloud.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/crusoe-cloud.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/crusoe-cloud.json", "dns": "crusoe-cloud.grade.anchorterminal.com", "repo": "https://github.com/crusoecloud/client-go", "license": "Proprietary service under the Crusoe Cloud Platform Terms of Service. The Go client and the MCP server package are MIT. The CLI ships as binaries, and no licence file was found in the Terraform provider repository", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.cloud.crusoe.ai/v1", "packages": [ { "registry": "go", "name": "github.com/crusoecloud/client-go" }, { "registry": "npm", "name": "@crusoeai/cloud-mcp" } ], "auth": "api-key", "authNotes": "Self-serve. A person signs up in the console with Google, GitHub or an email code, then creates an access key ID and secret key under Security, with an optional alias and expiry. Each request carries `X-Crusoe-Timestamp` and `Authorization: Bearer 1.0:\u003caccess_key_id\u003e:\u003csignature\u003e`, where the signature is an HMAC-SHA256 of the path, sorted query string, verb and timestamp. Keys inherit the roles of the user who made them (`org-admin`, `org-editor`, `org-reader`, `project-editor`, `project-reader`). Managed AI uses separate Intelligence API keys sent as a Bearer token. Service accounts appear in the API description and the Terraform provider 1.6.0, with no docs page found.", "pricing": "usage", "pricingNotes": "Pay as you go, billed per second for on-demand VMs. Per GPU-hour, B300 $8.96, H200 $4.29, H100 $3.90, MI300X $3.45, A100 $2.00 to $2.30 and L40S $1.50. Vera Rubin, GB300, GB200, B200, MI355X and all spot prices are contact sales. Compute needs a non-prepaid credit card. $5 of introductory credits cover Serverless Inference and Fine-Tuning without a card. Ingress and egress are free (https://www.crusoe.ai/cloud/pricing, checked 2026-11-02).", "priceSummary": "$0.04 / vCPU-hr", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the API description or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": 41, "popularity": { "githubStars": null, "npmWeekly": 7, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.crusoecloud.com/", "llmsTxt": "https://docs.crusoecloud.com/llms.txt", "openapi": "https://api.crusoecloud.com/v1/openapi.json", "capabilities": [ "compute.gpu", "compute.containers", "compute.batch", "compute.endpoints" ], "tags": [ "hosted", "usage-priced", "openapi", "llms-txt", "mcp", "cli", "terraform", "go", "status-page", "soc2", "enterprise" ], "lastRelease": "2026-10-27", "graded": true, "anchor": { "graded": true, "score": 62.4, "grade": "B", "agentReady": false, "rank": 557, "ranked": true, "rankOf": 1510, "categoryRank": 8, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 45, "maintenance": 76, "payments": 30, "reliability": 76, "schema": 79, "security": 74, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": -3, "negativeNotes": [ "2026-09-12 and 2026-10-02. Crusoe Updates marks two Serverless Inference model deprecations as Breaking, each dated the day it took effect. Z.ai GLM-5.1, Z.ai GLM-5.2, DeepSeek V3, Qwen3 235B A22B and Llama 3.3 70B \"were deprecated for Serverless Inference on September 12, 2026\", and Moonshot Kimi K2.6 on 2 October, with no earlier entry found. On 21 October DeepSeek V4.1 Flash began serving a new checkpoint in place, announced the same day. The terms promise 90 days' notice for incompatible API changes. One folded same-day term of 3 (https://docs.crusoe.ai/updates/index.html)." ], "verdict": "The v1 REST API has a published OpenAPI description, Markdown docs, HMAC-signed keys, reader roles and a 90-day audit log, with on-demand GPU prices public. No idempotency keys or control-plane rate limits were found, and serverless models were withdrawn in September and October 2026 on the day they were announced, despite 90-day notice terms.", "bestFor": "Teams that want whole GPU machines or clusters with managed Kubernetes or Slurm in the US, Iceland or Norway, under an SLA, and are content to manage lifecycles themselves.", "strengths": [ "Requests are signed with HMAC-SHA256 over the path, query, verb and timestamp, so the secret key never travels with a request.", "The API description is published for `/v1` and `/v1alpha5`, with 1,231 examples, and the docs serve `llms.txt` and a Markdown twin of each page.", "On-demand prices are public and billed per second. H100 is $3.90, H200 $4.29 and B300 $8.96 a GPU-hour, with no charge for ingress or egress.", "Organisation and project roles include read-only `org-reader` and `project-reader`, and the audit log keeps 90 days of control-plane actions readable through the API.", "The Terms of Service promise 90 days' notice before a service is discontinued or a customer-facing API changes in a backwards-incompatible way." ], "weaknesses": [ "No idempotency key or safe-retry guidance was found for create and delete calls, which return asynchronous operations to poll.", "No request rate limits were found for the infrastructure API. Numbers are published only for Serverless Inference.", "Spot prices and on-demand prices for Vera Rubin, GB300, GB200, B200 and MI355X are contact sales, and provisioning compute needs a non-prepaid credit card.", "Six Serverless Inference models were deprecated on 12 September and 2 October 2026 in entries dated the same day, with no earlier notice found.", "The Service Specific Terms let customers publish benchmark results only with Crusoe's written consent, and the Intelligence Foundry terms bar competitive analysis or benchmarking. Recorded as a fact, and it matters before any probe is run." ], "agentNotes": [ "Sign every request. Build the payload from path, sorted query string, verb and `X-Crusoe-Timestamp`, HMAC-SHA256 it with the base64url-decoded secret, and send `Authorization: Bearer 1.0:\u003caccess_key_id\u003e:\u003csignature\u003e`.", "Use `https://api.cloud.crusoe.ai/v1`. Some docs pages and the MCP server still name `api.crusoecloud.com` and `/v1alpha5`.", "Creates, updates and deletes return an operation. Poll the matching operations endpoint for `state`, and list existing resources by name before retrying a create, because no idempotency key was found.", "Managed AI uses separate Intelligence API keys and hosts, `api.inference.crusoecloud.com` for OpenAI-compatible calls and `api.intelligence.crusoecloud.com` for files and fine-tuning jobs.", "Delete a VM and its disks to stop charges. A stopped on-demand VM is not billed for compute, but its 128 GB OS disk still bills at $0.08 a GiB-month.", "Check Crusoe Updates before pinning a Serverless Inference model. Six models were withdrawn on the day of announcement, so keep a fallback model id ready." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.4 } ], "editorialScores": { "ergonomics": 45, "maintenance": 76, "payments": 30, "reliability": 76, "schema": 79, "security": 74, "transparency": 64 }, "provenanceScore": 90, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-11-02", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "brew install crusoecloud/cli/crusoe", "http": "curl https://api.cloud.crusoe.ai/v1/capacities -H \"X-Crusoe-Timestamp: \u003cRFC3339 timestamp\u003e\" -H \"Authorization: Bearer \u003cversion:access_key_id:base64_encoded_signature\u003e\"", "claudeCode": "claude mcp add crusoe-cloud -- npx -y @crusoeai/cloud-mcp", "config": { "mcpServers": { "crusoe-cloud": { "args": [ "-y", "@crusoeai/cloud-mcp" ], "command": "npx" } } } }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/crusoe-cloud" }, "area": "models", "unitPrices": [ { "item": "NVIDIA B300 288 GB HGX, on demand", "unit": "gpu-hour", "usd": 8.96, "note": "Billed per second while running. Spot is contact sales" }, { "item": "NVIDIA H100 80 GB HGX, on demand", "unit": "gpu-hour", "usd": 3.9, "note": "Billed per second while running. Spot is contact sales" }, { "item": "NVIDIA H200 141 GB HGX, on demand", "unit": "gpu-hour", "usd": 4.29 }, { "item": "NVIDIA A100 80 GB SXM, on demand", "unit": "gpu-hour", "usd": 2.3 }, { "item": "NVIDIA A100 80 GB PCIe, on demand", "unit": "gpu-hour", "usd": 2 }, { "item": "NVIDIA L40S 48 GB, on demand", "unit": "gpu-hour", "usd": 1.5 }, { "item": "AMD MI300X 192 GB, on demand", "unit": "gpu-hour", "usd": 3.45 }, { "item": "NVIDIA H100, Self-Serve Deployment", "unit": "gpu-hour", "usd": 5.5, "note": "Dedicated inference endpoint, billed until deleted. H200 $6.00, B200 $9.65, MI355X $7.40" }, { "item": "General-purpose CPU instance", "unit": "vcpu-hour", "usd": 0.04, "note": "Storage-optimised $0.09" }, { "item": "Persistent disk", "unit": "gb-month", "usd": 0.08, "note": "Per GiB. Shared disks $0.07, Object Storage $0.06" } ], "provenance": { "legalEntity": "Crusoe Technologies LLC", "domain": "crusoe.ai", "domainRegistered": "2019-01-28", "endpointOnVendorDomain": true, "terms": "https://legal.crusoe.ai/#terms-of-service", "privacy": "https://legal.crusoe.ai/#cloud-privacy-policy", "statusPage": "https://status.crusoecloud.com", "changelog": "https://docs.crusoecloud.com/updates", "securityTxt": "valid", "checked": "2026-10-09", "notes": [ "The Crusoe Cloud Platform Terms of Service, version 1.10, effective 10 August 2026, are a contract with Crusoe Technologies LLC and its affiliates. Ten earlier versions are kept on the same page.", "legal.crusoe.ai is one page that holds every legal document and its earlier versions, reached by anchor. The terms and privacy links point at the anchors for the platform terms and the Crusoe Cloud Platform Privacy Notice, not at the separate website terms and website privacy notice.", "The Crusoe Cloud Platform Privacy Notice, version 1.3, effective 12 March 2026, covers Service Data only. Customer Data falls under the Data Processing and Security Terms, version 1.3, effective 14 July 2026.", "The API reference gives `https://api.cloud.crusoe.ai/v1`, under the vendor domain. Other docs pages and the MCP server name `api.crusoecloud.com`, and Managed AI answers at `api.inference.crusoecloud.com` and `api.intelligence.crusoecloud.com`. crusoecloud.com was registered on 14 April 2020 per RDAP and redirects to www.crusoe.ai.", "security.txt at www.crusoe.ai gives security@crusoe.ai and expires on 1 March 2027. It has no Policy field.", "RDAP for crusoe.ai gives a registration date of 2019-01-28. The website footer reads Crusoe, Inc, and the licence files in the CLI and Go client repositories name Crusoe Energy Systems LLC." ], "score": 90 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/crusoe-cloud.json", "live": { "slug": "crusoe-cloud", "probe": { "target": "https://api.cloud.crusoe.ai/v1", "method": "get", "lastAt": "2026-11-07T19:22:02.122545866Z", "lastOk": true, "lastStatus": 200, "lastMs": 278, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 177, "p95ms24h": 256, "samples24h": 238, "samples30d": 7215, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.crusoecloud.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:21:40.70822793Z" }, "versions": [ { "registry": "npm", "name": "@crusoeai/cloud-mcp", "version": "0.1.6", "seenAt": "2026-11-06T23:18:42.185227268Z" } ], "githubStars": 4, "npmWeekly": 27, "securityTxt": { "url": "https://crusoe.ai/.well-known/security.txt", "state": "valid", "expires": "2027-03-01T21:00:00.000Z", "checkedAt": "2026-11-07T15:59:35.513641331Z" }, "llmsTxt": { "url": "https://docs.crusoecloud.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:13.809877657Z" }, "domain": { "domain": "crusoe.ai", "registered": "2019-01-28", "source": "https://rdap.identitydigital.services/rdap/domain/crusoe.ai", "checkedAt": "2026-11-01T14:18:14.102667117Z" }, "pages": [ { "url": "https://docs.crusoecloud.com/updates", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:05:59.977059308Z", "changedAt": "2026-11-07T14:05:59.977059308Z", "fingerprint": "37c27a1a3149" }, { "url": "https://docs.crusoe.ai/updates/index.html", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:05:59.878902129Z", "changedAt": "2026-11-07T14:05:59.878902129Z", "fingerprint": "37c27a1a3149" }, { "url": "https://www.crusoe.ai/cloud/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:27:38.401408348Z", "changedAt": "2026-11-07T14:27:38.401408348Z", "fingerprint": "a91c21f49d79" }, { "url": "https://legal.crusoe.ai/", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:12:51.725212267Z", "changedAt": "2026-11-06T13:34:52.347341362Z", "fingerprint": "963ee7400752" } ], "github": { "repo": "crusoecloud/client-go", "checkedAt": "2026-11-02T08:42:22.247028438Z", "stars": 4, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-30T21:19:26Z", "openIssues": 0, "openPRs": 0, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0 }, "updatedAt": "2026-11-07T19:22:02.122545866Z" } }, "answer": "Crusoe Cloud scores 62.4 (B) on agent readiness against Together GPU Clusters's 58.1 (C), and leads in 5 of 7 scored categories. Together GPU Clusters leads on schema \u0026 documentation and agent ergonomics.", "b": { "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": 768, "ranked": true, "rankOf": 1510, "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" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "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 } }, "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" ], "area": "models", "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 }, "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-07T19:22:40.660879578Z", "lastOk": true, "lastStatus": 401, "lastMs": 263, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 493, "p95ms24h": 857, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "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-07T19:22:40.660879578Z" } }, "edges": [ { "by": 38, "category": "reliability", "leads": "crusoe-cloud", "name": "Reliability", "reasons": { "a": "Graded as a hosted service on the REST API. Statuspage at status.crusoecloud.com with components per region and service (20). From 4 August to 2 November 2026 the history shows five incidents, each limited to one region or a subset of resources, so all read as partial. They were VM and Kubernetes cluster creation in us-east2 for about 7.5 hours (2 September, minor), network errors in us-east1 (3 September, no stated impact), a subset of VMs showing as UNSPECIFIED in us-east2 (9 September, no stated impact), Shared Storage, Object Storage and the container registry unreachable in eu-norway1 for about 3 hours 54 minutes (29 September, labelled critical) and a facility issue that powered off a subset of compute instances in us-east2-a from 15 to 18 October (labelled critical). Scheduled maintenance isn't counted. Minor incidents only (20). Rate limits carry numbers only for Serverless Inference (500,000 tokens and 30 requests a minute per model without a payment method, 2,000,000 and 600 with one); none were found for the infrastructure API, whose MCP server throttles itself to 60 requests a minute (8 of 15). Serverless Inference documents 429 and 503 with exponential backoff and `x-ratelimit-*` headers; no Retry-After, no idempotency keys and no retry guidance for infrastructure writes were found (8 of 15). SLA version 8.0 (21 July 2026) of 99.5 per cent a month per GPU virtual machine and per persistent or shared disk, with credits of 10, 25 or 100 per cent (10). The v1 API is labelled Latest and the services graded are generally available; the MCP server is in preview (10).", "b": "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." }, "scores": { "a": 76, "b": 38 } }, { "by": 13, "category": "schema", "leads": "together-gpu-clusters", "name": "Schema \u0026 documentation", "reasons": { "a": "A Swagger 2.0 description for `/v1` and `/v1alpha5`, linked from the reference page and kept in `crusoecloud/client-go`, and an OpenAPI description for the Intelligence Foundry API (25). `llms.txt` and a Markdown twin of each docs page (10). Every one of the 257 operations in the repository copy has a one-line summary, 74 have a longer description, and fields are described; few say when not to call (11). 64 enums and 208 required lists, though `limit` is typed as a string and instance types and locations are plain strings; the file declares no security scheme (10). 1,231 examples with request and response samples, and 400, 401, 403, 404 and 500 responses with a `code` and `message` body; no error catalogue and 429 appears on one operation (10). Versioned paths, dated Crusoe Updates entries with RSS and Atom feeds, and tagged Go client releases; the updates do not list API changes field by field (13).", "b": "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." }, "scores": { "a": 79, "b": 92 } }, { "by": 12, "category": "transparency", "leads": "crusoe-cloud", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under Terms of Service version 1.10, effective 10 August 2026, with ten earlier versions kept on the legal page; the Go client and MCP package are MIT (15). The Privacy Notice (version 1.3, 12 March 2026) covers Service Data and the Data Processing and Security Terms (version 1.3, 14 July 2026) cover Customer Data, with deletion on instruction and at the end of the term, and the Intelligence Foundry terms say inputs, outputs and training data are not used to train models without opt-in consent; no retention periods are given in numbers (22). The terms promise 90 days' notice before discontinuing a service or changing a customer-facing API incompatibly, and a deprecation page gives dates such as 8 November 2026 for old CSI drivers, announced 15 September; model deprecations are logged on the day they take effect, six models on 12 September and 2 October 2026 (17). Seven data centre zones are published; the data processing terms point to a sub-processor list that was not found in the pages read (10).", "b": "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." }, "scores": { "a": 77, "b": 65 } }, { "by": 10, "category": "ergonomics", "leads": "together-gpu-clusters", "name": "Agent ergonomics", "reasons": { "a": "Lists take `limit` or `page_size` on 16 of about 104 list calls, and VM lists filter by id, name, type, location and state; no field selection (12 of 25). Token pagination with next and previous tokens and a `sort` parameter where present; most lists return everything (12). Errors are an HTTP status with `code` and `message`, and long-running calls return an operation with `state` and `result` to poll; no documented list of error codes (10). No idempotency key or safe-retry guidance found; the preview MCP server has read tools only, and its annotations were not read (4). VM create needs a name, type, location and SSH key and installs a monitoring agent by default; the Go client is the only official SDK found, beside a CLI and a Terraform provider, and other languages must code the request signature (7).", "b": "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." }, "scores": { "a": 45, "b": 55 } }, { "by": 10, "category": "payments", "leads": "crusoe-cloud", "name": "Payments \u0026 pricing", "reasons": { "a": "No machine payment protocol (0). Per-GPU-hour, per-vCPU-hour, per-GiB and per-token prices published without a login, though spot prices and on-demand prices for GB200, B200 and MI355X are contact sales (20). $5 of introductory credits cover Serverless Inference and Serverless Fine-Tuning without a payment method; GPU machines, the product graded here, need a non-prepaid credit card (10 of 20). Signup is a browser flow with Google, GitHub or an emailed code, and the first key is made in the console (0).", "b": "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." }, "scores": { "a": 30, "b": 20 } }, { "by": 6, "category": "security", "leads": "crusoe-cloud", "name": "Security \u0026 auth", "reasons": { "a": "Access key and secret key with optional expiry, deletable in the console or through `/users/tokens`. Requests are signed with HMAC-SHA256 and a timestamp, so no secret is sent and none travels in a URL. Keys inherit their creator's roles and cannot be narrowed further; service accounts with their own credentials appear in the API description and the Terraform provider 1.6.0 (24). `org-reader` and `project-reader` roles give read-only access and the MCP server exposes no write tools; no confirmation step for destructive API calls (14). Returns infrastructure metadata, and the MCP docs warn that it is sent to the assistant and that an agent with a shell can still run the CLI (10). Audit log of 90 days of control-plane actions with actor, IP, surface and result, readable through the API by admins; read events are not logged (13). security.txt valid until 1 March 2027 with no Policy field, ISO 27001, ISO 42001 and SOC 2 Type I and II claimed on the cloud page, customer-managed encryption keys; no bug bounty found, the trust centre was unreadable, and the apt install line sets `[trusted=yes]` (13).", "b": "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." }, "scores": { "a": 74, "b": 68 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Crusoe", "b": "Together AI", "name": "Vendor" }, { "a": "https://api.cloud.crusoe.ai/v1", "b": "https://api.together.ai/v1/compute/clusters", "name": "Hosted endpoint" }, { "a": "HTTP, stdio", "b": "", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Crusoe Cloud Platform Terms of Service. The Go client and the MCP server package are MIT. The CLI ships as binaries, and no licence file was found in the Terraform provider repository", "b": "Proprietary service under Together's terms of service. The Python SDK and CLI are Apache-2.0 and the OpenAPI document is MIT", "name": "Licence" }, { "a": "41", "b": "none", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-27", "b": "2026-10-22", "name": "Last release" }, { "a": "couldn't be read", "b": "no date given", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "7 npm/wk", "b": "none", "name": "Popularity" }, { "a": "3.3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Crusoe Cloud scores 62.4 (B) on agent readiness against Together GPU Clusters's 58.1 (C), and leads in 5 of 7 scored categories. Together GPU Clusters leads on schema \u0026 documentation and agent ergonomics.", "question": "Which is better for AI agents, Crusoe Cloud or Together GPU Clusters?" }, { "answer": "Both need an API key.", "question": "Do Crusoe Cloud and Together GPU Clusters need an API key?" }, { "answer": "Yes. Crusoe Cloud has a hosted endpoint at https://api.cloud.crusoe.ai/v1 and Together GPU Clusters at https://api.together.ai/v1/compute/clusters.", "question": "Can an agent call Crusoe Cloud and Together GPU Clusters without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 76 against 38", "Security \u0026 auth, 74 against 68", "Payments \u0026 pricing, 30 against 20", "Transparency \u0026 trust, 77 against 65" ], "also": [ "Runs on your own machine" ], "goodFor": "Teams that want whole GPU machines or clusters with managed Kubernetes or Slurm in the US, Iceland or Norway, under an SLA, and are content to manage lifecycles themselves.", "slug": "crusoe-cloud", "watchFor": "No idempotency key or safe-retry guidance was found for create and delete calls, which return asynchronous operations to poll." }, { "aheadOn": [ "Schema \u0026 documentation, 92 against 79", "Agent ergonomics, 55 against 45" ], "also": [ "No incidents deducted, where Crusoe Cloud loses 3 points for them" ], "goodFor": "Training, fine-tuning and batch jobs that need several 8-GPU nodes with InfiniBand, run by a pipeline that creates and deletes clusters.", "slug": "together-gpu-clusters", "watchFor": "Provisioning takes 10 minutes to an hour, and a cluster can't be paused or scaled to zero" } ], "history": { "crusoe-cloud": [ { "causes": [ "correction", "event" ], "date": "2026-11-02", "delta": -1, "from": 63.4, "fromGrade": "B", "to": 62.4, "toGrade": "B" } ], "together-gpu-clusters": null }, "job": { "capability": "compute.gpu", "name": "GPU compute" }, "others": [ { "json": "https://www.anchorterminal.com/compare/baseten-vs-crusoe-cloud.json", "title": "Baseten vs Crusoe Cloud", "url": "https://www.anchorterminal.com/compare/baseten-vs-crusoe-cloud" }, { "json": "https://www.anchorterminal.com/compare/baseten-vs-together-gpu-clusters.json", "title": "Baseten vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/baseten-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/beam-vs-crusoe-cloud.json", "title": "Beam vs Crusoe Cloud", "url": "https://www.anchorterminal.com/compare/beam-vs-crusoe-cloud" }, { "json": "https://www.anchorterminal.com/compare/beam-vs-together-gpu-clusters.json", "title": "Beam vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/beam-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-crusoe-cloud.json", "title": "Cerebrium vs Crusoe Cloud", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-crusoe-cloud" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-together-gpu-clusters.json", "title": "Cerebrium vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-crusoe-cloud.json", "title": "Cloud Run GPUs vs Crusoe Cloud", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-crusoe-cloud" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-together-gpu-clusters.json", "title": "Cloud Run GPUs vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/coreweave-vs-crusoe-cloud.json", "title": "CoreWeave vs Crusoe Cloud", "url": "https://www.anchorterminal.com/compare/coreweave-vs-crusoe-cloud" }, { "json": "https://www.anchorterminal.com/compare/coreweave-vs-together-gpu-clusters.json", "title": "CoreWeave vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/coreweave-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-gpusmarket.json", "title": "Crusoe Cloud vs GPUsMarket", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-gpusmarket" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-hugging-face-inference-endpoints.json", "title": "Crusoe Cloud vs Hugging Face Inference Endpoints", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-hugging-face-inference-endpoints" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-hyperbolic.json", "title": "Crusoe Cloud vs Hyperbolic", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-hyperbolic" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-koyeb.json", "title": "Crusoe Cloud vs Koyeb", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-koyeb" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-lambda.json", "title": "Crusoe Cloud vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-lambda" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute.json", "title": "Crusoe Cloud vs Massed Compute", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-modal.json", "title": "Crusoe Cloud vs Modal", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-modal" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-nebius-ai-cloud.json", "title": "Crusoe Cloud vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-nebius-ai-cloud" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-northflank.json", "title": "Crusoe Cloud vs Northflank", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-northflank" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-replicate-deploy.json", "title": "Crusoe Cloud vs Replicate Deployments", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-replicate-deploy" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-runpod.json", "title": "Crusoe Cloud vs Runpod", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-runpod" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-thunder-compute.json", "title": "Crusoe Cloud vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-vast-ai.json", "title": "Crusoe Cloud vs Vast.ai", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-verda.json", "title": "Crusoe Cloud vs Verda", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.json", "title": "GPUsMarket vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-together-gpu-clusters.json", "title": "Hugging Face Inference Endpoints vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters.json", "title": "Hyperbolic vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters.json", "title": "Koyeb vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.json", "title": "Lambda Cloud vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.json", "title": "Massed Compute vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/modal-vs-together-gpu-clusters.json", "title": "Modal vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/modal-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters.json", "title": "Nebius AI Cloud vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters.json", "title": "Northflank vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/replicate-deploy-vs-together-gpu-clusters.json", "title": "Replicate Deployments vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/replicate-deploy-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/runpod-vs-together-gpu-clusters.json", "title": "Runpod vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/runpod-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters.json", "title": "Thunder Compute vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/together-gpu-clusters-vs-vast-ai.json", "title": "Together GPU Clusters vs Vast.ai", "url": "https://www.anchorterminal.com/compare/together-gpu-clusters-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda.json", "title": "Together GPU Clusters vs Verda", "url": "https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda" } ], "panel": null, "scores": [ { "by": 38, "crusoe-cloud": 76, "edge": "crusoe-cloud", "key": "reliability", "name": "Reliability", "together-gpu-clusters": 38, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 13, "crusoe-cloud": 79, "edge": "together-gpu-clusters", "key": "schema", "name": "Schema \u0026 documentation", "together-gpu-clusters": 92, "weight": 13 }, { "by": 10, "crusoe-cloud": 45, "edge": "together-gpu-clusters", "key": "ergonomics", "name": "Agent ergonomics", "together-gpu-clusters": 55, "weight": 13 }, { "by": 6, "crusoe-cloud": 74, "edge": "crusoe-cloud", "key": "security", "name": "Security \u0026 auth", "together-gpu-clusters": 68, "weight": 14 }, { "by": 10, "crusoe-cloud": 30, "edge": "crusoe-cloud", "key": "payments", "name": "Payments \u0026 pricing", "together-gpu-clusters": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 1, "crusoe-cloud": 76, "edge": "crusoe-cloud", "key": "maintenance", "name": "Maintenance \u0026 community", "together-gpu-clusters": 75, "weight": 7 }, { "by": 12, "crusoe-cloud": 77, "edge": "crusoe-cloud", "key": "transparency", "name": "Transparency \u0026 trust", "together-gpu-clusters": 65, "weight": 7 } ], "summary": "Crusoe Cloud scores 62.4 (B) on agent readiness against Together GPU Clusters's 58.1 (C), and leads in 5 of 7 scored categories. Together GPU Clusters leads on schema \u0026 documentation and agent ergonomics. Both do gpu compute.", "tasks": null, "tutorials": [], "verdicts": { "crusoe-cloud": "The v1 REST API has a published OpenAPI description, Markdown docs, HMAC-signed keys, reader roles and a 90-day audit log, with on-demand GPU prices public. No idempotency keys or control-plane rate limits were found, and serverless models were withdrawn in September and October 2026 on the day they were announced, despite 90-day notice terms.", "together-gpu-clusters": "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters", "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters.min.md" }, "markdown": "Crusoe Cloud scores 62.4 (B) on agent readiness against Together GPU Clusters's 58.1 (C), and leads in 5 of 7 scored categories. Together GPU Clusters leads on schema \u0026 documentation and agent ergonomics. Both do gpu compute.\n\n- Crusoe Cloud: grade B, 62.4/100, rank #557 of 1510. Markdown https://www.anchorterminal.com/tools/crusoe-cloud.md · JSON https://www.anchorterminal.com/api/v1/tools/crusoe-cloud.json\n- Together GPU Clusters: grade C, 58.1/100, rank #768 of 1510. Markdown https://www.anchorterminal.com/tools/together-gpu-clusters.md · JSON https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json\n- 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## Which one, for what\n\n### Crusoe Cloud (B)\n\nGood for: Teams that want whole GPU machines or clusters with managed Kubernetes or Slurm in the US, Iceland or Norway, under an SLA, and are content to manage lifecycles themselves.\n\nAhead on:\n- Reliability, 76 against 38\n- Security \u0026 auth, 74 against 68\n- Payments \u0026 pricing, 30 against 20\n- Transparency \u0026 trust, 77 against 65\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: No idempotency key or safe-retry guidance was found for create and delete calls, which return asynchronous operations to poll.\n\n### Together GPU Clusters (C)\n\nGood for: Training, fine-tuning and batch jobs that need several 8-GPU nodes with InfiniBand, run by a pipeline that creates and deletes clusters.\n\nAhead on:\n- Schema \u0026 documentation, 92 against 79\n- Agent ergonomics, 55 against 45\n\nAlso in its favour:\n- No incidents deducted, where Crusoe Cloud loses 3 points for them\n\nWatch for: Provisioning takes 10 minutes to an hour, and a cluster can't be paused or scaled to zero\n\n\n## Why the edge\n\n### Reliability: Crusoe Cloud +38\n\n- Crusoe Cloud (76): Graded as a hosted service on the REST API. Statuspage at status.crusoecloud.com with components per region and service (20). From 4 August to 2 November 2026 the history shows five incidents, each limited to one region or a subset of resources, so all read as partial. They were VM and Kubernetes cluster creation in us-east2 for about 7.5 hours (2 September, minor), network errors in us-east1 (3 September, no stated impact), a subset of VMs showing as UNSPECIFIED in us-east2 (9 September, no stated impact), Shared Storage, Object Storage and the container registry unreachable in eu-norway1 for about 3 hours 54 minutes (29 September, labelled critical) and a facility issue that powered off a subset of compute instances in us-east2-a from 15 to 18 October (labelled critical). Scheduled maintenance isn't counted. Minor incidents only (20). Rate limits carry numbers only for Serverless Inference (500,000 tokens and 30 requests a minute per model without a payment method, 2,000,000 and 600 with one); none were found for the infrastructure API, whose MCP server throttles itself to 60 requests a minute (8 of 15). Serverless Inference documents 429 and 503 with exponential backoff and `x-ratelimit-*` headers; no Retry-After, no idempotency keys and no retry guidance for infrastructure writes were found (8 of 15). SLA version 8.0 (21 July 2026) of 99.5 per cent a month per GPU virtual machine and per persistent or shared disk, with credits of 10, 25 or 100 per cent (10). The v1 API is labelled Latest and the services graded are generally available; the MCP server is in preview (10).\n- Together GPU Clusters (38): Read with the hosted lines. status.together.ai lists the website, the playground and serverless models with no component for GPU clusters, and a vendor page with no component for the product takes 15 in this run, as for Together's Code Sandbox and fine-tuning listings (15). No incident history for clusters can be read (5). No rate limits for the clusters API found (0). Together's docs give 429 and 503 backoff guidance for its APIs, per the inference listing's 1 November check, and the CLI has `--non-interactive` and `--json` for scripted retries, but creation has no idempotency key (8). No SLA for clusters found; the published 99% commitment covers provisioned inference throughput only (0). Generally available since 9 September 2025 and out of the CLI's beta paths since 22 October 2026, with preemptible nodes in preview (10). 15+5+0+8+0+10 = 38.\n\n### Schema \u0026 documentation: Together GPU Clusters +13\n\n- Crusoe Cloud (79): A Swagger 2.0 description for `/v1` and `/v1alpha5`, linked from the reference page and kept in `crusoecloud/client-go`, and an OpenAPI description for the Intelligence Foundry API (25). `llms.txt` and a Markdown twin of each docs page (10). Every one of the 257 operations in the repository copy has a one-line summary, 74 have a longer description, and fields are described; few say when not to call (11). 64 enums and 208 required lists, though `limit` is typed as a string and instance types and locations are plain strings; the file declares no security scheme (10). 1,231 examples with request and response samples, and 400, 401, 403, 404 and 500 responses with a `code` and `message` body; no error catalogue and 429 appears on one operation (10). Versioned paths, dated Crusoe Updates entries with RSS and Atom feeds, and tagged Go client releases; the updates do not list API changes field by field (13).\n- Together GPU Clusters (92): Public OpenAPI 3.1 for /v1/compute/clusters and shared volumes, MIT, embedded in every reference page (25). llms.txt and a Markdown twin of every page (10). The docs say when to choose Kubernetes or Slurm and each capacity type, and the management page carries instructions for agents on reporting live availability and prices (18). Enums for cluster type, billing type, GPU type and status, required fields marked (13). CLI, Python, TypeScript and console steps on each task, with 402 and 403 cases documented, though no error catalogue for the clusters API (11). Versioned SDKs and a dated changelog with cluster entries (15). 25+10+18+13+11+15 = 92.\n\n### Transparency \u0026 trust: Crusoe Cloud +12\n\n- Crusoe Cloud (77): Closed service under Terms of Service version 1.10, effective 10 August 2026, with ten earlier versions kept on the legal page; the Go client and MCP package are MIT (15). The Privacy Notice (version 1.3, 12 March 2026) covers Service Data and the Data Processing and Security Terms (version 1.3, 14 July 2026) cover Customer Data, with deletion on instruction and at the end of the term, and the Intelligence Foundry terms say inputs, outputs and training data are not used to train models without opt-in consent; no retention periods are given in numbers (22). The terms promise 90 days' notice before discontinuing a service or changing a customer-facing API incompatibly, and a deprecation page gives dates such as 8 November 2026 for old CSI drivers, announced 15 September; model deprecations are logged on the day they take effect, six models on 12 September and 2 October 2026 (17). Seven data centre zones are published; the data processing terms point to a sub-processor list that was not found in the pages read (10).\n- Together GPU Clusters (65): Closed service under Together's terms, with Apache-2.0 SDKs, which don't raise the line for a closed API (15). The privacy policy's data table covers GPU clusters, per the 4 November Code Sandbox check, and the billing page states when volumes are deleted after credit runs out, with no retention period for data on deleted clusters (15). The 3.0 breaking change came with a migration guide on the day, and reservations carry dated end-of-term emails, with no notice period for API changes found (8). Regions are listed through the API and US regions appear in examples; subprocessors and data locations for clusters were not established (8). 15+15+8+8 = 46.\n\n### Agent ergonomics: Together GPU Clusters +10\n\n- Crusoe Cloud (45): Lists take `limit` or `page_size` on 16 of about 104 list calls, and VM lists filter by id, name, type, location and state; no field selection (12 of 25). Token pagination with next and previous tokens and a `sort` parameter where present; most lists return everything (12). Errors are an HTTP status with `code` and `message`, and long-running calls return an operation with `state` and `result` to poll; no documented list of error codes (10). No idempotency key or safe-retry guidance found; the preview MCP server has read tools only, and its annotations were not read (4). VM create needs a name, type, location and SSH key and installs a monitoring agent by default; the Go client is the only official SDK found, beside a CLI and a Terraform provider, and other languages must code the request signature (7).\n- Together GPU Clusters (55): Cluster objects are compact, and `--json` gives machine-readable output, but list calls take no field selection (15). No pagination or filters on the clusters list (8). 402 and 403 with readable messages such as \"Insufficient credits for cluster creation\", and troubleshooting for common failures (12). Status polling until Ready is documented and deletes run non-interactively, but there is no idempotency key on creation and a duplicate create bills a second cluster (8). Official Python and TypeScript SDKs and a CLI, though a create takes GPU type, region, driver and CUDA versions, cluster type and billing type (12). 15+8+12+8+12 = 55.\n\n### Payments \u0026 pricing: Crusoe Cloud +10\n\n- Crusoe Cloud (30): No machine payment protocol (0). Per-GPU-hour, per-vCPU-hour, per-GiB and per-token prices published without a login, though spot prices and on-demand prices for GB200, B200 and MI355X are contact sales (20). $5 of introductory credits cover Serverless Inference and Serverless Fine-Tuning without a payment method; GPU machines, the product graded here, need a non-prepaid credit card (10 of 20). Signup is a browser flow with Google, GitHub or an emailed code, and the first key is made in the console (0).\n- Together GPU Clusters (20): 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\n### Security \u0026 auth: Crusoe Cloud +6\n\n- Crusoe Cloud (74): Access key and secret key with optional expiry, deletable in the console or through `/users/tokens`. Requests are signed with HMAC-SHA256 and a timestamp, so no secret is sent and none travels in a URL. Keys inherit their creator's roles and cannot be narrowed further; service accounts with their own credentials appear in the API description and the Terraform provider 1.6.0 (24). `org-reader` and `project-reader` roles give read-only access and the MCP server exposes no write tools; no confirmation step for destructive API calls (14). Returns infrastructure metadata, and the MCP docs warn that it is sent to the assistant and that an agent with a shell can still run the CLI (10). Audit log of 90 days of control-plane actions with actor, IP, surface and result, readable through the API by admins; read events are not logged (13). security.txt valid until 1 March 2027 with no Policy field, ISO 27001, ISO 42001 and SOC 2 Type I and II claimed on the cloud page, customer-managed encryption keys; no bug bounty found, the trust centre was unreadable, and the apt install line sets `[trusted=yes]` (13).\n- Together GPU Clusters (68): Project-scoped API keys, revocable with optional expiry, read as Together's other listings read the same key model (30). Admin and editor roles with no read-only role. Only admins get the admin kubeconfig, which has cluster-admin rights, and OIDC lets editors use kubectl under RBAC. Deletes run without confirmation when `--non-interactive` is passed (8). The API returns cluster state, not third-party content (10). Invoices itemise reserved, on-demand and storage charges, and no audit log for cluster operations was found (5). security.txt with a HackerOne route, per the 1 November check of the inference listing (15). 30+8+10+5+15 = 68.\n\n## Score by category\n\n| Category | Weight | Crusoe Cloud | Together GPU Clusters | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 76 | 38 | Crusoe Cloud +38 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 79 | 92 | Together GPU Clusters +13 |\n| Agent ergonomics | 13% (16.2 this run) | 45 | 55 | Together GPU Clusters +10 |\n| Security \u0026 auth | 14% (17.5 this run) | 74 | 68 | Crusoe Cloud +6 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 20 | Crusoe Cloud +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 76 | 75 | Crusoe Cloud +1 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 65 | Crusoe Cloud +12 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **62.4 · B** | **58.1 · C** | |\n\n## Facts side by side\n\n| Fact | Crusoe Cloud | Together GPU Clusters |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Crusoe | Together AI |\n| Hosted endpoint | `https://api.cloud.crusoe.ai/v1` | `https://api.together.ai/v1/compute/clusters` |\n| Transports | HTTP, stdio | |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary service under the Crusoe Cloud Platform Terms of Service. The Go client and the MCP server package are MIT. The CLI ships as binaries, and no licence file was found in the Terraform provider repository | Proprietary service under Together's terms of service. The Python SDK and CLI are Apache-2.0 and the OpenAPI document is MIT |\n| Tools exposed | 41 | none |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-27 | 2026-10-22 |\n| Terms last updated | couldn't be read | no date given |\n| Privacy policy last updated | couldn't be read | no date given |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | yes |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n| Popularity | 7 npm/wk | none |\n| Agent reviews | 3.3/5 (4) | none |\n\n## How the scores have moved\n\n### Crusoe Cloud\n\n- -1.0 on 2 November 2026: correction, negative event\n\n### Together GPU Clusters\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Crusoe Cloud.** The v1 REST API has a published OpenAPI description, Markdown docs, HMAC-signed keys, reader roles and a 90-day audit log, with on-demand GPU prices public. No idempotency keys or control-plane rate limits were found, and serverless models were withdrawn in September and October 2026 on the day they were announced, despite 90-day notice terms.\n\n**Together GPU Clusters.** 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.\n\n## Before you call either\n\n### Crusoe Cloud\n\n1. Sign every request. Build the payload from path, sorted query string, verb and `X-Crusoe-Timestamp`, HMAC-SHA256 it with the base64url-decoded secret, and send `Authorization: Bearer 1.0:\u003caccess_key_id\u003e:\u003csignature\u003e`.\n2. Use `https://api.cloud.crusoe.ai/v1`. Some docs pages and the MCP server still name `api.crusoecloud.com` and `/v1alpha5`.\n3. Creates, updates and deletes return an operation. Poll the matching operations endpoint for `state`, and list existing resources by name before retrying a create, because no idempotency key was found.\n4. Managed AI uses separate Intelligence API keys and hosts, `api.inference.crusoecloud.com` for OpenAI-compatible calls and `api.intelligence.crusoecloud.com` for files and fine-tuning jobs.\n5. Delete a VM and its disks to stop charges. A stopped on-demand VM is not billed for compute, but its 128 GB OS disk still bills at $0.08 a GiB-month.\n6. Check Crusoe Updates before pinning a Serverless Inference model. Six models were withdrawn on the day of announcement, so keep a fallback model id ready.\n\n### Together GPU Clusters\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## Questions\n\n### Which is better for AI agents, Crusoe Cloud or Together GPU Clusters?\n\nCrusoe Cloud scores 62.4 (B) on agent readiness against Together GPU Clusters's 58.1 (C), and leads in 5 of 7 scored categories. Together GPU Clusters leads on schema \u0026 documentation and agent ergonomics.\n\n### Do Crusoe Cloud and Together GPU Clusters need an API key?\n\nBoth need an API key.\n\n### Can an agent call Crusoe Cloud and Together GPU Clusters without installing anything?\n\nYes. Crusoe Cloud has a hosted endpoint at https://api.cloud.crusoe.ai/v1 and Together GPU Clusters at https://api.together.ai/v1/compute/clusters.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters.json, and with the fewest tokens: https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"crusoe-cloud\", \"b\": \"together-gpu-clusters\"}`. From a terminal: `anchor compare crusoe-cloud together-gpu-clusters`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/crusoe-cloud.json and https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json\n\n## Other comparisons with Crusoe Cloud or Together GPU Clusters\n\n- [Baseten vs Crusoe Cloud](https://www.anchorterminal.com/compare/baseten-vs-crusoe-cloud.md)\n- [Baseten vs Together GPU Clusters](https://www.anchorterminal.com/compare/baseten-vs-together-gpu-clusters.md)\n- [Beam vs Crusoe Cloud](https://www.anchorterminal.com/compare/beam-vs-crusoe-cloud.md)\n- [Beam vs Together GPU Clusters](https://www.anchorterminal.com/compare/beam-vs-together-gpu-clusters.md)\n- [Cerebrium vs Crusoe Cloud](https://www.anchorterminal.com/compare/cerebrium-vs-crusoe-cloud.md)\n- [Cerebrium vs Together GPU Clusters](https://www.anchorterminal.com/compare/cerebrium-vs-together-gpu-clusters.md)\n- [Cloud Run GPUs vs Crusoe Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-crusoe-cloud.md)\n- [Cloud Run GPUs vs Together GPU Clusters](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-together-gpu-clusters.md)\n- [CoreWeave vs Crusoe Cloud](https://www.anchorterminal.com/compare/coreweave-vs-crusoe-cloud.md)\n- [CoreWeave vs Together GPU Clusters](https://www.anchorterminal.com/compare/coreweave-vs-together-gpu-clusters.md)\n- [Crusoe Cloud vs GPUsMarket](https://www.anchorterminal.com/compare/crusoe-cloud-vs-gpusmarket.md)\n- [Crusoe Cloud vs Hugging Face Inference Endpoints](https://www.anchorterminal.com/compare/crusoe-cloud-vs-hugging-face-inference-endpoints.md)\n- [Crusoe Cloud vs Hyperbolic](https://www.anchorterminal.com/compare/crusoe-cloud-vs-hyperbolic.md)\n- [Crusoe Cloud vs Koyeb](https://www.anchorterminal.com/compare/crusoe-cloud-vs-koyeb.md)\n- [Crusoe Cloud vs Lambda Cloud](https://www.anchorterminal.com/compare/crusoe-cloud-vs-lambda.md)\n- [Crusoe Cloud vs Massed Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute.md)\n- [Crusoe Cloud vs Modal](https://www.anchorterminal.com/compare/crusoe-cloud-vs-modal.md)\n- [Crusoe Cloud vs Nebius AI Cloud](https://www.anchorterminal.com/compare/crusoe-cloud-vs-nebius-ai-cloud.md)\n- [Crusoe Cloud vs Northflank](https://www.anchorterminal.com/compare/crusoe-cloud-vs-northflank.md)\n- [Crusoe Cloud vs Replicate Deployments](https://www.anchorterminal.com/compare/crusoe-cloud-vs-replicate-deploy.md)\n- [Crusoe Cloud vs Runpod](https://www.anchorterminal.com/compare/crusoe-cloud-vs-runpod.md)\n- [Crusoe Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-thunder-compute.md)\n- [Crusoe Cloud vs Vast.ai](https://www.anchorterminal.com/compare/crusoe-cloud-vs-vast-ai.md)\n- [Crusoe Cloud vs Verda](https://www.anchorterminal.com/compare/crusoe-cloud-vs-verda.md)\n- [GPUsMarket vs Together GPU Clusters](https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.md)\n- [Hugging Face Inference Endpoints vs Together GPU Clusters](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-together-gpu-clusters.md)\n- [Hyperbolic vs Together GPU Clusters](https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters.md)\n- [Koyeb vs Together GPU Clusters](https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters.md)\n- [Lambda Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.md)\n- [Massed Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.md)\n- [Modal vs Together GPU Clusters](https://www.anchorterminal.com/compare/modal-vs-together-gpu-clusters.md)\n- [Nebius AI Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters.md)\n- [Northflank vs Together GPU Clusters](https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters.md)\n- [Replicate Deployments vs Together GPU Clusters](https://www.anchorterminal.com/compare/replicate-deploy-vs-together-gpu-clusters.md)\n- [Runpod vs Together GPU Clusters](https://www.anchorterminal.com/compare/runpod-vs-together-gpu-clusters.md)\n- [Thunder Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters.md)\n- [Together GPU Clusters vs Vast.ai](https://www.anchorterminal.com/compare/together-gpu-clusters-vs-vast-ai.md)\n- [Together GPU Clusters vs Verda](https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda.md)\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": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Crusoe Cloud vs Together GPU Clusters", "url": "" } ], "description": "Crusoe Cloud scores 62.4 (B) to Together GPU Clusters's 58.1 (C) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Crusoe Cloud B 62.4", "Together GPU Clusters C 58.1", "scores" ], "h1": "Crusoe Cloud vs Together GPU Clusters", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/crusoe-cloud-vs-together-gpu-clusters", "published": "2026-10-01", "section": "tools", "title": "Crusoe Cloud vs Together GPU Clusters for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters" }, "tokens": { "markdown": 5850, "slim": 3380 }, "version": 1 }