# CoreWeave > CoreWeave is a GPU cloud that rents NVIDIA GPU nodes through a managed Kubernetes service (CKS), with REST and gRPC platform APIs, a Terraform provider and a hosted MCP server for observability. - Canonical: https://www.anchorterminal.com/tools/coreweave - Markdown: https://www.anchorterminal.com/tools/coreweave.md (~8,050 tokens) - Slim: https://www.anchorterminal.com/tools/coreweave.min.md (~1,630 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/coreweave.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade C · 61.5/100 · rank #363 of 722 · #5 in GPU & serverless compute · not agent-ready · confidence medium** ## Assessment Per-hour prices for 8-GPU H100, H200 and B200 nodes are public, the docs ship as Markdown with llms.txt and embedded OpenAPI specs, and IAM has read-only roles per service. An organisation must be approved by CoreWeave's sales team before any token exists, and no request rate limits were found in the reviewed documentation. ## Facts | Field | Value | | --- | --- | | Vendor | CoreWeave, Inc. (https://www.coreweave.com) | | Kind | HTTP API | | Category | GPU & serverless compute (https://www.anchorterminal.com/categories/gpu-compute) | | Transport | HTTP | | Endpoint | `https://api.coreweave.com` | | Auth | Token · Access starts with sales approval. CoreWeave's sales team approves an organisation and emails an activation link, then a user with the Access Token User role creates an API access token at console.coreweave.com/tokens with a name and an expiry. The token is user-scoped, shown once, revocable in the console and sent as `Authorization: Bearer` to api.coreweave.com, to a CKS cluster's Kubernetes API (through a kubeconfig) and to the Mission Control MCP server. What it can do follows the user's IAM roles, which include a Viewer and an Admin role per service. CKS workloads can also use OIDC workload identity federation. Serverless Inference takes a separate Forge API key. | | Pricing | Pay per use (Pay per use) · Per instance-hour, published without a login. On demand in North America, HGX H100 (8 GPUs) $49.24, HGX H200 $50.44, HGX B200 $68.80, A100 $21.60, L40S $18.00, L40 $10.00, GB200 NVL72 (4 GPUs) $42.00 and GH200 (1 GPU) $6.50, with spot rates on most. GB300 NVL72 and HGX B300 on demand are quoted by sales. Reserved capacity is discounted by up to 60 per cent through sales. AI Object Storage is $0.06 a GB-month hot, $0.03 warm and $0.015 cold, distributed file storage $0.07, and egress, VPC and the CKS control plane are free. No free tier or self-serve trial was found, and the terms treat any trial as part of the sales-run ARENA programme (https://www.coreweave.com/pricing, https://docs.coreweave.com/policies/terms-of-service). | | x402 | No · No x402, MPP or L402 in the docs index, the API references or the pricing page (checked 2026-10-08). | | Licence | Proprietary service under CoreWeave's Terms of Service. The Terraform provider on GitHub is MIT | | Tools exposed | 38 | | Source | https://github.com/coreweave/terraform-provider-coreweave | | Docs | https://docs.coreweave.com/ | | llms.txt | https://docs.coreweave.com/llms.txt | | Last release | 2026-10-02 | | Free tier | None found. Trials run through the sales-led ARENA programme | | Access | Sales approves the organisation, then tokens are created in the Cloud Console | | GPUs | GB300 and GB200 NVL72, HGX B300, B200, H200 and H100, A100, L40S, L40, GH200 and RTX PRO 6000 Blackwell, mostly as 8-GPU nodes. Vera Rubin NVL72 in limited availability from 30 September 2026 | | Scale to zero | Node Pools take `targetNodes`, `minNodes` and `maxNodes` with an optional autoscaler. Nodes bill while they exist | | Billing basis | Per instance-hour, monthly in arrears. Invoices under $20,000 are charged to the card on file | | Rate limits | No request rate limits found. The gateway caps Kubernetes API requests at about 50 KB of URL and headers and 100 MB of body | | APIs | CKS (v1beta1), VPC, Object Storage, Dedicated Inference (v1alpha1), Capacity Finder, Telemetry Relay and FOCUS usage export at api.coreweave.com, REST and gRPC, with generated clients on the Buf Schema Registry | | MCP | Mission Control at https://mc.coreweave.com/mcp, streamable HTTP, 38 documented tools, 2 of them write tools enabled per organisation | | Service level | Objective of 99.9 per cent across multiple regions and 99 per cent in one, with credits of up to 50 per cent of the month's bill | | Regions | Seven super regions (US-EAST, US-CENTRAL, US-WEST, CA-EAST, EU-NORTH, EU-SOUTH, EU-WEST) | | Capabilities | compute.gpu, compute.containers, compute.endpoints, compute.batch | | Tags | hosted, usage-priced, enterprise, sales-led, mcp, openapi, llms-txt, terraform, status-page, soc2 | | JSON | https://www.anchorterminal.com/api/v1/tools/coreweave.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 50 | 10.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 79 | 12.8 | | Agent ergonomics | 13% | 16.2 | 58 | 9.4 | | Security & auth | 14% | 17.5 | 74 | 12.9 | | Payments & pricing | 10% | 12.5 | 20 | 2.5 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 80 | 7.0 | | Transparency & trust (editorial 71, provenance 83) | 7% | 8.8 | 77 | 6.7 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **61.5 → C** | ### Why each score - Reliability 50: Graded as a hosted service on the CKS and platform APIs. Status.io page at status.coreweave.com with components per data centre, an RSS feed and email, webhook and Slack subscriptions (20). The history page is drawn by script and the feed holds ten items back to 25 September 2026, so only the last two weeks were readable. In that window the Cloud Console returned 404 for about 40 minutes on 6 October, US-CENTRAL-09A lost network connectivity from 06:22 to 08:37 UTC on 5 October, and object storage in the same zone ran at reduced IOPS for about two hours on 26 September. One major regional outage (10). No request rate limits found for api.coreweave.com, only gateway size limits of about 50 KB and 100 MB, and quotas are set per customer through support (0). No 429 or backoff guidance and no idempotency keys found. Kubernetes resources are declarative, so re-applying a manifest is safe (5 of 15). The terms set an objective of 99.9 per cent across multiple regions and 99 per cent in one, with financial credits (10). CKS is sold as a general service but its cluster API is v1beta1 and the Node Pool resource v1alpha1 (5 of 10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 79: OpenAPI 3.0 specs for the CKS, VPC, Object Storage, Dedicated Inference, Capacity Finder and Telemetry Relay APIs are embedded in the reference pages, and the same services are published as Protobuf on the Buf Schema Registry. The raw .yaml paths in llms.txt redirected our reader to a docs login (25). llms.txt at docs.coreweave.com and every page served as Markdown (10). Operations and MCP tools state their purpose and inputs, with few lines on when not to use them (12). Required fields are marked and the Node Pool reference lists enums, but the CKS spec has none and instance types and versions are plain strings (9). Each operation page has a curl example. Errors are one generic `code`, `message`, `details` shape with no per-operation codes (8). Versioned paths and a dated changelog of 168 entries since December 2024 (15). - Agent ergonomics 58: Graded on the platform API, the Kubernetes API and the Mission Control MCP server together. The MCP server documents 38 tools, most of them small read-only queries with limits, and every tool also takes an optional `user_prompt` (12 of 25). The Dedicated Inference API pages with `maxPageSize` and `pageToken`. The cluster list returns everything, with `returnPartialSuccess` for unreachable zones (14). Errors follow the google.rpc shape with a numeric code and a message, and support articles explain common failures (12). No idempotency keys, no MCP read-only or destructive annotations documented, and `coreweave_kubectl_apply` ignores `dry_run` and `plan_token` and applies the manifest (8). Generated clients on Buf for Go, Python, TypeScript, Java and others, plus a Terraform provider. Creating a cluster needs a zone, version and VPC (12). - Security & auth 74: API access tokens are user-scoped, carry an expiry, are shown once and can be revoked in the console. They inherit the user's IAM roles and have no scopes of their own. OIDC workload identity federation is available for CKS workloads. Tokens travel in the Authorization header only (25). IAM has a Viewer and an Admin role per service, and the MCP write tools are off unless CoreWeave enables them for an organisation. There is no confirmation step, and the apply tool ignores `dry_run` (15). The MCP server returns log lines and documentation text, which are untrusted content, and no injection guidance was found (5). Kubernetes audit logs have a Grafana dashboard, Telemetry Relay forwards audit logs to HTTPS or S3, and support staff access is controlled and logged (15). Vulnerability disclosure policy with safe harbour, trust centre badges for SOC 2 Type II, ISO 27001, 27017 and 27018, and a security advisories page whose latest entry is July 2024. No security.txt and no bug bounty found (14). - Payments & pricing 20: No machine payment protocol (0). Per instance-hour prices for GPUs, CPUs, storage and networking are published without a login, with some models quoted by sales (20). No free tier or self-serve trial found. Trials run through the sales-led ARENA programme (0). An organisation has to be approved by the sales team and a person creates the token in the console (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 80: The changelog's latest entry is 2 October 2026 (30). It has 18 dated entries between 10 July and 2 October 2026 (20). Closed service with a dated changelog, a support centre and status updates by email. No public issue tracker for the platform (10 of 15). Generated clients on the Buf Schema Registry and a Terraform provider tagged v0.24.0 on 11 September 2026, the eighth tag since 14 July. The MCP server isn't in the official MCP registry (12). The provider repository has build, test, acceptance-test, release and Renovate workflows. We didn't check that they pass (8). - Transparency & trust 77: Closed service with published terms. They were last modified on 30 June 2022 and say they may be amended without notice (15). The terms commit to deleting customer data after account closure within a 30-day recovery period and at most 180 days, there is a data processing agreement, and the privacy policy of 24 February 2026 gives no fixed retention period for personal data (22). The changelog gives dated deprecations, for example operating system and driver versions from 29 July 2026, and the maintenance policy promises 24 hours' notice for critical work, though it can change without notice (14). Three sub-processors are named with their country and 30 days' notice of additions, and regions and availability zones are documented (20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (17 items): https://www.anchorterminal.com/fixes/coreweave.md (JSON https://www.anchorterminal.com/fixes/coreweave.json) ### What we couldn't check - unchecked: status history before 25 September 2026. The Status.io history page is drawn by script and the feed keeps ten items, so the 90-day record is scored on two weeks. - unchecked: the raw OpenAPI .yaml files named in llms.txt redirected to a docs login, so the specs were read as embedded in the reference pages. - unchecked: whether the Terraform provider's CI passes on the default branch. - unchecked: id.coreweave.com/signup is drawn by script. The docs say the sales team approves each organisation, and we couldn't see whether that page opens an infrastructure account without approval. - unchecked: the trust centre's documents sit behind an access request, so the certifications are badges we read, not reports. - No request rate limits, billing increment for on-demand nodes or bug bounty were found in the reviewed documentation. - The lead lists Serverless Inference as part of this product. It is a Forge service at api.inference.wandb.ai with its own key and plans, so it is noted here and not graded. ### Sources - docs index (llms.txt): (seen 2026-10-08) - CKS API reference with OpenAPI spec: (seen 2026-10-08) - Node Pool reference: (seen 2026-10-08) - Dedicated Inference API reference: (seen 2026-10-08) - Serverless Inference API reference: (seen 2026-10-08) - Mission Control MCP tool reference: (seen 2026-10-08) - Mission Control MCP configuration: (seen 2026-10-08) - API access tokens: (seen 2026-10-08) - IAM roles: (seen 2026-10-08) - organisation activation: (seen 2026-10-08) - pricing: (seen 2026-10-08) - Terms of Service: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - sub-processors: (seen 2026-10-08) - maintenance policy: (seen 2026-10-08) - vulnerability disclosure policy: (seen 2026-10-08) - limits and quotas: (seen 2026-10-08) - Kubernetes API request size limits: (seen 2026-10-08) - changelog: (seen 2026-10-08) - status page: (seen 2026-10-08) - status feed: (seen 2026-10-08) - trust centre: (seen 2026-10-08) - security.txt (404): (seen 2026-10-08) - Terraform provider repository: (seen 2026-10-08) - official MCP registry search (no result): (seen 2026-10-08) - domain registration: (seen 2026-10-08) ## Who's behind it (provenance 83/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | CoreWeave, Inc. | 20/20 | | Domain age | coreweave.com, registered 2019-04-01 (7 years) | 11/15 | | Endpoint on the vendor's domain | api.coreweave.com | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects, and has 1 clause that costs points | 7.1/10 | | Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 | | Status page | status.coreweave.com | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The Terms of Service on docs.coreweave.com govern the CoreWeave Cloud Platform and were last modified on 30 June 2022. They are under New York law. The separate Terms of Use page covers the websites only. The privacy policy names CoreWeave, Inc. and its affiliates and was last updated on 24 February 2026. www.coreweave.com/.well-known/security.txt and coreweave.com/.well-known/security.txt return 404. A vulnerability disclosure policy is published in the docs. The APIs run on api.coreweave.com and mc.coreweave.com. Serverless Inference runs on api.inference.wandb.ai. coreweave.com was registered on 2019-04-01 per Verisign RDAP. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://docs.coreweave.com/policies/terms-of-service), read 2026-10-08, dated 2022-06-30, states 6 of the 7 things a reader expects. - To know. Says the terms or the service can change without notice (costs points). "The TOS for the CoreWeave Cloud Platform as a Covered Service may be amended and/or modified from time to time by CoreWeave, without notice to Customer." - To know. Has not been updated for three years or more. "Last modified: June 30, 2022" - Gives the date it was last updated. Last updated 2022-06-30. - Names the governing law or courts. The law of the State of New York. - States a limit on its liability. Capped at the fees paid in the 12 months before the claim. - Not found in the text. Says how changes to the terms are announced. - Also in the text (2026-10-08). The customer grants CoreWeave permission to use its name, logos and trademarks in promotional and marketing materials. "Customer grants CoreWeave permission to include Customer’s name, logos, and trademarks in its promotional and marketing materials and communications." - Also in the text (2026-10-08). After a term ends or an account closes, CoreWeave deletes Customer Data on the customer's instruction after a recovery period of up to 30 days and within at most 180 days. "CoreWeave will, after a recovery period of up to thirty (30) days following such expiry, comply with this instruction as soon as reasonably practicable and within a maximum period of one hundred eighty (180) days." - Also in the text (2026-10-08). All on-demand compute usage fees are subject to change. "All on-demand compute usage fees are subject to change." **Privacy policy** (https://docs.coreweave.com/policies/terms-of-service/privacy-policy), read 2026-10-08, dated 2026-02-24, states 8 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "We may share personal data with affiliated companies for cross-context behavioral advertising, which means targeted advertising based on your activity across different websites, applications, or services over time." - Gives the date it was last updated. Last updated 2026-02-24. - Says how long data is kept. For as long as needed, with no period named. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. privacy@coreweave.com. - Says where data is transferred or stored. Relies on standard contractual clauses. - Also in the text (2026-10-08). CoreWeave collects content customers submit through the Services, including inputs and outputs from service tools, and lists developing and improving products among the purposes. "We collect the content you submit through the Services and our Sites, including messages, posts, comments, support communications, customer-facing Slack interactions, and inputs and outputs from service tools and offerings." - Also in the text (2026-10-08). CoreWeave may use artificial intelligence and machine learning when processing data to operate, maintain, improve and develop its Services. "CoreWeave may use technologies such as artificial intelligence (AI) and machine learning (ML) when processing your data to operate, maintain, improve, and develop our Services." ## Live (updated 2026-10-08 19:52 UTC) - Right now: up, HTTP 404, 155 ms, checked 2026-10-08 19:52 UTC (get on `https://api.coreweave.com`) - Uptime 24h 100.0% (27 probes) · 30 days 100.0% (27 probes) · p50 143 ms · p95 202 ms - Vendor status page: unknown, no machine-readable status found - Watching changelog - Watching pricing - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/coreweave.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | HGX H100 80 GB | $6.16 | per GPU-hour | Published single-GPU rate. Sold as an 8-GPU node at $49.24 an hour on demand, $19.71 spot | | HGX H200 141 GB | $6.31 | per GPU-hour | 8-GPU node at $50.44 an hour on demand, $20.93 spot | | HGX B200 180 GB | $8.60 | per GPU-hour | 8-GPU node at $68.80 an hour on demand, $34.11 spot | | GB200 NVL72 186 GB | $10.50 | per GPU-hour | 4-GPU instance at $42.00 an hour on demand | | A100 80 GB | $2.70 | per GPU-hour | 8-GPU node at $21.60 an hour on demand, $9.65 spot | | L40S 48 GB | $2.25 | per GPU-hour | 8-GPU node at $18.00 an hour on demand, $7.88 spot | | AI Object Storage, hot tier | $0.06 | per GB per month | Warm $0.03, cold $0.015. No egress fee | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - On-demand and spot prices per instance-hour are public, for example HGX H100 at $49.24 on demand and $19.71 spot for 8 GPUs - Docs are served as Markdown with an llms.txt index, and OpenAPI 3.0 specs for CKS, VPC, storage and inference are embedded in the reference pages - IAM has Viewer and Admin roles per service, API tokens carry an expiry, and Kubernetes audit logs can be forwarded with Telemetry Relay - Terms carry a service level objective of 99.9 per cent across multiple regions and 99 per cent in one, with financial credits - Dated changelog with 18 entries between 10 July and 2 October 2026, and a Terraform provider tagged v0.24.0 on 11 September 2026 ## Weaknesses - No self-serve route. CoreWeave's sales team approves an organisation and emails the activation link before a token can be created - No request rate limits, 429 guidance or idempotency keys found for api.coreweave.com in the reviewed documentation - The CKS API is versioned v1beta1 and the Node Pool resource and Dedicated Inference API v1alpha1 - Three incidents between 26 September and 6 October 2026, including a US-CENTRAL-09A network outage of over two hours on 5 October - The MCP tool `coreweave_kubectl_apply` ignores its `dry_run` parameter and applies the manifest, per the tool reference ## Before you call it (notes for agents) 1. Create an API access token at console.coreweave.com/tokens with an expiry and send it as `Authorization: Bearer` to https://api.coreweave.com 2. Add GPUs by applying a NodePool resource (`compute.coreweave.com/v1alpha1`) to a CKS cluster with `instanceType` and `targetNodes`. `instanceType` can't be changed afterwards 3. Set `targetNodes` to 0 or delete the Node Pool when a job ends. Nodes are whole 8-GPU machines billed by the hour 4. Never pass `dry_run` to the MCP tool `coreweave_kubectl_apply` expecting a preview. The reference says the parameter is ignored and the manifest is applied 5. Use a separate Forge API key and https://api.inference.wandb.ai/v1 for Serverless Inference. A CoreWeave API access token doesn't work there ## Connect First request: ```bash curl "https://api.coreweave.com/v1beta1/cks/clusters" -H "Authorization: Bearer $COREWEAVE_API_TOKEN" ``` Claude Code: ```bash claude mcp add --transport http mission-control https://mc.coreweave.com/mcp --header "Authorization: Bearer [YOUR-COREWEAVE-API-TOKEN]" ``` MCP client configuration: ```json { "mcpServers": { "mission-control": { "headers": { "Authorization": "Bearer [YOUR-COREWEAVE-API-TOKEN]" }, "url": "https://mc.coreweave.com/mcp" } } } ``` Through letme (picks today, calling later): https://letme.dev/coreweave. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Modal | B | 63.6 | 302 | compute.gpu, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/modal.md | | Northflank | C | 61.3 | 367 | compute.gpu, compute.containers, compute.batch, compute.endpoints | no | https://www.anchorterminal.com/tools/northflank.md | | Beam | C | 55.5 | 507 | compute.gpu, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/beam.md | | Cerebrium | C | 55.3 | 512 | compute.gpu, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/cerebrium.md | | Runpod | D | 53.5 | 542 | compute.gpu, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/runpod.md | | Baseten | B | 66.5 | 233 | compute.gpu, compute.endpoints, compute.containers | no | https://www.anchorterminal.com/tools/baseten.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The CKS API at https://api.coreweave.com/v1beta1/cks/clusters lists, creates, updates and deletes clusters over REST or gRPC with a Bearer API access token. GPU nodes are then added by applying a NodePool resource to the cluster (source: ) - A new organisation is approved by the CoreWeave sales team, which emails an activation link to its creator. Initial sign-up is by email only (source: ) - Mission Control MCP is a hosted server at https://mc.coreweave.com/mcp with 38 documented tools, 36 read-only for metrics, logs, dashboards, docs, billing, clusters and nodes, and 2 write tools that CoreWeave enables per organisation (source: ) - Pricing is per instance-hour. HGX H100 with 8 GPUs is $49.24 on demand and $19.71 spot, HGX B200 $68.80 and $34.11, HGX H200 $50.44 and $20.93. The CKS control plane, egress and VPC are free (source: ) - The Terms of Service, last modified 30 June 2022, set a service level objective of 99.9 per cent for instances in multiple regions and 99 per cent in one region, with credits capped at 50 per cent of the month's bill, and say the terms may be amended without notice (source: ) - Serverless Inference is a Forge product at https://api.inference.wandb.ai/v1 with OpenAI-compatible chat completions and a Forge API key, separate from the infrastructure token (source: ) - The status page runs on Status.io with components per data centre. Its feed shows a console outage on 6 October 2026, a US-CENTRAL-09A networking incident on 5 October and reduced object storage IOPS on 26 September (source: ) - The trust centre shows badges for SOC 2 Type II, ISO 27001, ISO 27017 and ISO 27018, and three sub-processors are named with 30 days' notice of additions (source: ) ## Compare - [Baseten vs CoreWeave](https://www.anchorterminal.com/compare/baseten-vs-coreweave.md): B 66.5 vs C 61.5 - [Beam vs CoreWeave](https://www.anchorterminal.com/compare/beam-vs-coreweave.md): C 55.5 vs C 61.5 - [Cerebrium vs CoreWeave](https://www.anchorterminal.com/compare/cerebrium-vs-coreweave.md): C 55.3 vs C 61.5 - [CoreWeave vs Koyeb](https://www.anchorterminal.com/compare/coreweave-vs-koyeb.md): C 61.5 vs D 46.5 - [CoreWeave vs Lambda Cloud](https://www.anchorterminal.com/compare/coreweave-vs-lambda.md): C 61.5 vs D 50 - [CoreWeave vs Modal](https://www.anchorterminal.com/compare/coreweave-vs-modal.md): C 61.5 vs B 63.6 - [CoreWeave vs Northflank](https://www.anchorterminal.com/compare/coreweave-vs-northflank.md): C 61.5 vs C 61.3 - [CoreWeave vs Replicate Deployments](https://www.anchorterminal.com/compare/coreweave-vs-replicate-deploy.md): C 61.5 vs B 63.6 - [CoreWeave vs Runpod](https://www.anchorterminal.com/compare/coreweave-vs-runpod.md): C 61.5 vs D 53.5 - [CoreWeave vs Vast.ai](https://www.anchorterminal.com/compare/coreweave-vs-vast-ai.md): C 61.5 vs B 62.6 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on coreweave.com or one of its subdomains, or the README of github.com/coreweave/terraform-provider-coreweave. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "coreweave", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html CoreWeave on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![CoreWeave on Anchor Terminal](https://www.anchorterminal.com/badges/coreweave.svg)](https://www.anchorterminal.com/tools/coreweave) ``` Plain link: ```html CoreWeave on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say CoreWeave is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/coreweave-dark.png - Light: https://www.anchorterminal.com/assets/share/coreweave-light.png