CoreWeave Cloud UI
Deploy Virtual Servers via the Cloud UI
The CoreWeave Cloud UI is a responsive, Web-based dashboard enabling users to configure, deploy, and manage Virtual Servers.
This guide presumes you have an active CoreWeave Cloud account. Once you have an active account, log in to the Cloud UI dashboard at
https://cloud.coreweave.com.Once signed in to your CoreWeave Cloud account, navigate to the Virtual Servers menu located in the upper left-hand side of the sidebar menu, or click the Deploy Now button under Deploy Virtual Servers in the top-middle of the dashboard - this will redirect you to the Virtual Server hub.
Navigate to the Virtual Server creation page either from the Deploy Now button or using the side navigation
New Virtual Server
🎉
CoreWeave Cloud Virtual Server has more features than the CoreWeave Apps edition, but you can use either one. You may see a selection screen like this when deploying.
These instructions are for CoreWeave Cloud Virtual Server.
The Virtual Server hub is where all existing Virtual Servers are listed. From here, you can manage current Virtual Servers, or create a new one.
To create a new Virtual Server, click the New Virtual Server button.
Deploy a Virtual Server
The Virtual Server hub has several deployment options. Choose the option that best suits your use-case.
A new Virtual Server is the default option. Choose all the parameters from scratch to build a custom-configured machine tailored to your needs.
A clone is a snapshot of an existing Virtual Server, including the PVC containing the OS and all files. Deploying a clone Virtual Server creates an exact duplicate of an existing Virtual Server in its current state.
A template uses an existing Virtual Server as a model. Deploying from a template creates a new Virtual Server with the same configuration as the original, but without the state or a copy of the data.
A custom deployment is a special case.
Compared to a clone which is an exact copy, or a template that uses the same settings but no data, a custom deployment can use custom settings while copying the PVC from another Virtual Server, or load the disk image from a remote HTTP source.
A new Virtual Server is the default option. Choose all the parameters from scratch to build a custom-configured machine tailored to your needs.
The deployment page has two panes: the web UI, and the Custom Resource Definition (CRD) YAML manifest. Changes made in either pane are reflected in both.
While configuration options can be made in either pane, not all options are exposed in the Web UI. For complete control over the Virtual Server configuration, edit the YAML directly. The YAML manifest can be copied from here to use with the CLI, and pasted back to this page in later deployments.
When the web editor has focus, sensitive values such as passwords are obscured with asterisks in the YAML editor. Click the YAML pane to give it focus and reveal the sensitive values, or click the Hide YAML button between the panes to close the YAML.
New Virtual Server deployment page
There are three buttons in the upper-right corner of the web UI pane:
Option buttons
A clone is a snapshot of an existing Virtual Server, including the PVC containing the OS and all files. Deploying a clone Virtual Server creates an exact duplicate of an existing Virtual Server in its current state.
Note
Shut down the existing source server before cloning. The deployment page does not allow cloning a running server.
One way to initiate a clone deployment is to open the New Virtual Server form, as if deploying from scratch. Then, click Load or clone from existing in the upper-right, which opens the Select Template modal.
Select an existing Virtual Server in the drop-down presented. Then toggle the Clone (use resource as source) option to create an exact clone of the selected Virtual Server.
Clone server modal
Another way to deploy a clone is to select Clone from the more menu of an existing server. Or, expand the server details and click Clone.
Deployment options
A template uses an existing Virtual Server as a model. Deploying from a template creates a new Virtual Server with the same configuration as the original, but without the state or a copy of the data.
The steps to deploy as a template are similar to deploying a clone, but choose the Use As Template option instead. In the Select Template modal, leave the Clone option untoggled:
Leave Clone untoggled to create a template
Changing the configuration options before deployment is allowed when using a template. For example, change the Region when deploying from a template to use the same server configuration in a different datacenter.
While this is also possible with cloning, there's less risk of deployment failure when using a template because templates don't copy the source server's files or state.
A custom deployment is a special case. Compared to a clone which is an exact copy, or a template that uses the same settings but no data, a custom deployment can use custom settings while copying the PVC from another Virtual Server, or load the disk image from a remote HTTP source.
To deploy a custom Virtual Server, follow the same steps as deploying a new server from scratch, but select either Custom OS with Remote Source, or Custom OS with PVC in the Operating System section.
Choose a Custom option
Note
The Custom OS with PVC option does not appear unless you have an eligible PVC available.
This option provides complete flexibility. You can supply your own OS image over HTTP in
qcow2, raw and iso formats, optionally compressed with either gz or xz. You can also copy the PVC from existing Virtual Server in CoreWeave Cloud, or prepare a custom PVC image using any other procedure. See Importing Disk Images for more details about these options.Click any of the specification cards to learn more about each configuration option.
Not all Virtual Server configuration options are exposed in the Web UI.
For more fine-grained control over the Virtual Server configuration, use the YAML pane on the right side of the screen.
The YAML editor allows the Custom Resource Definition (CRD) of the Virtual Server to be edited directly, offering a high level of both flexible customization and transparency. The CRD's YAML may also be copied from here for future programmatic deployments using the CLI.
The View/Hide YAML tab is located on the right-hand side of the screen
When you are ready to launch your new Virtual Server, click the Deploy Now button.
Click the new Virtual Server to expand its menu for more information and to see all options.
Additionally featured on the status page is a virtual terminal, allowing immediate access to the Virtual Server once it is in a ready state through a VNC terminal. To open the virtual terminal, click the Terminal button in the Virtual Server's expanded menu, or click the ellipses on the right hand side of its name.
Note
For Virtual Servers running Windows, it may take time to install and upgrade the OS. Additionally, the Web-based terminal is not supported by Virtual Servers utilizing custom EDID.
Clicking the Upgrade button will bring you back to the Hardware Selection page shown above. From there, you can change options such as GPU type, CPU core amounts, root disk size, and so on.
A basic diagnostic log of all actions involving the Virtual Server are recorded in a list, viewed by clicking the Events button.
Note
The events listed under Events are short-lived, so should mostly be used for diagnostic purposes or for tracing the status of the Virtual Server.
Last modified 8d ago