{ "data": { "a": { "slug": "northflank", "name": "Northflank", "vendor": "Northflank", "vendorUrl": "https://northflank.com", "kind": "platform", "category": "gpu-compute", "summary": "Platform for deploying services, jobs and databases from Git or container images, in managed or customer-owned infrastructure. Supports GPU workloads and sandboxes.", "url": "https://www.anchorterminal.com/tools/northflank", "markdownUrl": "https://www.anchorterminal.com/tools/northflank.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/northflank.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/northflank.json", "dns": "northflank.grade.anchorterminal.com", "transports": [ "http" ], "remoteUrl": "https://api.northflank.com/v1", "packages": [ { "registry": "npm", "name": "@northflank/cli" }, { "registry": "npm", "name": "@northflank/js-client" } ], "auth": "pat", "authNotes": "Personal API token from account settings, or a team token issued under an API role, sent as `Authorization: Bearer` to api.northflank.com/v1. Rate limit headers `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset` come back on every response.", "pricing": "freemium", "pricingNotes": "Pay as you go, pro-rated to the second and charged at the end of the monthly cycle. CPU $0.01667 a vCPU-hour and memory $0.00833 a GB-hour, from a 0.5 vCPU 1 GB plan at $12 a month. GPUs an hour are L4 24 GB $0.80, A100 40 GB $1.42, A100 80 GB $1.76, H100 80 GB $2.74, RTX PRO 6000 96 GB $3.00, and in eights H200 141 GB $3.14 and B200 180 GB $5.87. Persistent NVMe disk $0.11657 a GiB-month and egress $0.06 a GB. Running in your own cloud bills $0.02083 a node vCPU-hour and $1.00 a GB of GPU VRAM a month. The free Sandbox needs no card and gives 2 services, 2 jobs and 1 database, up to $20 a month of resources and one BYOC cluster up to 12 vCPU and 48 GB. Enterprise is by quote with a custom SLA (https://northflank.com/pricing).", "priceSummary": "$0.0167 / vCPU-hr", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 19190, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://northflank.com/docs/v1/application", "llmsTxt": "https://northflank.com/docs/llms.txt", "openapi": "https://api.northflank.com/v1/swagger-json", "capabilities": [ "compute.gpu", "compute.containers", "compute.batch", "compute.endpoints" ], "tags": [ "hosted", "freemium", "free-tier", "openapi", "llms-txt", "typescript", "uk", "enterprise" ], "lastRelease": "2026-09-24", "graded": true, "anchor": { "graded": true, "score": 54, "grade": "C", "agentReady": false, "rank": 925, "ranked": true, "rankOf": 1510, "categoryRank": 14, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 52, "maintenance": 70, "payments": 40, "reliability": 85, "schema": 81, "security": 82, "transparency": 56 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": -15, "negativeNotes": [ "2026-10-30, security incident, open on 2 November. After a Wiz threat alert at 11:43 UTC, Northflank told every customer to \"assume all environment variables have been decrypted\" and rotate all secrets, and reported that users confirmed unauthorised use of AI API keys they had stored on the platform. No cause or postmortem yet. An exfiltration path across the hosted service, 15 points, as trigger-dev's 1 November breach took 15 for a subset of organisations (https://status.northflank.com/history/1).", "2026-11-02, inside the floor. The security page still says \"Northflank has not experienced a security breach since the company's formation\" while the incident above is open, a claim on its own pages that contradicts its status page. A misleading claim on one page, a separate kind, 2 points (https://northflank.com/security).", "Total 15 + 2 = 17, held at the -15 floor." ], "verdict": "Northflank runs services, jobs, databases and GPUs on its cloud or the customer's, with an OpenAPI 3.0 contract, scoped team tokens and a free sandbox that needs no card. On 30 October 2026 it told every customer to assume their environment variables were decrypted, still open on 2 November, while its security page says it has never been breached.", "bestFor": "Teams that want GPUs next to their services and databases on one platform, or inside their own cloud account.", "strengths": [ "OpenAPI 3.0 with over 100 paths, enums and `per_page`, `page` and `cursor` on every list", "Team API tokens under API roles with granular permissions and key rotation, plus audit logs for every customer", "Runs in Northflank's cloud or your own AWS, GCP, Azure or bare metal", "Free Sandbox with no card needed, and llms.txt with a Markdown twin for every docs page", "H100 at $2.74 and A100 80 GB at $1.76 an hour, billed per second" ], "weaknesses": [ "A security incident opened on 30 October 2026, still open on 2 November, told customers to assume all environment variables were decrypted", "The security page says Northflank has never been breached, against its own open incident", "1,000 API requests an hour by default", "Terms and privacy policy unchanged since 1 March 2021, and no security.txt or disclosure policy", "No error schemas in the spec and no idempotency keys" ], "agentNotes": [ "Rotate every secret stored in Northflank, including AI provider keys, and check provider billing before trusting existing credentials. The 30 October 2026 incident was still open on 2 November", "Issue the agent a team token under an API role limited to one project, not a personal token", "Read `x-ratelimit-remaining` and wait `x-ratelimit-reset` seconds on a 429. The default is 1,000 calls an hour", "Page lists with `per_page` up to 100 and the returned `cursor` instead of numbered pages", "Use a job, not a service, for anything that finishes. Services bill until paused or deleted" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 54 } ], "editorialScores": { "ergonomics": 52, "maintenance": 70, "payments": 40, "reliability": 85, "schema": 81, "security": 82, "transparency": 33 }, "provenanceScore": 79, "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": "npm i -g @northflank/cli \u0026\u0026 northflank login", "http": "curl \"https://api.northflank.com/v1/projects\" -H \"Authorization: Bearer $NORTHFLANK_TOKEN\"" }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/northflank" }, "area": "models", "unitPrices": [ { "item": "B200 180 GB", "unit": "gpu-hour", "usd": 5.87, "note": "In nodes of 8" }, { "item": "H200 141 GB", "unit": "gpu-hour", "usd": 3.14, "note": "In nodes of 8" }, { "item": "H100 80 GB", "unit": "gpu-hour", "usd": 2.74, "note": "Billed per second" }, { "item": "RTX PRO 6000 96 GB", "unit": "gpu-hour", "usd": 3 }, { "item": "A100 80 GB", "unit": "gpu-hour", "usd": 1.76 }, { "item": "A100 40 GB", "unit": "gpu-hour", "usd": 1.42 }, { "item": "L4 24 GB", "unit": "gpu-hour", "usd": 0.8 }, { "item": "CPU", "unit": "vcpu-hour", "usd": 0.01667, "note": "Memory extra at $0.00833 a GB-hour" }, { "item": "Egress", "unit": "gb", "usd": 0.06 }, { "item": "Persistent NVMe disk", "unit": "gb-month", "usd": 0.11657, "note": "Per GiB" } ], "provenance": { "legalEntity": "Northflank Ltd", "domain": "northflank.com", "domainRegistered": "2019-03-31", "endpointOnVendorDomain": true, "terms": "https://northflank.com/legal/terms", "privacy": "https://northflank.com/legal/privacy", "statusPage": "https://status.northflank.com", "changelog": "https://northflank.com/changelog", "securityTxt": "none", "checked": "2026-11-02", "notes": [ "Terms and privacy policy, both dated 1 March 2021, name Northflank Ltd, company number 11918540, 20-22 Wenlock Road, London N1 7GU, with legal@northflank.com as contact.", "The API runs on api.northflank.com, a subdomain of the vendor domain.", "northflank.com/.well-known/security.txt returned 404 on 2 November 2026. The security page names security@northflank.com and a Vanta trust centre at trust.northflank.com.", "No public source repository for the platform; the CLI and JavaScript client are published on npm." ], "score": 79 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/northflank.json", "live": { "slug": "northflank", "probe": { "target": "https://api.northflank.com/v1", "method": "get", "lastAt": "2026-11-07T19:22:21.990614639Z", "lastOk": true, "lastStatus": 200, "lastMs": 53, "authRequired": false, "uptime24h": 100, "uptime30d": 99.99, "p50ms24h": 32, "p95ms24h": 134, "samples24h": 238, "samples30d": 7920, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "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": 250 }, { "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.northflank.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:16.496803251Z" }, "versions": [ { "registry": "npm", "name": "@northflank/cli", "version": "0.15.0", "seenAt": "2026-11-06T23:49:40.739192715Z" }, { "registry": "npm", "name": "@northflank/js-client", "version": "0.12.0", "seenAt": "2026-11-06T23:49:41.502233966Z" } ], "npmWeekly": 13207, "securityTxt": { "url": "https://northflank.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:01.257054984Z" }, "llmsTxt": { "url": "https://northflank.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:19.829249521Z" }, "domain": { "domain": "northflank.com", "registered": "2019-03-31", "source": "https://rdap.verisign.com/com/v1/domain/northflank.com", "checkedAt": "2026-11-01T14:28:03.205286282Z" }, "pages": [ { "url": "https://northflank.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:15:06.156731777Z", "changedAt": "2026-10-31T06:16:52.321788675Z", "fingerprint": "6b18c275afdd" }, { "url": "https://northflank.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:15:13.875972691Z", "changedAt": "2026-11-04T08:28:39.185920182Z", "fingerprint": "35d46102475b" }, { "url": "https://northflank.com/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:15:08.309081439Z", "changedAt": "2026-10-31T06:16:54.42220588Z", "fingerprint": "623675afce24" }, { "url": "https://northflank.com/legal/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:15:10.281992439Z", "changedAt": "2026-10-31T06:16:56.422295066Z", "fingerprint": "b7a2eb9a7baf" } ], "updatedAt": "2026-11-07T19:22:21.990614639Z" } }, "answer": "Together GPU Clusters scores 58.1 (C) on agent readiness against Northflank's 54 (C), and leads in 4 of 7 scored categories. Northflank leads on reliability, security \u0026 auth and payments \u0026 pricing.", "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": 47, "category": "reliability", "leads": "northflank", "name": "Reliability", "reasons": { "a": "Graded on the hosted platform lines. Instatus page at status.northflank.com with per-component uptime and history (20). Five notices from 4 August to 2 November 2026. Workloads failed to start for some users across several regions for 1 hour on 5 August (\"partial start up issues\", labelled partial outage), addon expose was paused in US - Central for 2 hours 25 minutes on 4 September (maintenance), SSO through WorkOS was degraded for 46 minutes on 25 September, and on 20 October a GCP europe-west2 zone fault reached login and control plane components for part of 6 hours 50 minutes, with workloads unaffected and \"the majority of users\" unaffected. Each is partial, so minor. The 30 October \"Security incident\", still open on 2 November, marks the platform components as major outage but describes exposed secrets, not downtime, and the Northflank API component shows 100 per cent uptime for October, so it's scored as a negative event (20). 1,000 API requests an hour by default (15). A 429 past the limit, with `x-ratelimit-remaining` and `x-ratelimit-reset` on every response. No backoff or safe-retry guidance (10 of 15). The pricing page lists a 99.99 per cent uptime SLA and a custom SLA on Enterprise; no SLA document was found (10). Services, jobs and GPU workloads are GA (10). 20 + 20 + 15 + 10 + 10 + 10 = 85.", "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": 85, "b": 38 } }, { "by": 20, "category": "payments", "leads": "northflank", "name": "Payments \u0026 pricing", "reasons": { "a": "No machine payment protocol (0). Per-hour GPU, vCPU and memory prices published without a login (20). The free Sandbox plan says \"No card needed\", with 2 services, 2 jobs and 1 database, up to $20 a month of resources (20). Signup is a browser flow (0). 0 + 20 + 20 + 0 = 40.", "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": 40, "b": 20 } }, { "by": 14, "category": "security", "leads": "northflank", "name": "Security \u0026 auth", "reasons": { "a": "Personal tokens and team API tokens issued under API roles with granular permissions and project or cluster restrictions, and the API now documents rotating a key on an API token (30). API roles take per-action permissions and can be restricted to named projects or clusters. No confirmation step for destructive calls found (15). Runs your own containers and returns their output (10). Audit logs with filters since April 2025, enabled for every customer including free users on 31 October 2026 (15). The security page claims SOC 2 Type II, HIPAA and ISO 27001, names security@northflank.com and a trust centre, and says penetration tests are planned. No security.txt (404 on 2 November), disclosure policy, bug bounty or advisories found, and the same page says Northflank has never been breached while the 30 October incident is open. That is fireworks-inference's record (SOC 2 Type II and ISO 27001, a Vanta trust centre, no security.txt, disclosure policy or bounty), so level with it (12). The open incident and the no-breach sentence are counted under negative events, as trigger-dev's breach was, not on this line. 30 + 15 + 10 + 15 + 12 = 82.", "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": 82, "b": 68 } }, { "by": 11, "category": "schema", "leads": "together-gpu-clusters", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.0 at api.northflank.com/v1/swagger-json with well over 100 paths, plus an HTML view, per the 1 October check, not re-read on 2 November (25). llms.txt and a .md twin for every docs page (10). Operations carry short descriptions and the guides explain jobs against services; few say when not to use an endpoint (12). Enums throughout (token kind, scope, restriction mode) and bounded parameters such as `per_page` 1 to 100 (13). Examples in the guides; the spec documents 200 responses but not error schemas (6). Versioned /v1 and a dated changelog (15).", "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": 81, "b": 92 } }, { "by": 9, "category": "transparency", "leads": "together-gpu-clusters", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under UK law (15). Terms and privacy policy are both dated 1 March 2021, more than five years old, with no retention periods we could find (10). Both still read Effective Date 1 March 2021 on 2 November. No deprecation policy or dated notices found (0). Regions and bring-your-own-cloud are documented; no subprocessor list found (8).", "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": 56, "b": 65 } }, { "by": 5, "category": "maintenance", "leads": "together-gpu-clusters", "name": "Maintenance \u0026 community", "reasons": { "a": "The newest changelog digest is dated 24 September 2026, 39 days before the check. The status page's dated updates on 30 and 31 October 2026 announce secret rotation for Postgres, MongoDB and RabbitMQ add-ons and audit logs for all customers, platform changes on the vendor's own page within 30 days (30). Digests come every two months, so one falls in the 90 days from 4 August (24 September, the 23 July digest having left), with the October changes on the status page. Half credit (10). Closed service with a dated changelog and a support address for rate-limit increases (10 of 15). A CLI and JavaScript client on npm and a Python client the docs put at 2.1.0. npm and PyPI couldn't be read on 2 November (15). npm packages not audited (5). 30 + 10 + 10 + 15 + 5 = 70.", "b": "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." }, "scores": { "a": 70, "b": 75 } } ], "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "Northflank", "b": "Together AI", "name": "Vendor" }, { "a": "https://api.northflank.com/v1", "b": "https://api.together.ai/v1/compute/clusters", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "", "name": "Transports" }, { "a": "Token", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "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": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-24", "b": "2026-10-22", "name": "Last release" }, { "a": "2021-03-01", "b": "no date given", "name": "Terms last updated" }, { "a": "2021-03-01", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "19k npm/wk", "b": "none", "name": "Popularity" }, { "a": "3.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Together GPU Clusters scores 58.1 (C) on agent readiness against Northflank's 54 (C), and leads in 4 of 7 scored categories. Northflank leads on reliability, security \u0026 auth and payments \u0026 pricing.", "question": "Which is better for AI agents, Northflank or Together GPU Clusters?" }, { "answer": "Yes. Northflank has a hosted endpoint at https://api.northflank.com/v1 and Together GPU Clusters at https://api.together.ai/v1/compute/clusters.", "question": "Can an agent call Northflank and Together GPU Clusters without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 85 against 38", "Security \u0026 auth, 82 against 68", "Payments \u0026 pricing, 40 against 20" ], "also": null, "goodFor": "Teams that want GPUs next to their services and databases on one platform, or inside their own cloud account.", "slug": "northflank", "watchFor": "A security incident opened on 30 October 2026, still open on 2 November, told customers to assume all environment variables were decrypted" }, { "aheadOn": [ "Schema \u0026 documentation, 92 against 81", "Maintenance \u0026 community, 75 against 70", "Transparency \u0026 trust, 65 against 56" ], "also": [ "No incidents deducted, where Northflank loses 15 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": { "northflank": [ { "causes": [ "pricing", "product", "evidence", "correction", "event" ], "date": "2026-11-02", "delta": -7.4, "from": 61.4, "fromGrade": "C", "to": 54, "toGrade": "C" }, { "causes": [ "evidence" ], "date": "2026-10-28", "delta": 0.1, "from": 61.3, "fromGrade": "C", "to": 61.4, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.5, "from": 61.8, "fromGrade": "C", "to": 61.3, "toGrade": "C" } ], "together-gpu-clusters": null }, "job": { "capability": "compute.gpu", "name": "GPU compute" }, "others": [ { "json": "https://www.anchorterminal.com/compare/baseten-vs-northflank.json", "title": "Baseten vs Northflank", "url": "https://www.anchorterminal.com/compare/baseten-vs-northflank" }, { "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-northflank.json", "title": "Beam vs Northflank", "url": "https://www.anchorterminal.com/compare/beam-vs-northflank" }, { "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-northflank.json", "title": "Cerebrium vs Northflank", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-northflank" }, { "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-northflank.json", "title": "Cloud Run GPUs vs Northflank", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-northflank" }, { "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-northflank.json", "title": "CoreWeave vs Northflank", "url": "https://www.anchorterminal.com/compare/coreweave-vs-northflank" }, { "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-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-together-gpu-clusters.json", "title": "Crusoe Cloud vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-northflank.json", "title": "GPUsMarket vs Northflank", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-northflank" }, { "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-northflank.json", "title": "Hugging Face Inference Endpoints vs Northflank", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-northflank" }, { "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-northflank.json", "title": "Hyperbolic vs Northflank", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-northflank" }, { "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-northflank.json", "title": "Koyeb vs Northflank", "url": "https://www.anchorterminal.com/compare/koyeb-vs-northflank" }, { "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-northflank.json", "title": "Lambda Cloud vs Northflank", "url": "https://www.anchorterminal.com/compare/lambda-vs-northflank" }, { "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-northflank.json", "title": "Massed Compute vs Northflank", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-northflank" }, { "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-northflank.json", "title": "Modal vs Northflank", "url": "https://www.anchorterminal.com/compare/modal-vs-northflank" }, { "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-northflank.json", "title": "Nebius AI Cloud vs Northflank", "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-northflank" }, { "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-replicate-deploy.json", "title": "Northflank vs Replicate Deployments", "url": "https://www.anchorterminal.com/compare/northflank-vs-replicate-deploy" }, { "json": "https://www.anchorterminal.com/compare/northflank-vs-runpod.json", "title": "Northflank vs Runpod", "url": "https://www.anchorterminal.com/compare/northflank-vs-runpod" }, { "json": "https://www.anchorterminal.com/compare/northflank-vs-thunder-compute.json", "title": "Northflank vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/northflank-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/northflank-vs-vast-ai.json", "title": "Northflank vs Vast.ai", "url": "https://www.anchorterminal.com/compare/northflank-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/northflank-vs-verda.json", "title": "Northflank vs Verda", "url": "https://www.anchorterminal.com/compare/northflank-vs-verda" }, { "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": 47, "edge": "northflank", "key": "reliability", "name": "Reliability", "northflank": 85, "together-gpu-clusters": 38, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 11, "edge": "together-gpu-clusters", "key": "schema", "name": "Schema \u0026 documentation", "northflank": 81, "together-gpu-clusters": 92, "weight": 13 }, { "by": 3, "edge": "together-gpu-clusters", "key": "ergonomics", "name": "Agent ergonomics", "northflank": 52, "together-gpu-clusters": 55, "weight": 13 }, { "by": 14, "edge": "northflank", "key": "security", "name": "Security \u0026 auth", "northflank": 82, "together-gpu-clusters": 68, "weight": 14 }, { "by": 20, "edge": "northflank", "key": "payments", "name": "Payments \u0026 pricing", "northflank": 40, "together-gpu-clusters": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 5, "edge": "together-gpu-clusters", "key": "maintenance", "name": "Maintenance \u0026 community", "northflank": 70, "together-gpu-clusters": 75, "weight": 7 }, { "by": 9, "edge": "together-gpu-clusters", "key": "transparency", "name": "Transparency \u0026 trust", "northflank": 56, "together-gpu-clusters": 65, "weight": 7 } ], "summary": "Together GPU Clusters scores 58.1 (C) on agent readiness against Northflank's 54 (C), and leads in 4 of 7 scored categories. Northflank leads on reliability, security \u0026 auth and payments \u0026 pricing. Both do gpu compute.", "tasks": null, "tutorials": [], "verdicts": { "northflank": "Northflank runs services, jobs, databases and GPUs on its cloud or the customer's, with an OpenAPI 3.0 contract, scoped team tokens and a free sandbox that needs no card. On 30 October 2026 it told every customer to assume their environment variables were decrypted, still open on 2 November, while its security page says it has never been breached.", "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/northflank-vs-together-gpu-clusters", "json": "https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters.min.md" }, "markdown": "Together GPU Clusters scores 58.1 (C) on agent readiness against Northflank's 54 (C), and leads in 4 of 7 scored categories. Northflank leads on reliability, security \u0026 auth and payments \u0026 pricing. Both do gpu compute.\n\n- Northflank: grade C, 54/100, rank #925 of 1510. Markdown https://www.anchorterminal.com/tools/northflank.md · JSON https://www.anchorterminal.com/api/v1/tools/northflank.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### Northflank (C)\n\nGood for: Teams that want GPUs next to their services and databases on one platform, or inside their own cloud account.\n\nAhead on:\n- Reliability, 85 against 38\n- Security \u0026 auth, 82 against 68\n- Payments \u0026 pricing, 40 against 20\n\nWatch for: A security incident opened on 30 October 2026, still open on 2 November, told customers to assume all environment variables were decrypted\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 81\n- Maintenance \u0026 community, 75 against 70\n- Transparency \u0026 trust, 65 against 56\n\nAlso in its favour:\n- No incidents deducted, where Northflank loses 15 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: Northflank +47\n\n- Northflank (85): Graded on the hosted platform lines. Instatus page at status.northflank.com with per-component uptime and history (20). Five notices from 4 August to 2 November 2026. Workloads failed to start for some users across several regions for 1 hour on 5 August (\"partial start up issues\", labelled partial outage), addon expose was paused in US - Central for 2 hours 25 minutes on 4 September (maintenance), SSO through WorkOS was degraded for 46 minutes on 25 September, and on 20 October a GCP europe-west2 zone fault reached login and control plane components for part of 6 hours 50 minutes, with workloads unaffected and \"the majority of users\" unaffected. Each is partial, so minor. The 30 October \"Security incident\", still open on 2 November, marks the platform components as major outage but describes exposed secrets, not downtime, and the Northflank API component shows 100 per cent uptime for October, so it's scored as a negative event (20). 1,000 API requests an hour by default (15). A 429 past the limit, with `x-ratelimit-remaining` and `x-ratelimit-reset` on every response. No backoff or safe-retry guidance (10 of 15). The pricing page lists a 99.99 per cent uptime SLA and a custom SLA on Enterprise; no SLA document was found (10). Services, jobs and GPU workloads are GA (10). 20 + 20 + 15 + 10 + 10 + 10 = 85.\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### Payments \u0026 pricing: Northflank +20\n\n- Northflank (40): No machine payment protocol (0). Per-hour GPU, vCPU and memory prices published without a login (20). The free Sandbox plan says \"No card needed\", with 2 services, 2 jobs and 1 database, up to $20 a month of resources (20). Signup is a browser flow (0). 0 + 20 + 20 + 0 = 40.\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: Northflank +14\n\n- Northflank (82): Personal tokens and team API tokens issued under API roles with granular permissions and project or cluster restrictions, and the API now documents rotating a key on an API token (30). API roles take per-action permissions and can be restricted to named projects or clusters. No confirmation step for destructive calls found (15). Runs your own containers and returns their output (10). Audit logs with filters since April 2025, enabled for every customer including free users on 31 October 2026 (15). The security page claims SOC 2 Type II, HIPAA and ISO 27001, names security@northflank.com and a trust centre, and says penetration tests are planned. No security.txt (404 on 2 November), disclosure policy, bug bounty or advisories found, and the same page says Northflank has never been breached while the 30 October incident is open. That is fireworks-inference's record (SOC 2 Type II and ISO 27001, a Vanta trust centre, no security.txt, disclosure policy or bounty), so level with it (12). The open incident and the no-breach sentence are counted under negative events, as trigger-dev's breach was, not on this line. 30 + 15 + 10 + 15 + 12 = 82.\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### Schema \u0026 documentation: Together GPU Clusters +11\n\n- Northflank (81): OpenAPI 3.0 at api.northflank.com/v1/swagger-json with well over 100 paths, plus an HTML view, per the 1 October check, not re-read on 2 November (25). llms.txt and a .md twin for every docs page (10). Operations carry short descriptions and the guides explain jobs against services; few say when not to use an endpoint (12). Enums throughout (token kind, scope, restriction mode) and bounded parameters such as `per_page` 1 to 100 (13). Examples in the guides; the spec documents 200 responses but not error schemas (6). Versioned /v1 and a dated changelog (15).\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: Together GPU Clusters +9\n\n- Northflank (56): Closed service under UK law (15). Terms and privacy policy are both dated 1 March 2021, more than five years old, with no retention periods we could find (10). Both still read Effective Date 1 March 2021 on 2 November. No deprecation policy or dated notices found (0). Regions and bring-your-own-cloud are documented; no subprocessor list found (8).\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### Maintenance \u0026 community: Together GPU Clusters +5\n\n- Northflank (70): The newest changelog digest is dated 24 September 2026, 39 days before the check. The status page's dated updates on 30 and 31 October 2026 announce secret rotation for Postgres, MongoDB and RabbitMQ add-ons and audit logs for all customers, platform changes on the vendor's own page within 30 days (30). Digests come every two months, so one falls in the 90 days from 4 August (24 September, the 23 July digest having left), with the October changes on the status page. Half credit (10). Closed service with a dated changelog and a support address for rate-limit increases (10 of 15). A CLI and JavaScript client on npm and a Python client the docs put at 2.1.0. npm and PyPI couldn't be read on 2 November (15). npm packages not audited (5). 30 + 10 + 10 + 15 + 5 = 70.\n- Together GPU Clusters (75): Closed service. The newest cluster change is CLI and SDK 3.0 on 22 October 2026, 15 days before this check (30). Dated cluster entries in the 90 days from 8 August include 12, 18, 19, 24, 27 and 28 August, 10 September and 22 October (20). Dated changelog, a support portal and Discord, with responsiveness not tested (8). Python SDK 3.1 and TypeScript SDK 1.0 are current and cover clusters (15). SDK CI and dependencies weren't audited (2). 30+20+8+15+2 = 75.\n\n## Score by category\n\n| Category | Weight | Northflank | Together GPU Clusters | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 85 | 38 | Northflank +47 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 81 | 92 | Together GPU Clusters +11 |\n| Agent ergonomics | 13% (16.2 this run) | 52 | 55 | Together GPU Clusters +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 82 | 68 | Northflank +14 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 20 | Northflank +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 70 | 75 | Together GPU Clusters +5 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 56 | 65 | Together GPU Clusters +9 |\n| Negative events | ≤15 | -15 | 0 | |\n| **Total** | | **54 · C** | **58.1 · C** | |\n\n## Facts side by side\n\n| Fact | Northflank | Together GPU Clusters |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | Northflank | Together AI |\n| Hosted endpoint | `https://api.northflank.com/v1` | `https://api.together.ai/v1/compute/clusters` |\n| Transports | HTTP | |\n| Auth | Token | API key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | no |\n| Licence | none | Proprietary service under Together's terms of service. The Python SDK and CLI are Apache-2.0 and the OpenAPI document is MIT |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-24 | 2026-10-22 |\n| Terms last updated | 2021-03-01 | no date given |\n| Privacy policy last updated | 2021-03-01 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 19k npm/wk | none |\n| Agent reviews | 3.5/5 (2) | none |\n\n## How the scores have moved\n\n### Northflank\n\n- -7.4 on 2 November 2026: pricing, product, new evidence, correction, negative event\n- +0.1 on 28 October 2026: new evidence\n- -0.5 on 8 October 2026: checklist\n\n### Together GPU Clusters\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Northflank.** Northflank runs services, jobs, databases and GPUs on its cloud or the customer's, with an OpenAPI 3.0 contract, scoped team tokens and a free sandbox that needs no card. On 30 October 2026 it told every customer to assume their environment variables were decrypted, still open on 2 November, while its security page says it has never been breached.\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### Northflank\n\n1. Rotate every secret stored in Northflank, including AI provider keys, and check provider billing before trusting existing credentials. The 30 October 2026 incident was still open on 2 November\n2. Issue the agent a team token under an API role limited to one project, not a personal token\n3. Read `x-ratelimit-remaining` and wait `x-ratelimit-reset` seconds on a 429. The default is 1,000 calls an hour\n4. Page lists with `per_page` up to 100 and the returned `cursor` instead of numbered pages\n5. Use a job, not a service, for anything that finishes. Services bill until paused or deleted\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, Northflank or Together GPU Clusters?\n\nTogether GPU Clusters scores 58.1 (C) on agent readiness against Northflank's 54 (C), and leads in 4 of 7 scored categories. Northflank leads on reliability, security \u0026 auth and payments \u0026 pricing.\n\n### Can an agent call Northflank and Together GPU Clusters without installing anything?\n\nYes. Northflank has a hosted endpoint at https://api.northflank.com/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/northflank-vs-together-gpu-clusters.json, and with the fewest tokens: https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"northflank\", \"b\": \"together-gpu-clusters\"}`. From a terminal: `anchor compare northflank together-gpu-clusters`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/northflank.json and https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json\n\n## Other comparisons with Northflank or Together GPU Clusters\n\n- [Baseten vs Northflank](https://www.anchorterminal.com/compare/baseten-vs-northflank.md)\n- [Baseten vs Together GPU Clusters](https://www.anchorterminal.com/compare/baseten-vs-together-gpu-clusters.md)\n- [Beam vs Northflank](https://www.anchorterminal.com/compare/beam-vs-northflank.md)\n- [Beam vs Together GPU Clusters](https://www.anchorterminal.com/compare/beam-vs-together-gpu-clusters.md)\n- [Cerebrium vs Northflank](https://www.anchorterminal.com/compare/cerebrium-vs-northflank.md)\n- [Cerebrium vs Together GPU Clusters](https://www.anchorterminal.com/compare/cerebrium-vs-together-gpu-clusters.md)\n- [Cloud Run GPUs vs Northflank](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-northflank.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 Northflank](https://www.anchorterminal.com/compare/coreweave-vs-northflank.md)\n- [CoreWeave vs Together GPU Clusters](https://www.anchorterminal.com/compare/coreweave-vs-together-gpu-clusters.md)\n- [Crusoe Cloud vs Northflank](https://www.anchorterminal.com/compare/crusoe-cloud-vs-northflank.md)\n- [Crusoe Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters.md)\n- [GPUsMarket vs Northflank](https://www.anchorterminal.com/compare/gpusmarket-vs-northflank.md)\n- [GPUsMarket vs Together GPU Clusters](https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.md)\n- [Hugging Face Inference Endpoints vs Northflank](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-northflank.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 Northflank](https://www.anchorterminal.com/compare/hyperbolic-vs-northflank.md)\n- [Hyperbolic vs Together GPU Clusters](https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters.md)\n- [Koyeb vs Northflank](https://www.anchorterminal.com/compare/koyeb-vs-northflank.md)\n- [Koyeb vs Together GPU Clusters](https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters.md)\n- [Lambda Cloud vs Northflank](https://www.anchorterminal.com/compare/lambda-vs-northflank.md)\n- [Lambda Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.md)\n- [Massed Compute vs Northflank](https://www.anchorterminal.com/compare/massed-compute-vs-northflank.md)\n- [Massed Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.md)\n- [Modal vs Northflank](https://www.anchorterminal.com/compare/modal-vs-northflank.md)\n- [Modal vs Together GPU Clusters](https://www.anchorterminal.com/compare/modal-vs-together-gpu-clusters.md)\n- [Nebius AI Cloud vs Northflank](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-northflank.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 Replicate Deployments](https://www.anchorterminal.com/compare/northflank-vs-replicate-deploy.md)\n- [Northflank vs Runpod](https://www.anchorterminal.com/compare/northflank-vs-runpod.md)\n- [Northflank vs Thunder Compute](https://www.anchorterminal.com/compare/northflank-vs-thunder-compute.md)\n- [Northflank vs Vast.ai](https://www.anchorterminal.com/compare/northflank-vs-vast-ai.md)\n- [Northflank vs Verda](https://www.anchorterminal.com/compare/northflank-vs-verda.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": "Northflank vs Together GPU Clusters", "url": "" } ], "description": "Together GPU Clusters scores 58.1 (C) to Northflank's 54 (C) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Northflank C 54", "Together GPU Clusters C 58.1", "scores" ], "h1": "Northflank vs Together GPU Clusters", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/northflank-vs-together-gpu-clusters", "published": "2026-10-01", "section": "tools", "title": "Northflank vs Together GPU Clusters for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters" }, "tokens": { "markdown": 5150, "slim": 2830 }, "version": 1 }