Help
Cloud Macs
A Cloud Mac runs macOS in a virtual machine on a shared physical Mac. The standard allocation is 4 CPU cores, 8 GiB memory and an 80 GiB logical disk. The account catalog shows the qualified macOS version, region, current monthly price and available capacity before you buy.
Create and connect
Open Machines in an updated app, choose Cloud Mac and sign in. Compute needs its own paid seat or an explicit, time-limited grant. Pro does not provide compute capacity, and Cloud Mac access does not require Pro.
Checkout returns to your account while payment confirmation creates the allocation. Keep the fulfillment ID if interrupted; returning to the account recovers its status. A Mac becomes ready only after the host provisions it and its signed gateway health confirms a working listener and relay connection. The account shows each operation and an ID for support.
Power, health and deletion
Stop preserves your disk and reservation. Start resumes the same disk; restart is available for a running Mac. Stale health can show Unavailable without discarding your allocation or replacing its data. Recovery work waits for verified host inventory and operator decisions.
Delete revokes access immediately and requests permanent host cleanup. The seat stays reserved until cleanup is confirmed. For a paid seat, the deletion control explicitly offers cancellation at the end of the paid period or keeping the seat for another allocation. Cancelling the seat alone keeps existing compute available until its entitlement ends.
Billing and interruptions
Each seat is reserved monthly capacity, including while stopped. Price comes from the configured provider catalog. Payment confirmation is authoritative; the checkout return page cannot grant capacity. If a confirmed purchase cannot be allocated, or its first allocation never becomes ready within the initial fulfillment window, the service records subscription cancellation and refund work and retries provider failures. Contact support with the fulfillment ID if compensation remains pending.
A failed payment has seven days of grace. After grace, access and host execution leases are withdrawn. Disks remain retained for at least 30 days. Renewal restores entitlement to the retained disk; it can then be started again. Retention expiry creates an operator review, with notices before review; it does not automatically delete the disk.
Backups and recovery
Qualified hosts create daily encrypted backups and retain seven verified recovery points. A backup may briefly stop the VM to create a consistent copy. The account displays the last verified backup; a failed backup does not advance that timestamp. This is operator-assisted recovery, with no self-service restore or guaranteed recovery time.
Restoring requires a verified recovery point, access to independently escrowed encryption keys and a qualified destination with capacity. The original allocation must be physically fenced or observed stopped before a new generation is reserved. Old gateway access is revoked, and original disk cleanup remains separately tracked. Host loss, unavailable keys, provider outages or failed qualification can delay recovery. Keep your own copy of important work.
Deleting a Mac schedules backup-object and encryption-key purge within seven days. Each host that could retain a local key requires its own destruction receipt; an unavailable host leaves that receipt pending for operator follow-up. Once cleanup removes the disk or recovery points, restoration may no longer be possible.
Support
The shared service has no published uptime SLA. Provide the machine, operation or fulfillment ID from your account when contacting support. Do not include login tokens, encryption keys or private restore authorization files.