Get started with CoreWeave

Documentation Index

Fetch the complete documentation index at: https://docs.coreweave.com/llms.txt

Use this file to discover all available pages before exploring further.

CoreWeave is a cloud platform purpose-built for AI and high-performance compute. CoreWeave Kubernetes Service (CKS) runs bare-metal clusters on our GPU and CPU fleet, enabling model training and inference at scale. SUNK is CoreWeave’s solution for running Slurm on Kubernetes, providing Slurm-based job scheduling on top of CKS for distributed training workloads. This page orients you to the key concepts, tools, and setup paths, with links to full instructions for each.

​

Account setup

Account activation and user invitation apply to all CoreWeave users. If your team uses SUNK, admins must also complete a separate user provisioning step before users can SSH into Slurm login nodes.

​

Activate your account

When CoreWeave approves your organization, the CoreWeave Sales team sends an invitation email. Click Activate to access the Cloud Console. For more details, see Activate and sign in to your CoreWeave organization.

​

Invite users and manage your org

Admins invite users from the Users page. New users click the invitation link and sign in with the same email used for the invite. To sync users and groups from your IdP (Okta, Microsoft Entra, and others) instead of inviting manually, use Automated User Provisioning (AUP) with SCIM. This keeps your organization in sync with your identity provider. See the following guides for setup instructions:

• Configure AUP with Okta
• Configure AUP with Microsoft Entra

​

IAM and access policies

IAM Access Policies define which users and groups can perform actions on platform services: creating and managing CKS clusters, managing IAM users and groups, viewing billing, and so on. Admins create policies in the Cloud Console and assign roles to principals. The following services use their own separate authorization systems rather than IAM Access Policies:

• AI Object Storage, which uses organization and bucket access policies
• CKS clusters, which use Kubernetes RBAC
• SUNK clusters, which use SUNK User Provisioning (SUP) rather than IAM Access Policies directly

See IAM Access Policies for the full reference.

​

Provision users for SUNK

Users who need access to SUNK require additional provisioning beyond the standard Cloud Console invite:

• An admin must enable SCIM API and SUNK User Provisioning in the Cloud Console.
• Each user must add an SSH public key before they can connect to Slurm login nodes.

See Provision users in SUNK for the full setup, including IdP-based provisioning with AUP and nsscache configuration.

​

Environment setup

The tools you need depend on your path:

• CKS users need kubectl and Helm.
• SUNK end users need Git and SSH.
• AI Object Storage is optional and works with both CKS and SUNK workloads.

​

Kubernetes and kubectl (CKS)

kubectl is the command-line tool for interacting with CKS clusters. To use it, you first need a cluster (see Create a CKS cluster). Once a cluster exists, install kubectl, then create an API access token and download the kubeconfig file from the Tokens page in the Cloud Console. See Manage API Access Tokens and Kubeconfig Files for setup instructions.

​

Helm (CKS)

Helm is an admin and infrastructure tool used to deploy CoreWeave-provided charts, including Traefik, cert-manager, and container registries. If you’re an admin, install Helm (3.8+). End users running workloads on CKS do not need Helm installed locally. See CoreWeave Charts for the available charts and how to add the repository to Helm.

​

AI Object Storage

AI Object Storage has an S3-compatible API that can be used with any S3-compatible client, such as the AWS CLI, s3cmd, or Boto3. LOTA is an intelligent caching proxy installed on every Node that significantly improves data transfer rates for training and inference workloads. When running workloads inside a CoreWeave cluster, use the LOTA endpoint (http://cwlota.com) instead of the primary endpoint (https://cwobject.com). Before creating buckets and objects, admins must configure access policies and authentication:

• Create at least one organization access policy before any S3-compatible request will succeed. See About policies for more information.
• Choose how workloads authenticate: static access keys for simplicity and quick testing, or Workload Identity Federation for production workloads that should not rely on long-lived credentials.

See Get started with AI Object Storage for authentication, policies, and full setup instructions.

​

Git and SSH (SUNK)

Git is used to clone training code and job scripts onto the login node or shared storage. SUNK end users connect to Slurm login nodes over SSH. SSH is typically pre-installed on macOS and Linux; on Windows, use OpenSSH or enable it in Settings. See Connect to the Slurm login node for setup instructions.

​

Documentation MCP server

The CoreWeave documentation site exposes an MCP server endpoint that lets AI coding assistants query the docs directly in your development environment. (This is a separate control from the Ask AI button at the top of the page.) To connect your assistant:

• Expand the Copy page menu at the top of any documentation page, to the right of the page title:
• Select an option such as Connect to Cursor or Connect to VS Code. Alternatively, copy the MCP server URL from the same menu to configure other tools manually.

​

Running workloads

Choose your path based on your use case.

​

Inference

Deploy a model for inference on CKS. See Deploy an open-source LLM on CKS for a complete walkthrough covering cluster setup and Open WebUI.

​

Training

Run multi-node, multi-GPU distributed training with Slurm on SUNK. See Train on SUNK for a complete walkthrough covering cluster setup, job submission, and monitoring.

​

Security and networking

Recommended functionality to explore as you scale:

• VPCs: Virtual Private Clouds isolate clusters and control traffic. Use custom VPCs for multi-cluster communication, peering, or on-premises connectivity.
• Network policies: Deploy network policies to enforce Layer 4 and Layer 7 traffic rules at the DPU level.
• Direct Connect: Direct Connect provides private, dedicated links to CoreWeave from Equinix or Megaport.
• HPC interconnect: GPUDirect RDMA with InfiniBand enables low-latency, high-throughput multi-node training.

See Security and Networking for the full picture.

​

Automate your solution

CoreWeave exposes REST APIs and infrastructure-as-code options for managing resources programmatically.

​

REST APIs

• CKS API: Create, list, update, and delete clusters programmatically. See CKS API Reference.
• VPC API: Manage VPCs through REST. See VPC API.
• Object Storage API: Manage access keys, policies, and organization settings programmatically. See AI Object Storage API Reference.

​

Infrastructure-as-code

The CoreWeave Terraform Provider lets you manage your CoreWeave infrastructure as code, including CKS clusters, VPCs, Object Storage buckets, access policies, and more. Declare your infrastructure in configuration files and apply changes consistently across environments. See Terraform reference architecture for a complete example.

​

For more information

• Instances: GPU and CPU specifications help you choose the right instance for your workload.
• Node lifecycle: See how instances are validated and maintained, from Day 1 setup through Day 2+ operations.
• Regions: Regions and availability zones covers global infrastructure and how CoreWeave delivers reliability and connectivity.
• Pricing: Instance pricing provides guidance on costs and how to optimize them for your workload.