Overview
Crusoe Cloud is currently in private beta. If you do not currently have access, please request access to continue.
Crusoe Cloud provides a high performance, carbon negative cloud platform with the latest hardware.
VM specifications
GPU-enabled VMs
Customers can create GPU-enabled VMs with the following specs:
| Type | vCPU | GPU | Memory | Disk | VPC Network | InfiniBand Network | Availablilty |
|---|---|---|---|---|---|---|---|
a40.1x | 6-core Intel Xeon (Ice Lake) | 1x NVIDIA A40 48GB PCIe | 60GB | 1x 960GB NVMe | 25 Gbps | N/A | Now |
a40.2x | 12-core Intel Xeon (Ice Lake) | 2x NVIDIA A40 48GB PCIe | 120GB | 2x 960GB NVMe | 50 Gbps | N/A | Now |
a40.4x | 24-core Intel Xeon (Ice Lake) | 4x NVIDIA A40 48GB PCIe | 240GB | 4x 960GB NVMe | 100 Gbps | N/A | Now |
a40.8x | 48-core Intel Xeon (Ice Lake) | 8x NVIDIA A40 48GB PCIe | 480GB | 8x 960GB NVMe | 200 Gbps | N/A | Now |
a100.1x | 12-core Intel Xeon (Ice Lake) | 1x NVIDIA A100 40GB PCIe | 120GB | 1x 960GB NVMe | 25 Gbps | N/A | Now |
a100.2x | 24-core Intel Xeon (Ice Lake) | 2x NVIDIA A100 40GB PCIe | 240GB | 2x 960GB NVMe | 50 Gbps | N/A | Now |
a100.4x | 48-core Intel Xeon (Ice Lake) | 4x NVIDIA A100 40GB PCIe | 480GB | 4x 960GB NVMe | 100 Gbps | N/A | Now |
a100.8x | 96-core Intel Xeon (Ice Lake) | 8x NVIDIA A100 40GB PCIe | 960GB | 8x 960GB NVMe | 200 Gbps | N/A | Now |
a100-80gb.1x | 12-core Intel Xeon (Ice Lake) | 1x NVIDIA A100 80GB PCIe | 120GB | 1x 960GB NVMe | 25 Gbps | N/A | Now |
a100-80gb.2x | 24-core Intel Xeon (Ice Lake) | 2x NVIDIA A100 80GB PCIe | 240GB | 2x 960GB NVMe | 50 Gbps | N/A | Now |
a100-80gb.4x | 48-core Intel Xeon (Ice Lake) | 4x NVIDIA A100 80GB PCIe | 480GB | 4x 960GB NVMe | 100 Gbps | N/A | Now |
a100-80gb.8x | 96-core Intel Xeon (Ice Lake) | 8x NVIDIA A100 80GB PCIe | 960GB | 8x 960GB NVMe | 200 Gbps | N/A | Now |
a100-80gb-sxm-ib.8x | 96-core Intel Xeon (Ice Lake) | 8x NVIDIA A100 80GB SXM4 | 960GB | 8x 960GB NVMe | 200 Gbps | 1600 Gbps | Now |
h100-80gb-sxm-ib.8x | 176-core Intel Xeon (Sapphire Rapids) | 8x NVIDIA H100 80GB SXM5 | 960GB | 8x 960GB NVMe | 200 Gbps | 3200 Gbps | Now |
l40s-48gb.1x | 8-core AMD EPYC (Genoa) | 1x NVIDIA L40S 48GB PCIe | 147GB | N/A | 20 Gbps | N/A | Now |
l40s-48gb.2x | 16-core AMD EPYC (Genoa) | 2x NVIDIA L40S 48GB PCIe | 294GB | N/A | 40 Gbps | N/A | Now |
l40s-48gb.4x | 32-core AMD EPYC (Genoa) | 4x NVIDIA L40S 48GB PCIe | 588GB | N/A | 80 Gbps | N/A | Now |
l40s-48gb.8x | 64-core AMD EPYC (Genoa) | 8x NVIDIA L40S 48GB PCIe | 1176GB | N/A | 160 Gbps | N/A | Now |
l40s-48gb.10x | 80-core AMD EPYC (Genoa) | 10x NVIDIA L40S 48GB PCIe | 1470GB | N/A | 200 Gbps | N/A | Now |
CPU VMs
Crusoe Cloud offers two CPU-only instance types: c1a and s1a. c1a instances are "general purpose" and intended to be used for control planes, web serving, and other lightweight compute. s1a instances are "storage specific" and intended for running high performance file systems like Lustre or ceph, or object stores like minio.
Customers can create c1a VMs with the following specs:
| Type | vCPU | Memory | Disk | VPC Network | Block Storage Network | Availablilty |
|---|---|---|---|---|---|---|
c1a.2x | 2-core AMD (Genoa) | 8GB | N/A | 1 Gbps | 256 Mbps | Now |
c1a.4x | 4-core AMD (Genoa) | 16GB | N/A | 2 Gbps | 512 Mbps | Now |
c1a.8x | 8-core AMD (Genoa) | 32GB | N/A | 5 Gbps | 1 Gbps | Now |
c1a.16x | 16-core AMD (Genoa) | 64GB | N/A | 10 Gbps | 2 Gbps | Now |
c1a.32x | 32-core AMD (Genoa) | 128GB | N/A | 20 Gbps | 5 Gbps | Now |
c1a.64x | 64-core AMD (Genoa) | 256GB | N/A | 35 Gbps | 10 Gbps | Now |
c1a.128x | 128-core AMD (Genoa) | 512GB | N/A | 70 Gbps | 20 Gbps | Now |
c1a.176x | 176-core AMD (Genoa) | 704GB | N/A | 100 Gbps | 25 Gbps | Now |
Customers can create s1a VMs with the following specs:
| Type | vCPU | Memory | Disk | VPC Network | Block Storage Network | Availablilty |
|---|---|---|---|---|---|---|
s1a.20x | 20-core AMD (Genoa) | 176GB | 1x 12.8TB NVMe | 25 Gbps | up to 25 Gbps | Now |
s1a.40x | 40-core AMD (Genoa) | 352GB | 2x 12.8TB NVMe | 50 Gbps | up to 50 Gbps | Now |
s1a.60x | 60-core AMD (Genoa) | 528GB | 3x 12.8TB NVMe | 75 Gbps | up to 75 Gbps | Now |
s1a.80x | 80-core AMD (Genoa) | 704GB | 4x 12.8TB NVMe | 100 Gbps | up to 100 Gbps | Now |
s1a.120x | 120-core AMD (Genoa) | 1056GB | 6x 12.8TB NVMe | 150 Gbps | up to 150 Gbps | Coming Soon |
s1a.160x | 160-core AMD (Genoa) | 1408GB | 8x 12.8TB NVMe | 200 Gbps | up to 200 Gbps | Coming Soon |
VM lifecycle
VMs transition through the following states:
| State | Description |
|---|---|
Creating | The VM is being created. This can take up to a minute. After the VM has been created, it will transition to the Stopped state |
Starting | The VM is being started. Once it has started, it will transition to Running. |
Running | The VM is running and accessible. You can now SSH into it and run your desired software. The VM will continue to run until you stop it. |
Stopping | The VM is being shut down, and no more customer work will be performed. Once it has shut down, it will transition to Stopped. |
Stopped | The VM is stopped and inaccessible. You must manually start it to change the state. Stopped VMs aren't billed for hourly compute charges. |
VM billing
Crusoe Cloud bills for VM usage in two separate ways:
- On-demand
- Instance commitments
On-demand usage provides developers the most flexibility. VMs are charged for the hour (or fraction of an hour, down to the second) that their machine is in the running state. This includes time that the VM is spent running Lifecycle Scripts on startup or shutdown. Stopped VMs are not charged for on-demand usage.
Instance commitments offer discounts in exchange for sustained usage. These VMs are billed for the entire duration of the commitment, regardless of their state. Learn more about Managing instance Commitments.
A VM may only be billed via one of these mechanisms at a time, but different VMs in the same organization may be billed differently.
Quotas
Crusoe Cloud aims to provide a consistent, performant experience for all customers. To that end, each VM is subject to network throughput constraints (currently 1Gbps per VM) as well as disk IOPS constraints.
If you need higher quotas, please contact support and let us know why you need to raise your limits.