CoreWeave vs Koyeb

CoreWeave

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.

Koyeb

H100 at $2.50 and H200 at $3.00 an hour, billed per second. Changelog silent since 27 February 2026 and no CLI release since 12 May 2026.

CoreWeave

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

Koyeb

1. Pass dry_run on service create or update to validate the definition before anything deploys
2. Page service lists with limit and offset and filter by statuses instead of fetching everything
3. Expect the first request after deep sleep to take 1 to 5 seconds and retry once with a timeout
4. Set --min-scale 0 on GPU services so idle instances stop billing
5. Re-check the Mistral transition before building anything long-lived on it