> ## 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. # Get started with CoreWeave > Find your setup path and the right documentation for your CoreWeave workload. 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](#provision-users-for-sunk) before you can connect to Slurm login nodes over SSH. ### Activate your account When CoreWeave approves your organization, the CoreWeave Sales team sends an invitation email. Click **Activate** to access the [Cloud Console](https://console.coreweave.com). The first user invited becomes an administrator by default and can invite others. For more details, see [Activate and sign in to your CoreWeave organization](/security/authn-authz/activate-org). ### Invite users and manage your org Admins invite users from the [Users](https://console.coreweave.com/organization/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)](/security/automated-user-provisioning) with SCIM. This keeps your organization in sync with your identity provider. See the following guides for setup instructions: * [Configure AUP with Okta](/security/automated-user-provisioning/configure-okta) * [Configure AUP with Microsoft Entra](/security/automated-user-provisioning/configure-microsoft-entra) ### IAM and access policies Identity and Access Management (IAM) Access Policies define which users and groups can perform actions on platform services, such as creating and managing CKS clusters, managing IAM users and groups, and viewing billing. 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: * [CoreWeave AI Object Storage](/products/storage/object-storage), which uses organization and bucket access policies. * [CKS clusters](/products/cks), which use Kubernetes RBAC. * [SUNK clusters](/products/sunk), which use [SUNK User Provisioning (SUP)](/products/sunk/manage_sunk/manage_cluster_access/sunk_user_provisioning) rather than IAM Access Policies directly. See [IAM Access Policies](/security/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](/products/sunk/manage_sunk/manage_cluster_access/sunk_user_provisioning) 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](/products/cks/clusters/create)). Once a cluster exists, install [kubectl](https://kubernetes.io/docs/tasks/tools/), then create an API access token and download the kubeconfig file from the [Tokens](https://console.coreweave.com/tokens) page in the Cloud Console. See [Manage API Access Tokens and Kubeconfig Files](/security/authn-authz/manage-api-access-tokens) for setup instructions. ### Helm (CKS) Helm is an admin and infrastructure tool that deploys CoreWeave-provided charts, including Traefik, cert-manager, and container registries. If you're an admin, [install Helm](https://helm.sh/docs/intro/install/) (3.8+). End users running workloads on CKS don't need Helm installed locally. See [CoreWeave Charts](/products/cks/clusters/coreweave-charts/introduction) for the available charts and how to add the repository to Helm. ### AI Object Storage AI Object Storage has an [S3-compatible API](/products/storage/object-storage/reference/object-storage-s3) that you can use with any S3-compatible client, such as the [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html), [s3cmd](https://s3tools.org/download), or [Boto3](https://docs.aws.amazon.com/boto3/latest/guide/quickstart.html#installation). [LOTA](/products/storage/object-storage/improving-performance/about-lota) is an intelligent caching proxy installed on every Node that 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 can succeed. See [About policies](/products/storage/object-storage/auth-access/policies) for more information. * Choose how workloads authenticate: static access keys for simplicity and quick testing, or [Workload Identity Federation](/products/storage/object-storage/auth-access/workload-identity-federation/about) for production workloads that shouldn't rely on long-lived credentials. See [Get started with AI Object Storage](/products/storage/object-storage/get-started-caios) for authentication, policies, and full setup instructions. ### Git and SSH (SUNK) Use Git 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](https://learn.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse) or enable it in **Settings**. See [Connect to the Slurm login node](/products/sunk/access_sunk/connect-to-slurm-login-node) for setup instructions. ### Documentation MCP server The CoreWeave documentation site exposes a Model Context Protocol (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, do the following: 1. Expand the **Copy MCP Server** menu at the top of any documentation page, to the right of the page title: Documentation MCP server menu 2. Copy the MCP server URL to configure tools manually. Alternatively, you can install the MCP server on an IDE or install it locally. You can also copy or view the page content as Markdown, and launch the AI assistant chat window in your browser. ## Run 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](/products/cks/deploy-model) 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](/products/sunk/tutorials/train-on-sunk) for a complete walkthrough covering cluster setup, job submission, and monitoring. ## Security and networking Explore the following recommended functionality as you scale: * **VPCs**: [Virtual Private Clouds](/products/networking/vpc/about-vpcs) isolate clusters and control traffic. Use custom VPCs for multi-cluster communication, peering, or on-premises connectivity. * **Network policies**: [Deploy network policies](/security/tutorials/deploying-network-policies) to enforce Layer 4 and Layer 7 traffic rules at the DPU level. * **Direct Connect**: [Direct Connect](/products/networking/direct-connect/about-direct-connect) provides private, dedicated links to CoreWeave from Equinix or Megaport. * **HPC interconnect**: [GPUDirect RDMA with InfiniBand](/products/networking/hpc-interconnect/about-hpc-interconnect) enables low-latency, high-throughput multi-node training. See [Security](/security) and [Networking](/products/networking) for the full picture. ## Automate your solution CoreWeave exposes REST APIs and infrastructure-as-code options for managing resources programmatically. ### REST APIs CoreWeave provides the following REST APIs: * **CKS API**: Create, list, update, and delete clusters programmatically. See [CKS API Reference](/products/cks/reference/cks-api). * **VPC API**: Manage VPCs through REST. See [VPC API](/products/networking/vpc/vpc-api). * **Object Storage API**: Manage access keys, policies, and organization settings programmatically. See [AI Object Storage API Reference](/products/storage/object-storage/reference/object-storage-api-ref). ### Infrastructure-as-code The [CoreWeave Terraform Provider](/platform/terraform) lets you manage your CoreWeave infrastructure as code, including CKS clusters, VPCs, Object Storage buckets, and Object Storage access policies. Declare your infrastructure in configuration files and apply changes consistently across environments. See [Terraform reference architecture](/platform/reference-architecture) for a complete example. ## For more information Explore these resources to plan and scale your CoreWeave deployment: * **Instances**: [GPU and CPU specifications](/platform/instances/about-instances) help you [choose the right instance](/platform/instances/selecting-an-instance) for your workload. * **Node lifecycle**: See [how instances are validated and maintained](/platform/fleet-management/node-lifecycle), from [Day 1](/platform/fleet-management/node-lifecycle/day1) setup through [Day 2+](/platform/fleet-management/node-lifecycle/day2) operations. * **Regions**: [Regions and availability zones](/platform/regions/about-regions-and-azs) covers global infrastructure and how CoreWeave delivers reliability and connectivity. * **Pricing**: [Instance pricing](https://www.coreweave.com/pricing) provides guidance on costs and how to optimize them for your workload.