Before you begin
Serverless sandboxes are generally available, and usage is billed. Access is enabled per organization. To request access for your organization, contact support. If your organization uses W&B Dedicated Cloud, follow Use sandboxes with W&B Dedicated Cloud.Run your first sandbox
Choose the credential for the account that owns and is billed for your sandbox. A Forge API key supports serverless placement. A CoreWeave API access token supports serverless and CoreWeave Kubernetes Service (CKS) placement. For account requirements, see Choose and get credentials. Choose a credential tab, then verify the result.- Forge API key
- CoreWeave API access token
Get your Forge API key. If you don’t have an account, sign up through the same link. Then set the key in your terminal. These examples explicitly select W&B authentication:The Forge API key uses the SDK’s existing W&B identifiers:
- Python
- TypeScript
With Run it with Python 3.11 and the sandbox client. The command installs them if needed:
uv installed, save this as hello.py:hello.py
WANDB_API_KEY, AuthStrategy.WANDB, and the TypeScript /wandb entry point.Verify the result
The example prints the following output and stops the sandbox when it finishes:Output
resources to choose its CPU and memory.
For concurrent quotas, rate limits on create requests, and quota errors, see Limits and quotas.
Next steps
Continue with the guide for your workload:- Use your own compute: enable a runner on your cluster and run a sandbox there.
- Sandbox placement and spillover: compare serverless and CKS capacity and configure fallback.
- Run coding agents: connect a coding agent to a sandbox.
- GPU sandboxes: request GPU access and run a GPU workload.
- Python client: execute commands, work with files, and configure sandboxes.