Check the boundaries before moving in your project

Your code and certificates, on your own Mac

You get an entire dedicated Apple Silicon M4 / M4 Pro physical Mac mini, not a virtual machine. Other customers do not share its system, disk or keychain. You are responsible for managing access credentials, project permissions and end-of-term backups.

Ideal for developers who need an independent development environment. If your project requires you to keep all assets locally, check your compliance requirements first.

An entire Mac, not a shared development environment

Dedicated access separates environments; it doesn’t replace access controls

If you regularly build, run simulators and manage signing assets on the same machine, an independent system makes it easier to control project state. If you only need macOS for a few minutes now and then, renting an entire machine may not be worth the cost.

A system not shared with other customers

For the rental period, the entire physical Mac mini is assigned to one customer. The system isn’t split into separate customer desktops, and its computing resources aren’t shared with others.

The toolchains, simulator runtimes and build caches you select in Xcode belong to this independent environment. Before switching versions, we recommend noting which version your project currently uses.

Dedicated Mac · Not a VM

Clear boundaries for the disk and keychain

The system disk and keychain aren’t shared with other customers. Your source code, signing certificates and project files stay in your rented machine environment, not in a shared directory accessible to other customers.

A dedicated machine doesn’t mean automatic backups. Arrange separate storage for repository history, uncommitted changes, private keys and build artifacts.

You manage your project files

Assign collaboration access person by person

A machine assigned to one customer doesn’t mean you should share a set of connection passwords with every collaborator. If you manage the machine for a team, limit access to repositories, signing assets and automation credentials according to each person’s role.

If several people need to use the same desktop at once, check that your workflows won’t interrupt one another. A dedicated machine doesn’t include team approvals or access governance.

Least privilege · Revocable access
Connecting from Windows? Check the connection path first

Check encryption separately for desktop access and command-line connections

Browser access, remote desktop clients and SSH use different connection paths. Being able to open the desktop doesn’t mean every client protocol is encrypted by default. Use the connection details provided in the console; don’t expose the desktop port to the public internet yourself.

Check the method you plan to use before connecting
Connection method How to check transport security Recommended practices
Browser access Sign in and access the service through the console. Check that the page uses HTTPS and your browser shows no certificate warnings. HTTPS protects traffic between your browser and the server. Don’t save your login session on a public computer. Sign out of the console and close the session page when you’re done. Don’t share the session link or credentials.
Remote desktop client Check the encryption provided by the protocol you’re using. A desktop login password doesn’t prove that traffic is encrypted. If the protocol doesn’t provide end-to-end encryption, connect through an SSH tunnel instead. Use only the address and connection method returned by the console. Don’t open desktop ports yourself or bypass certificate or identity warnings.
SSH command line SSH encrypts session traffic. On first connection, verify the host key fingerprint. If it changes later, check why before proceeding; don’t simply delete the record and reconnect. Use a passphrase-protected key where possible, and restrict permissions on automation keys. Keep private keys on a trusted device, not in a code repository.

Tunnel your desktop connection through SSH

Get the SSH address, username and remote desktop port from the console. Then set up local port forwarding in your Windows SSH client, binding the local listener to 127.0.0.1and using the desktop service address and port on the machine as the remote destination.

While the tunnel is running, connect your desktop client to the local port instead of the public desktop port. Close the desktop client and tunnel when you’re finished. If you hit a connection error, check the forwarding direction and ports first; don’t troubleshoot by widening access.

Secure the email account you use to recover access

Enable two-factor authentication on the email account that receives verification codes and service notices. Use a unique password and check that you still control the recovery methods. Never give email verification codes, machine passwords or private keys to anyone asking for credentials.

You can describe an issue in a support ticket without including secrets that grant direct access. If connection details change or you notice a suspicious login, sign in to the console and open a ticket. If you suspect a local device has been compromised, revoke affected keys too.

Plan your exports before the rental ends

Verify delivery, then export your assets before your term ends

