Where to manage billing
Use the following table to find where each billing task belongs:What each billing system covers
The following list describes what each billing system covers:- CoreWeave Infrastructure bills for Cloud Console resources: CKS compute, capacity plans, Object Storage, and network usage. Review those charges in the Cloud Console.
- CoreWeave Forge bills for the Forge organization plan and the Forge usage categories shown in billing settings. Those categories can include Weights & Biases storage and tracked hours, Weave, Serverless Inference, Training, ARIA, and Sandboxes when the usage is billed to the Forge organization.
Sandboxes
Serverless Sandboxes accept two credentials. Which account the sandbox belongs to and bills to depends on the credential you present:
For details, see Choose a credential.
Inference
Inference billing depends on the deployment option:
For details, see Inference pricing and Dedicated Inference billing.
Manage billing across both platforms
If your organization uses both platforms, review billing separately in each one. CoreWeave Infrastructure and Forge don’t share invoices, payment methods, usage alerts, or billing permissions.- Permissions. CoreWeave uses the Billing Viewer IAM role and related legacy groups. Forge uses organization admin and billing admin roles inside Forge. Holding one role doesn’t grant the other.
- Usage and alerts. CoreWeave billing insights cover infrastructure usage. Forge usage and spending alerts cover Forge plan categories. Configure and review each set of alerts in its own system.
- Payment methods. Add and update payment methods in each platform’s billing page. A payment method on file for Forge doesn’t apply to CoreWeave Infrastructure, and vice versa.
- Invoices. A Forge invoice doesn’t include CoreWeave Infrastructure usage, and a CoreWeave Infrastructure invoice doesn’t include Forge plan charges. Reconcile spend by checking both billing pages when you use both platforms.
Invoice separation, payment methods, usage alerts, and billing permissions are subject to change.
Multi-tenant Forge deployments
The guidance on this page applies to multi-tenant Forge. W&B Dedicated Cloud and W&B Self-Managed deployments keep their existing billing configuration. See Deployment options.Related resources
The following pages cover related billing and access topics:- Billing: Manage CoreWeave Infrastructure usage and costs in the Cloud Console.
- Forge billing settings: Review the Forge plan, usage, alerts, payment methods, and invoices.
- Forge and CoreWeave identity: Understand how the two identity systems relate and where each administrative task belongs.
- Get started with CoreWeave sandboxes: Choose the credential that determines which account a serverless sandbox bills to.
- What moved in CoreWeave Forge: Find projects, settings, and account locations in Forge if you already use Weights & Biases.