Skip to main content
You pay a USD budget for the selected instance. The quote shows the hourly rate and estimated runtime before you pay. Review the final payment page for the amount charged. Successful payment starts provisioning. Purchased runtime begins when the deployment becomes active, not while it is waiting to provision. The ready email includes order and access details, plus a payment receipt link when available.

​
No automatic renewal

A rental ends when its purchased runtime expires. There is no documented self-service add-hours or renewal flow at launch. Do not assume another payment extends an existing machine or preserves its files.

​
Early termination and failures

Terminating early is irreversible and forfeits unused paid runtime; do not assume a prorated refund. Back up first. If provisioning ultimately fails, the backend schedules refund handling. A scheduled refund is not confirmation that money has reached your card. Contact support if payment or refund status is unclear; bank processing can take time.

​
Missing email or duplicate payment concerns

Check junk mail and the deployment status before trying again. Send support your order/deployment ID and payment time, never full card details or credentials. For API checkout retries, reuse the same Idempotency-Key and request body. A new key is a new purchase intent; see API.