A dark server rack with copper braided cables, representing energy-focused AI data centers.
Crusoe pairs the compute layer with the power layer, building and operating the data centers its GPUs run in.

Crusoe is a vertically integrated AI cloud that describes itself as “the energy-first AI factory company.” It sources energy, builds and operates hyperscale AI data centers, and rents that capacity as a GPU cloud for training and inference . The problem it targets is the bottleneck behind every large model project: not chips alone, but the power and physical buildings to run them. Crusoe controls the whole stack, from the turbine to the GPU, so it can add capacity without waiting on a landlord or a utility.

The company started in 2018 with patented Digital Flare Mitigation technology, converting wasted natural gas into electricity for computing. In 2025 it divested its bitcoin mining business to focus on AI infrastructure, and it now runs a diversified energy portfolio that includes geothermal and hydro power, gas turbines, and second-life EV batteries.

Where Crusoe sits in the stack

Crusoe operates lower in the stack than a typical model API provider. It owns the energy and buildings, then layers cloud services on top.

Managed AI
Crusoe Managed Inference Intelligence Foundry model marketplace Serve open models like Llama and DeepSeek behind an endpoint
Cloud platform
Crusoe Cloud Managed Kubernetes Managed Slurm AutoClusters Command Center
Compute
NVIDIA GB200 NVL72 NVIDIA HGX B200 NVIDIA H200 / H100 AMD MI355X / MI300X
Facilities
Crusoe Spark modular data centers Crusoe Edge Zones
Energy
Geothermal and hydro Gas turbines Second-life EV batteries

How to access it and typical use

Crusoe sells two things depending on how much you want to manage yourself.

  • Crusoe Cloud gives you raw GPU infrastructure. You rent clusters of NVIDIA or AMD accelerators and run your own training or serving stack on top, with Managed Kubernetes, Managed Slurm, and AutoClusters to schedule the work. This suits teams training or fine-tuning large models who want dense, high-end GPU capacity without buying hardware.
  • Crusoe Managed Inference is a platform service. You call an endpoint and Crusoe serves an open model for you, drawing from its Intelligence Foundry marketplace, which lists models such as Llama, DeepSeek, GLM, Kimi, and Nemotron. This suits teams that want production inference without operating clusters.

Access starts through the Crusoe website: request access, then provision resources through the Crusoe Cloud console and the Command Center operations view. Because Crusoe builds its own sites, capacity is often contracted in advance for larger commitments rather than clicked into existence like a hyperscaler instance.

Step 1 Choose the layer Raw GPU clusters through Crusoe Cloud, or a served endpoint through Managed Inference.
Step 2 Provision capacity Pick GPU type and cluster size, then schedule with Kubernetes or Slurm.
Step 3 Run the workload Train, fine-tune, or serve models on the allocated GPUs.
Step 4 Operate and monitor Track jobs, usage, and health through the Command Center.

How Crusoe compares

Crusoe belongs to the “neocloud” category: specialist GPU clouds that compete with hyperscalers on price and availability of scarce accelerators. Its differentiator is owning the energy and buildings, not renting them.

CrusoeCoreWeaveNebiusLambda
Primary focusEnergy plus GPU cloudGPU cloud at scaleGPU cloud and platformGPU cloud for AI
Owns energy layerYes, energy-firstNoNoNo
Managed inferenceYesLimitedYesYes
GPU vendorsNVIDIA and AMDMainly NVIDIAMainly NVIDIAMainly NVIDIA
Best forPower-constrained scaleLarge NVIDIA fleetsFull AI platformFast GPU access

For the neighboring options, see CoreWeave , Nebius , Lambda Cloud , and the serving-focused Together AI . If you want a fully managed model API instead of infrastructure, Amazon Bedrock sits one layer higher again.

When not to use it

  • You want a plug-and-play model API and nothing else. A managed API like Bedrock or a first-party lab endpoint is faster to adopt than provisioning cloud capacity.
  • You need instant, self-serve elastic scaling for small jobs. Neoclouds shine at reserved, dense GPU capacity, less so at spiky micro-workloads that a hyperscaler spot instance handles cheaply.
  • You are locked into one hyperscaler’s managed services. If your data, IAM, and pipelines live inside AWS, Azure, or Google Cloud, moving GPU workloads to a separate cloud adds integration and egress work.
  • You need a specific region Crusoe does not serve. Because Crusoe builds physical sites, availability follows its footprint rather than a global default.

Further reading

Sources