Workload library
Start with what the server needs to accomplish.
A useful server decision begins with workload behavior—not a product label. These guides connect common projects to the compute model, location, recovery, and management questions that matter.
Which cloud server should I choose?
Choose Shared CPU for general and variable workloads, Dedicated CPU for sustained or latency-sensitive compute, GPU for supported accelerated work, and Bare Metal when physical isolation or intensive hardware use matters. Then size memory, storage, and location for the application’s actual behavior.
Start with Shared CPU; move to Dedicated CPU for sustained load.
Web hosting
Keep websites responsive as traffic and background work grow.
Explore this use caseShared High Performance or Dedicated CPU, depending on sustained load.
API hosting
Give applications a stable endpoint close to users and connected systems.
Explore this use caseShared Regular for general work; High Frequency for build-heavy workflows.
Development environments
Create a repeatable workspace without tying the project to one machine.
Explore this use caseDedicated General Purpose, Memory Optimized, or Storage Optimized.
Self-managed databases
Match CPU and memory to the workload instead of choosing by label alone.
Explore this use caseCloud GPU for flexible deployment; Bare Metal GPU for intensive isolated work.
AI inference and accelerated compute
Run accelerated workloads without purchasing and housing dedicated hardware.
Explore this use case