Marketplace · IaaS
Infrastructure as a Service on VirtEngine
Choose infrastructure. Form a lease. Operate it through the provider's control plane. Settle from verified usage.
Provider supplies
Tenant receives
Catalogue
Common IaaS listing types
Three illustrative examples. Example providers and prices only — not live availability.
IaaS
Illustrative exampleGeneral Purpose VM
Example Provider
Example region
- 4 vCPU
- 16 GB RAM
- 200 GB NVMe
$0.06 / vCPU-hour
IaaS
Illustrative exampleGPU Node
Example Provider
Example region
- 1 × H100
- 24 vCPU
- 192 GB RAM
- NVMe scratch
$1.29 / GPU-hour
IaaS
Illustrative examplePrivate Cloud Tenant
Example Provider
Example region
- Dedicated quota
- Managed control plane
- Network isolation
Reserved plan
More examples
- Bare Metal Node — 64 cores, 512 GB RAM
- Block Storage — SSD-backed snapshots
- Object Storage — S3-compatible versioning
Variation
What varies between providers
Two listings can look similar and differ on every dimension that matters to a workload.
| Attribute | What it changes |
|---|---|
| Region | placement, residency and latency differ per listing |
| CPU / GPU | architecture, generation and core count |
| Memory / storage | capacity, storage class and IOPS tier |
| Network | bandwidth, private links and egress treatment |
| Attestation | confidential capability where the provider offers it |
| Audits / benchmarks | auditor-signed attributes and measured performance |
| Pricing | published plan, metered components or reserved term |
| Support | the response tier attached to the plan |
Check the listing, not the category. The card and the plan are where these differences are visible before you order. Evidence like audits, benchmarks and attestation travels with the provider — see provider participation.
Fulfilment
How a lease becomes a machine
- 01 Lease
- 02 Provider daemon
- 03 Waldur / provider API
- 04 Backend
- 05 VM · network · storage
Lease → daemon → Waldur/backend → resource. Consensus records the agreement; the provider's control plane creates the resource.
Go deeper: Waldur integration for the control-plane boundary, listing anatomy for the fields behind each card, and IaaS vs PaaS vs SaaS for where the responsibility line moves.
Continue