Service stops when your term ends unless you renew. Don’t treat the machine shutdown time as the time your backup is complete, or assume your project will remain available until your next rental. Add renewal decisions and data exports to your own release checklist.

  1. 01

    At first connection

    Check the model, rental term and connection details in the console. Then confirm that you can access the system, the disk capacity matches your selected plan and the development tools meet your project’s requirements. Refer to the delivery notes for the exact preinstalled software; don’t assume a particular Xcode version is included.

    If you find files unrelated to your project or delivery details that don’t match, stop before importing code or certificates and report the issue in a support ticket. Don’t open, copy or use files from an unknown source.

  2. 02

    During development

    Commit your code regularly to a repository you control. Separately save configurations not tracked in version control, signing assets and any build artifacts you need. Caches can be rebuilt, but private keys and uncommitted changes can’t be recovered by cloning the repository again.

    If you have data retention, deletion evidence or specific data-clearing requirements, contact support to confirm what’s available before importing data—not on the last day of your rental.

  3. 03

    If you decide not to renew

    Export and verify your backups first, then revoke repository tokens, automation credentials and SSH access you no longer need. Check that exported certificate files can be opened and that any required passwords are stored securely, then remove sensitive project files from the machine.

    When service ends, data enters the recovery and deletion process. This page does not promise a fixed retention period, instant deletion or a recovery window. For the status and timing of deletion for a specific order, check through a support ticket in the console. Don’t rely on being able to access the machine after it shuts down.

Check permissions once more before signing

What you need to take with you usually isn’t the build cache

For a one-off release sprint, treat the machine as a temporary workspace and revoke project access when the work is done. If you run CI continuously, manage key lifecycles on an ongoing basis instead of treating one successful connection as a permanent setup.

Certificate private keys: keep a backup and restrict their use

Before importing a signing certificate, make sure you have a usable backup. If you need to export the private key, protect the export file with a strong password and store the file and password separately. Don’t share them through public links or ordinary support ticket attachments.

Use signing assets that meet your current build needs; don’t put every project’s long-term keys on the same short-term rental machine. If you suspect a key has been exposed, revoke and replace it promptly through the relevant developer service.

Verify exported files open correctly

Repository credentials: grant only the access this project needs

Set up access tokens or deploy keys for each repository and task. A build task that only needs to fetch code shouldn’t also get organization admin access. For short-term tasks, set a clear expiration date where possible.

Don’t put tokens in scripts, build logs or commit history. When a team member leaves, the machine is no longer used or a project is handed over, review and revoke the relevant access—not just the working directory.

Per-project access · Revoke when done

Troubleshooting attachments: show support the issue, not your secrets

When submitting an issue, include the order number, machine model, time it occurred and steps to reproduce it. Keep error codes and necessary context in logs, but redact passwords, tokens, private keys, signing file passwords and sensitive source code.

Screenshots can also expose connection credentials, repository addresses or environment variables. Review them before sending. Don’t upload a complete keychain or a certificate bundle that could be used to publish an app as proof of an issue.

Support tickets don’t need full credentials
Keep billing details separate from project files

When choosing a payment method, check who receives your information

All services are billed in US dollars (USD). We accept USDT-TRC20 and Visa / Mastercard / Amex processed by Stripe. Check the console for the payment gateways available for your specific order.

Card payments: this site doesn’t store full card numbers

Visa / Mastercard / Amex payments are processed by Stripe. This site doesn’t store full card numbers. Pay through the order checkout flow; never send card numbers or security codes by email or support ticket.

If you prefer to pay by card, open the payment flow from your order in the console. If a payment fails, don’t keep retrying to troubleshoot it. Check the order and billing status first, then contact support with your order number.

Visa / Mastercard / Amex

USDT-TRC20: check the network before sending

After selecting USDT-TRC20, follow the payment details, amount and instructions shown on the current order payment page. Verify the network and address; don’t reuse an address from chat history, an old order screenshot or a message forwarded by someone else.

If you’re familiar with on-chain transfers, follow the order instructions. If you can’t confirm that the network and address match, stop and contact support. Verify everything before sending; tracing a transfer afterward is much harder.

USDT-TRC20 · Billed in USD

For payment issues, open a support ticket in the console or email support@vpsomni.com. Include your order number and the error message. Don’t send complete payment credentials.

Read the data rules before you start development

The Privacy Policy explains what information is collected and how it is used. The Terms of Service explain rental periods and each party’s responsibilities. Make sure these terms meet your project’s requirements before moving source code and signing assets to your remote workstation.