Close your account and export data

Export data before requesting destructive cleanup. Account closure does not make an unchecked export complete or waive payment, refund or legal-preservation obligations.

Export and verify

Download important files with cec cp, SSH/SCP or rsync to storage outside this server. Check file sizes and application-level integrity on the destination. A snapshot or private image on the same server is not an independent backup. Export source, configuration and application data; keep credentials in your own secret store rather than ordinary archives.

Remove resources

Stop workloads and remove computers, their snapshots and any independent private images you no longer need. Retain accepted deletion operation IDs and poll them; an accepted request is not proof of completed destruction. Revoke previews, shares, hooks, program credentials and API keys. If a destructive request returns 409 invalid_state because of preservation, it has not been accepted and does not itself change existing billing state.

Settle money and close

Request eligible unused paid credit through the console's refund process; there is no public refund endpoint and we send the payout. Approved-pending liabilities are already excluded from spendable funds. An uncertain payout must be reconciled before retry/cancellation. Preserve the relevant receipt and ledger records for your own accounting. Then request account closure through the console/support process. Closure does not promise immediate erasure of retained operational or legal records.

Dory is in development; these pages describe the planned service and may change. Questions: support@computeengines.com.