Quote
Configuration and price are calculated from the versioned catalog.
Operating model
The service design connects a versioned catalog, account ledger, capacity request, and instance lifecycle. Provisioning and payment confirmation remain separate integrations.
No live inventory, host telemetry, payment custody, operator staffing, or recovery capability is asserted on this page.
Lifecycle
A production adapter must confirm every external action and preserve a stable event history.
Configuration and price are calculated from the versioned catalog.
Funds and capacity are intended to be checked as one operation.
The request waits for an external infrastructure confirmation.
Stop and restart change compute state but do not pause the term.
The account workflow schedules automatic renewal 24 hours before expiry when enabled.
Release ends the reservation and is intended to destroy local data.
Region records
Installed fleet, rentable inventory, and historical capacity should never be treated as the same number.
Facility details are not published.
Open region recordFacility details are not published.
Open region recordFacility details are not published.
Open region recordAccounting records
Deposits, rental charges, renewal charges, withdrawal holds, refunds, and corrections are intended to remain separate records rather than rewriting a stored balance.
Billing FAQExternal systems
Provisioning, chain confirmation, and settlement depend on separate integrations. The interface must not report success before external confirmation.
Service status