Dedicated CPU
Builds, tests and local workloads run on the Mac mini assigned to you. Other customers' workloads won't compete for its processor.
For continuous build workloads
Security for your cloud Mac
Dedicated means hardware-level isolation
Each Mac mini is assigned to a single customer. You get a dedicated physical Mac, not a virtual machine, with its CPU, unified memory and SSD reserved for your use.
Device allocation · at a glance
1 : 1
Allocation
One complete Mac mini
Not a virtual machine sharing compute resources.
During your rental
One customer per device
You manage the projects, toolchains and settings on your device.
Provisioning and release
Reinstall and erase
The system is reinstalled before delivery. After release, the disk is erased and the system is reinstalled.
Hardware isolation
You rent a device, not a resource quota
Dedicated hardware prevents resources from being shared between customers. The three resources below come with the same device and are not overcommitted to other customers.
Dedicated unified memory
Xcode, simulators and MLX workloads use the unified memory included with your selected model. Capacity depends on the tier you choose at checkout and isn't shared with other customers.
Capacity depends on your modelDedicated device storage
Repositories, build artifacts and development tools are stored on your rented device's SSD. The system is reinstalled before delivery; see the data lifecycle below for what happens after your rental ends.
Keep your own backups of important dataHardware isolation doesn't replace account security. When your rental begins, change the initial credentials, configure SSH keys and manage access to the device according to your project's needs.
Data lifecycle
Clear boundaries from delivery to release
We don't create or retain images of your business data. Before releasing the device, back up your repositories, certificates, build caches and other work files.
01
Before delivery
The system is reinstalled before the device is delivered. Once you receive your connection credentials, you can verify the system version and install the tools your project needs.
02
During your rental
You manage the business data on the device. Keep separate backups of repositories, signing materials and files that can't be regenerated. Don't rely on a single rented device as your only copy.
03
After device release
The disk is erased and the system is reinstalled. Data on the original device can't be recovered after release, so export any files you need before confirming the release in the console.
Network and access
Lock down access, then open up your workflow
SSH and VNC screen sharing are the default access methods. After delivery, you can adjust the macOS firewall rules for your services. Before making a service publicly accessible, check its listening address and port range.
SSH: day-to-day access
Verify the host fingerprint on your first connection, switch to key-based authentication and store your private key securely. Use separate accounts or credentials for automation instead of sharing login details.
Use key-based authenticationVNC: graphical access
Use screen sharing when you need to work in Xcode or inspect a simulator. End the session when you're done, and don't store VNC credentials in repositories or CI logs.
Keep credentials separate from codeConsole: account access
Console accounts support two-factor authentication. Even with it enabled, use a strong, unique password and regularly review activity in your account and support tickets.
Secure your account and device separately
Operational access
A dedicated device means controlled operational access
You handle day-to-day project work. Operations staff access a device only when authorized through a support ticket or when necessary to address a hardware fault. Relevant actions are logged.
| Scenario | Access boundary | What you should do |
|---|---|---|
| General setup and software issues | We provide troubleshooting steps through a support ticket wherever possible; routine administration isn't a reason to access your device. | Include a brief error summary, system version and steps to reproduce. Remove keys and tokens from logs first. |
| Device operation requiring assistance | After you confirm the authorized scope through a support ticket, we work only within the limits needed to resolve the issue and log our actions. | Specify what assistance you authorize. Once the issue is resolved, review and rotate any temporary credentials you shared. |
| Hardware fault | We access the device only as needed to diagnose the fault and restore service, and record the relevant actions. | Keep external backups of your business files and track progress through a support ticket in the console. |
When submitting a support ticket, describe the issue. Don't send private keys, full payment credentials or business data that isn't needed for troubleshooting.
Service availability
Availability targets and credits are separate
All locations operate 365 days a year. The figure below is a monthly service target, not a measured result for a completed month.
Monthly availability target
99.9%
Refer to the console for actual records and location-specific incidents.
Availability records for the past 90 days
Review records across three consecutive 30-day periods. The target isn't presented here as historical uptime.
01—30days
31—60days
61—90days
If monthly availability falls below 99.9%, compensation is credited to your account based on the duration of the outage. Submit a request through a console support ticket within 7 days after the month ends, and include the affected instance and time period.
Payment security
Payment details stay separate from device access
All plans are billed in US dollars. Available payment gateways are determined by the backend response at checkout. Only the following two payment methods are publicly supported.
Visa / Mastercard / Amex
Card payments are processed by Stripe. ZSHMac doesn't store full card numbers. Billing records are used to confirm transactions and resolve payment issues.
Billed in US dollarsUSDT-TRC20
Transfers must use the TRC20 network. Payment is confirmed when it arrives on-chain. Before sending, check the amount and recipient details shown at checkout.
Prices shown in US dollars
Responsible disclosure
Found a security issue? Report it privately
Email support@zshmac.com with the affected feature, steps to reproduce, and the expected and actual results. If you attach logs, remove personal information, keys and payment credentials first.
We'll acknowledge your report during business days and follow up in the same email thread. Until we've verified and addressed the issue, please don't publish details that could be used to reproduce it, or access accounts or devices that aren't yours.
Next step
Review the isolation details, then choose your Mac
Compare the three model tiers by memory, storage and billing period. Choose a location when you place your order. Check the console for real-time availability.