From connecting to a dedicated physical Mac mini to building, managing your rental, and troubleshooting issues. Search this page by command or keyword to find the relevant section.
Once setup is complete, check the host address, username, and connection options in your instance details in the console. Don’t treat example variables as real credentials: set them to the values provided for your instance before running commands.
Create a key pair on your computer and add the public key in the console. Keep the private key on your own device. After your instance is ready and the key is linked, connect using the address and username shown in the instance details.
ssh-keygen -t ed25519
ssh -i ~/.ssh/id_ed25519 "$USER@$HOST"USER and HOST are environment variables that you must set locally. Verify the host fingerprint on first connection; never skip this check.
To use Xcode, the Simulator, or system settings, connect to the remote desktop using the access method shown in your instance details. Check the instance status first, then verify the display address and access credentials.
If the display is noticeably laggy, lower the resolution or color depth in your client and check that your local network is stable. Never put VNC credentials in build logs or share them with your SSH private key.
Check the instance details in the console for the ports actually open; don’t assume every instance uses the same ports. If SSH times out, first check whether your local network blocks outbound connections, then verify the host address, port, and instance status. Before changing firewall rules, keep one working management connection open so you don’t lock yourself out.
Before running command-line builds on a dedicated physical Mac, make sure the Xcode version matches your project’s requirements. For team CI, pin the sources of your project, Scheme, and signing assets so a successful build doesn’t depend on one-off desktop steps.
List the Xcode installations on the machine, then select the version your project requires. After switching, check the command-line tools path and version again. Use the paths below only if the relevant version is installed.
ls /Applications | grep Xcode
sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
xcode-select -p
xcodebuild -versionFrom your project directory, list the available Schemes and confirm the build target before running a Release build. If your team uses fastlane, keep the lane configuration in version control and check certificates and environment variables before running it.
xcodebuild -list
xcodebuild -scheme App -configuration Release build
bundle exec fastlane gymApp Replace with a Scheme that exists in your project;gym requires a matching fastlane configuration in your project.
Give the system account that runs jobs only the permissions it needs, restrict its working directory, and never commit SSH private keys or signing assets to your repository.
Generate the required registration details in your GitHub Actions or GitLab project settings, then follow the platform’s current installation instructions to register the runner on your Mac.
Start with a small job that outputs sw_vers and xcodebuild -version to confirm it runs on the right machine before adding your full build.
If this is your first time using a delivered instance, start with thequick start guideto connect and run your first build.
These terms distinguish the device you rent, how you connect to it, and how billing works. When choosing a plan, start with your workload, then choose a rental period.
Choose a model, node, rental period, and add-ons when you place your order, then pay the full amount for the selected period. Use the delivery and expiry times shown in the console; don’t estimate your available time from the payment time.
Before paying, confirm the model, node, and daily, weekly, monthly, or quarterly period you selected. Availability is based on the latest information returned by the console.
After delivery, check your rental record and expiry details in the console. Reminders can help you plan, but they don’t replace your own backup plan.
To keep using your instance, start the renewal process from your order in the console. To switch from Commit 16 to Commit 24, check the new configuration and plan your data migration first, then follow the steps shown in the console.
We accept USDT-TRC20 and Visa, Mastercard, and Amex processed by Stripe. All prices and payments are in US dollars (USD). The payment gateways available at checkout are those shown in the console. Seeplans and pricingfor prices by model and all four rental periods.
Check each layer in turn, from instance status and network to system sessions and project configuration. Record the exact error, when it occurred, and the steps you’ve tried to help support get straight to the issue.
First check that the instance is available to connect in the console. Disconnect and start a new desktop session, then try lowering your client’s resolution. If SSH works, check whether the system still responds to commands. When submitting a support ticket, include the client message, connection time, and whether SSH works. Don’t include your connection password.
A timeout usually occurs before key authentication. Check the address and port shown in the console, the instance status, and whether your local network allows outbound connections. Test from another network and note the result; don’t keep changing private keys without first confirming the port rules.
Run df -h to check available space, then look at usage by build artifacts, DerivedData, archives, and model files. Before deleting anything, confirm who owns the files and back up any artifacts you need to keep. If you’ll need more space long term, check the SSD add-on on theplans page.
Check that the certificate is valid, the provisioning profile matches the Bundle ID, and the account running the build can access the relevant Keychain. The desktop login account may differ from the CI runner account, so first reproduce the error under the same account. You can attach redacted error logs to a support ticket, but never send private keys or certificate passwords.
Back up your project source, build artifacts, certificates, and model files yourself. After your rental ends, access to the instance is handled under the Terms of Service. Data retention periods and subsequent deletion rules are specified in theTerms of Serviceand your order details. Don’t assume you’ll still be able to log in and retrieve files after expiry.
Commit code to your own repository, and copy any unarchived IPAs, logs, or model outputs to storage you manage.
Review the use of signing certificates, keys, and CI variables. Rotate credentials on the project side if needed, and don’t leave private keys in shared build logs.
If you need the same instance, check renewal options early. If you’re finishing up, verify that your backups are readable before wrapping up.
If you have an order, sign in to the console and submit a support ticket with your order number, node, when the issue occurred, and the error details. If you haven’t ordered yet and have a question about connection or configuration, email us through the contact page.