Search here first. If you’re stuck, submit a ticket

Sign in to the console and open the relevant order. Check the node ID, SSH address, port, and provided credentials. Connect using a terminal or SSH client; for a graphical desktop, use the VNC details in your order. After logging in, check the machine specs, macOS version, and available disk space before setting up your build environment.

If the connection fails, record the SSH and VNC results separately. When submitting a ticket, include the node ID, time of the failure, and the error shown by your client. Don’t include your password or private key.

Wait for the desktop session to finish loading, then disconnect and reconnect once. Make sure your client is using the VNC address and port from your order, not the SSH port. If SSH works, check whether the machine still responds to commands and whether the graphical session is running properly. Don’t repeatedly reset the machine to troubleshoot a display issue.

If the screen is still black, include your client name, a screenshot, the node ID, and whether SSH works in your ticket. This helps us identify whether the issue is with the display session or the machine connection.

Keep your current connection open. First, append the new public key to the target user’s ~/.ssh/authorized_keys. Check that the directory and file permissions meet SSH requirements. Open another terminal and test a login with the new private key. Remove the old public key only after the test succeeds.

Upload only your public key. Keep the private key on your own device—never send it in a support ticket. If the old key no longer works and you can’t access the machine, submit a ticket with your order number and node ID so our team can check how to restore access.

After signing in to the macOS user account provided with your machine, change the password in System Settings under Users & Groups, or run passwdin that user’s terminal session. Before changing it, make sure you still have a working SSH or VNC connection. Afterward, verify the new password in a fresh session rather than relying on your current logged-in window.

If you can no longer log in, submit a support ticket through the console with your order number, node ID, and the error message. Don’t include your old password.

First, run xcodebuild -version to check the current toolchain. If multiple Xcode installations are available, use xcode-select -s to select the version you need, then check the version again. You can also set DEVELOPER_DIRexplicitly in your CI script to prevent jobs from changing the default version for one another.

If the version you need isn’t installed, check its system requirements and the available disk space first. Then get the installer from an official source. Don’t assume every version is preinstalled on delivery.

Check in this order: whether the certificate has its corresponding private key, whether the provisioning profile matches the bundle identifier, and whether the build job can access the keychain in use. If a manual desktop build succeeds but CI fails, compare the user account, keychain unlock status, and signing parameters in each session.

Certificates, private keys, and keychain files are sensitive. You can attach redacted error logs to a ticket, but don’t upload certificate private keys or full signing passwords.

Check the installed runtimes in Xcode’s platform manager, or run xcrun simctl list devices available to see which devices are available. If you’re missing a required runtime, download a component compatible with your Xcode version. Make sure you have enough disk space before downloading.

In CI, don’t rely on device names alone to identify the target. Specify the runtime version and device model in your build configuration, and check that the target is still available after updating Xcode.

First, check DerivedData, old archives, downloaded Simulator runtimes, and dependency caches. Identify files that can safely be regenerated. Don’t delete certificates, source code, or active build artifacts without a backup.

If your project needs a larger persistent workspace, you can add a +1TB SSD or +2TB SSD when placing your order. Available changes to an existing order depend on the options shown in the console. If you need help, submit a ticket with your order number and disk usage details.

Choose one rental period per order. Your order shows the price and expiry date. XV M4 Runner costs $21.4/day, $57.8/week, $107.1/month, or $291.3/quarter. XV M4 Studio costs $40.7/day, $109.8/week, $203.3/month, or $553/quarter. All prices are in USD.

A monthly price isn’t charged daily. Once you know how long you’ll need the machine, compare the total price for each term. Check add-ons such as extra storage against the same order period.

If you renew the same instance before your current rental ends, you’ll normally continue using the same machine. Check the instance and new expiry date in the console renewal order. If you need a different model or node, don’t treat it as a standard renewal. Submit a ticket to confirm migration options, and back up your data.

Machines that aren’t renewed by expiry are reclaimed and fully reset. Don’t rely on an unpaid renewal as a backup plan.

Follow the payment details, requirements, and payment status shown for your current order in the console. Don’t reuse an address from an old order or assume a fixed number of confirmations. Check that you’re sending USDT-TRC20 on the correct network, and keep the transaction hash. If the transaction is confirmed on-chain but your order hasn’t updated, submit a console support ticket with your order number and transaction hash.

Never share your wallet’s private key or recovery phrase in a support ticket.

Orders are billed in US dollars (USD). Cards are processed by Stripe, which supports Visa, Mastercard, and Amex. Available payment gateways are shown in the console at checkout. Stripe processes your card details; they don’t pass through our servers.

If your card issuer shows a different billing amount or additional fees, check the issuer’s policies. The order amount is the USD amount shown in the console.

If your rental ends without a renewal, the machine is reclaimed and fully reset. All data on the drive is erased, and the system is reinstalled before the machine is assigned again. Your project files won’t be kept as recoverable copies.

Account data and records needed for billing are separate from data on the machine’s drive. To ask about how account information is handled, submit a support ticket through the console.

Commit your source code to a repository you manage. Then export certificates and private keys, signing settings, archives you want to keep, test data, and scripts to storage you control. For large files, use an SSH file transfer tool to copy them in batches, then check file sizes or checksums.

Don’t delete the originals as soon as the copy finishes. Restore a project or build artifact from your backup and verify that it opens or can be rebuilt. Once verified, plan the end of your rental around the order expiry date.

Project files stored on your dedicated physical machine belong to you. We don’t view or analyze them. When troubleshooting, we work from details you choose to share in your ticket, such as the node ID, error messages, and redacted screenshots.

Before sharing screenshots, hide tokens, connection credentials, certificate details, and other sensitive project information. If you need further assistance, tell us in your ticket which diagnostic materials you’re willing to provide.