Questions? Start here.

It’s not a virtual machine. Desk M4 is a physical Mac mini dedicated to you, with an M4 chip, 16GB of memory, and a 256GB SSD. During your rental, the machine isn’t time-shared with other users, and its memory and storage aren’t split into tenant allocations.

You get full access to both the macOS graphical interface and the command line. Use it as a remote development environment, build machine, or self-hosted CI runner. Plan parallel workloads around the machine’s actual memory, storage, and project requirements.

Start with compatibility—not simply the newest versions. macOS must support this M4 machine, and each Xcode release has its own system requirements. For older projects, check that the SDKs, dependencies, and build scripts support Apple Silicon.

If your project requires specific versions, send support the macOS, Xcode, and target SDK versions before ordering. Once your machine is ready, check the installed toolchain with xcodebuild -version and xcode-select -p. Leave enough disk space if you need multiple Xcode versions.

The development environment is set up for administrator-level use, with elevated commands run through sudo. Your login name and connection details are provided in the console. An administrator account does not mean that direct remote root login is enabled by default.

A standard login session is enough for everyday builds. Don’t run processes with elevated privileges long-term just to run a CI runner. Before changing SSH, firewall, or disk settings, keep your current connection available and make sure you have a way to recover.

The Desk M4 base configuration is M4 / 16GB / 256GB SSD. Pricing is $21.7 per day, $58.6 per week, $108.6 per month, or $295.4 per quarter. All prices are in USD. These are four billing terms for the same machine, not four different performance configurations.

Choose daily billing for a short troubleshooting session, weekly for a defined sprint, or compare monthly and quarterly billing for a long-running CI workload. A quarterly term covers three months and works out to about $98.47 per month. Extra SSD storage and Thunderbolt 5 interconnects are billed separately. See the full pricing.

The base price is the same across all six locations: Singapore, Tokyo, Seoul, Hong Kong, the eastern United States, and the western United States. You don’t have to choose a location farther from your team just to get a lower base rental price.

Compare your team’s network routes, code and artifact transfer paths, and remote desktop responsiveness. Check current availability in the console when you place your order.

Don’t count on being able to access the machine as storage after your rental ends. Check the expiry time and instructions shown on your order in the console. Before then, renew or move your projects, signing materials, build artifacts, and any important logs off the machine.

When the rental ends, the service is terminated and the data is erased. We don’t promise an additional free storage period. If your work can’t be interrupted, check your renewal status in the console ahead of time—don’t wait until your SSH connection drops.

Available add-ons include a +1TB SSD, a +2TB SSD, and a Thunderbolt 5 interconnect billed per machine. The +1TB SSD costs $11.4/month, the +2TB SSD costs $22.8/month, and the Thunderbolt 5 interconnect costs $6.4/month per machine. See the full pricing list for other terms.

To confirm whether an add-on can be applied mid-term, when it would take effect, and how it would be billed, check your order or submit a support ticket through the console. Don’t assume you’ll pay only for the remaining days or that your existing directories will be moved automatically. Confirm the plan, then back up your data before changing paths.

Use SSH to install dependencies, sync files, run xcodebuild or fastlane, and inspect logs. SSH generally needs less bandwidth and works well in automation scripts.

Use VNC remote desktop when you need Xcode, the Simulator, or system settings. We recommend connecting through an SSH tunnel rather than exposing the remote desktop port to any source. See the getting started guide for first-time setup and tunnel instructions. Find your connection details in the console after signing in.

Latency depends on your location, ISP, network route, and time of day, so there’s no single figure that applies to everyone. Geographic distance can help narrow down your options, but it doesn’t tell you your actual round-trip time.

For remote desktop, look at responsiveness and jitter. For CI, pay more attention to dependency downloads and artifact uploads. Test these routes using your team’s actual network before choosing a location. A single ping isn’t a guarantee of consistent performance. If you need help comparing options, provide your local network type and test results.

You can point an A record for a domain you manage to the public IPv4 address provided in the console, then connect over SSH using that domain. A DNS record won’t configure server ports, firewall rules, or application certificates, and it won’t improve your network route.

After a reinstall or reprovisioning, verify the current IP address and SSH host key fingerprint. If your domain still points to the old address, update the DNS record. If the fingerprint changes, verify the machine details rather than skipping the check.

When your rental ends, the base disk and any extra SSD are handled and erased as part of service termination. Check your order instructions and confirm the details with support. Don’t treat any timeframe that hasn’t been explicitly agreed as a data-retention commitment.

To confirm when data for a specific order will be erased, submit a support ticket through the console before the rental ends. Once data has been erased, renewing won’t restore it. The safest approach is always to move essential files off the machine and verify them before ending your rental.

Don’t assume that one-click virtual machine snapshots are available on a physical Mac. Whole-machine snapshots and automatic platform backups aren’t included as standard features. If your workflow depends on snapshots, confirm the requirements with support first.

You can export files yourself over SSH, with rsync, or through your existing backup workflow. Store backups somewhere outside the machine, then check the file count, checksums, and recovery steps. An extra SSD is still part of the same rental environment and is not a substitute for an independent backup.

At a minimum, check for uncommitted code, signing certificates and private keys, provisioning profiles, environment settings, release builds, dSYM files, experiment results, and assets you can’t download again. A Git repository alone usually won’t cover all of these.

Encrypt sensitive materials and verify that you can read your backup somewhere else. Before you leave the workstation, revoke any CI runner registrations, deployment keys, and access tokens you no longer need. Never paste private keys, passwords, or full payment credentials into public emails or logs.

We accept USDT-TRC20, as well as Visa / Mastercard / Amex through Stripe. All orders are charged in USD. Available payment gateways are determined by the response from the backend.

Before paying, check the machine, location, term, add-ons, and total due. For USDT, verify the network and payment details. For card payments, complete any verification steps shown on the payment page. Don’t rely on the browser’s return page alone to confirm that a payment succeeded.

The required confirmations and crediting conditions depend on the payment page and the gateway’s live response. We don’t publish a fixed confirmation count here. A transfer showing as sent in your wallet doesn’t mean the order has been credited.

If the transfer is complete but the order still shows as unpaid, keep the transaction hash, order number, amount, and network details, then submit a ticket through the console. Don’t pay again just because the status hasn’t updated, and never share your wallet’s recovery phrase or private key.

Check the payment status and service status separately in the console; they’re different steps. A pending transaction on your card statement doesn’t necessarily mean the charge has been finalized.

If the statuses don’t match, submit your order number, payment time, amount, and a redacted payment record. Don’t send your full card number or security code. Support will check the order and gateway records. Until the issue is resolved, we recommend not placing and paying for another order with the same configuration.

Refund requests are reviewed under the Terms of Service and against the status of the specific order. Ending a rental early doesn’t automatically qualify for a refund based on the remaining days. The service delivery, usage, payment status, and reason for the request all need to be checked against the order.

If you selected the wrong option, submit a support ticket through the console as soon as possible, including your order number and what you need changed. Eligibility, handling, and timing depend on the review. We don’t promise immediate payment or a fixed refund timeline.