Haizhi Weilai

Procurement / Cloud Compute

Cloud Compute Sourcing

Share your deployment region, workload and rental term. We compare GPU instances and bare-metal options, including storage, networking, costs and rental terms.

Prepare an inquiry email

01 / CLOUD COMPUTE

Compute options

We can compare GPU instances, dedicated or shared configurations, and bare-metal rentals. We review storage and networking alongside compute and consider non-GPU options where they suit the workload.

A bare-metal rental covers use of the server for an agreed term. Check which resources in the quote are dedicated, which are shared, and which need a separate order.

02 / CLOUD COMPUTE

Configuration, capacity, and provisioning

01

Workload

For a validation run, include the task and expected runtime. For ongoing inference, include peak concurrency, latency targets, and when you expect to scale. Break out requirements by location for a multi-region deployment.

02

Configuration

Include the instance type, image, storage, network needs, and preferred region or availability zone. For GPU instances, add the GPU count and memory per card.

03

Provisioning

Before ordering, confirm available capacity and reservation status for the target dates with the provider, along with project account quotas and any setup requirements.

03 / CLOUD COMPUTE

Quote breakdown

ChargeDetails to compare
ComputeInstance configuration, billing unit, and estimated usage. Compare pay-as-you-go and reserved pricing separately.
StorageCharges for disks, snapshots, and backups, including how capacity and retention affect the bill.
NetworkBandwidth or traffic pricing, including charges for public IPs, outbound traffic, and cross-region traffic.
SupportContact channels, coverage, and fees. List any work outside the proposed scope separately.

Check the rental start date, when billing begins, the minimum term, and the terms for capacity changes, cancellation, and renewal. The relevant order sets when a reservation takes effect and how it can be changed or cancelled.

04 / CLOUD COMPUTE

Billing by resource state

StateCharges that may continueResources to handle separatelyResponsibility
RunningCompare compute, disk, and network charges with the quote.List any storage, network, or support items ordered separately.The tenant administrator checks the inventory; the billing party checks the charges.
StoppedCompute charges depend on the stop method. Disks and public IPs may still incur charges.Check resources that are still attached or retained independently.The tenant administrator verifies the instance state; the billing party confirms which charges stopped.
ReleasedStandalone resources or unexpired reservations may still incur charges.Verify the data export, then use the checklist to handle disks, snapshots, public IPs, and any other resources.The tenant administrator checks release records; the billing party confirms remaining charges.

Agree in writing before ordering on who checks charges and who has permission to manage resources.

05 / CLOUD COMPUTE

Tenant handover and exit

At handover, confirm who controls the tenant account, who is responsible for the bill, who has admin access, and how to view usage records. Before exit, assign responsibility for exporting data, checking that copies are usable, revoking access, releasing resources, and reviewing final charges.

If snapshots, backups, or other copies need to be removed, agree on which copies to remove and how to verify removal.

See delivery and acceptance checks

INQUIRIES

Project inquiries

Start with the deployment location, workload and target dates.

Prepare an inquiry email