A defined resource budget
Each plan describes memory in GB, storage in GB, and CPU as a vCPU equivalent. CPU allocation is illustrative until the underlying scheduling and quota model is confirmed.
Leave room for the unexpected
A build, a traffic spike, or a database import can consume more resources than steady-state traffic. Choose a plan with headroom and review historical usage rather than a single snapshot.
Make your next step a clear one.
Read the quickstartExplore the handbook or compare the sample plans.