After renting a dedicated Mac, open the browser-based remote desktop in the portal to check the environment and disk. For longer MLX inference runs, use SSH with tmux so your work isn't tied to a browser tab.
OsxNode M4-16: 16GB unified memory / 256GB SSD. Your connection method doesn't add memory; the machine shuts down when your rental ends unless you renew.
Once your node is ready, there's no need to install a desktop client first. Open the remote desktop from your instance details after signing in. This public guide doesn't provide a direct link to your instance.
Open the portal, check which node and rental period are linked to your order, and view the instance details. If your credentials aren't available yet, check your payment and provisioning status. Don't try connecting with the address from another order.
Select “Open remote desktop” in your instance and sign in with the system username and password provided. Change the initial password on your first visit and store it securely. Don't confuse your portal login with your system connection credentials.
Confirm which disk contains your model directory, then open Activity Monitor to check memory pressure. Start with a small workload to verify the environment. Avoid downloading weights, unpacking a dataset, and starting inference all at once.
We recommend the latest stable versions of Chrome, Edge, Firefox, or Safari, with JavaScript, WebSocket, and Canvas enabled. Managed networks that block persistent connections may show a black screen after authentication or keep reconnecting.
First rule out interference from browser extensions, then try another browser or network. Refreshing the page does not restart the physical machine.
The desktop resolution comes from the remote macOS display settings. Browser zoom only changes how the desktop appears locally; it doesn't expand the remote workspace. Start with “Fit to window” to see the full desktop, then adjust the remote resolution if needed.
Higher resolutions use more bandwidth. You don't need a large desktop to read logs. If text looks small, increase the app's font size instead of continually raising the remote resolution.
Clipboard support depends on browser permissions and the remote desktop tool. Test it with a short, non-sensitive text snippet first. If keyboard shortcuts don't work, use the clipboard control in the session toolbar.
Don't rely on images, file drag-and-drop, or automatic two-way clipboard sync across devices. Transfer datasets and weights over SSH, and don't leave passwords on a shared clipboard.
If you need to work repeatedly with graphical tools, use a compatible VNC client. On macOS, you can also use Screen Sharing. Both connect to the same rented machine.
vnc://HOST:PORT.Clients can interpret single colons, double colons, and display numbers differently. Prefer a separate port field, and don't mistake a display number for a port.
A VNC client can't eliminate network round-trip time. GUI work across networks is still affected by latency and bandwidth. For read-only inference output, SSH may be a better fit.
A foreground process started in a regular SSH session may stop when the connection drops. Start tmux first, then run your script. If your local connection drops, you can reconnect to the session.
Set the three variables to the values provided in the portal. SSH commonly uses port 22, but use the external port shown in your connection details.
read -r -p "SSH host: " SSH_HOST
read -r -p "SSH user: " SSH_USER
read -r -p "SSH port: " SSH_PORT
ssh -p "$SSH_PORT" "$SSH_USER@$SSH_HOST"This variable prompt example is for local Bash. Check the host fingerprint on your first connection. If it changes, find out why before proceeding; don't bypass the warning by disabling host verification.
Run these commands on your rented Mac. Homebrew must be installed. Installing software and downloading models requires a working network connection and enough disk space.
brew install tmux
tmux new-session -A -s mlx-labOnce you're in the session, activate your Python environment and run your inference command. Press Ctrl+B, then D to detach. After reconnecting over SSH, run tmux attach -t mlx-lab to resume.
tmux keeps a session open; it doesn't make a job fault-tolerant. Errors, insufficient memory, a system restart, or the end of your rental will still stop a job. The system and apps share the 16GB of unified memory. We don't recommend running 8-bit models with 13B or more parameters on this plan.
Your choice of node affects how responsive the desktop feels, but it doesn't determine model inference speed. These estimates are for an initial comparison and can't replace testing from your own network.
| Node | Coverage area | Estimated round-trip latency | Good for |
|---|---|---|---|
| Singapore | Southeast Asia | 20~50ms | Remote desktop, builds, file transfers |
| Tokyo | East Asia | 30~60ms | Remote desktop, builds, file transfers |
| Seoul | Northeast Asia | 30~50ms | Remote desktop, builds, file transfers |
| Hong Kong | Southern China and Southeast Asia | 20~40ms | Remote desktop, builds, file transfers |
These are estimates; actual results depend on your network. Carrier routing, Wi-Fi, proxies, and congestion at peak times can all affect latency. These figures are not a guarantee.
When transferring large model weights, also check sustained throughput and retransmissions. Lower round-trip latency doesn't necessarily mean faster downloads. Don't choose a data transfer method based on a single latency test.
You can use multiple access methods in a single experiment. Use the desktop to check system status, the terminal to run processes, and file transfer tools to sync data. Remote desktop doesn't need to do everything.
Use SSH to read generated text, follow logs, and adjust command-line arguments. It only transfers terminal output. Run long jobs in tmux, save logs to remote files, and reconnect later to review them.
Limit: SSH can't operate graphical apps. Terminal output also isn't saved permanently unless you save it yourself.
TextUse the desktop to check Activity Monitor, file directories, app settings, and visualizations. For a quick look, use the browser. For longer sessions, adjust image quality and key mappings in a VNC client.
Limit: responsiveness depends on the network. Closing the desktop tab doesn't stop an experiment or end your rental.
GraphicsSync files over SSH and point the destination path to a disk you've checked. Start with a small sample to verify the directory structure, then transfer the full dataset. Retrieve result files the same way.
Limit: an additional disk doesn't automatically become your download folder. You'll need to configure your model tools' cache paths yourself.
File syncSet SSH_HOST, SSH_USER, and SSH_PORT as described above, then create a datasets folder in the remote user's home directory.
rsync -avP -e "ssh -p $SSH_PORT" ./datasets/ "$SSH_USER@$SSH_HOST:~/datasets/"The trailing slash on the source path means “sync the contents of this directory.” This example doesn't delete files at the destination, but check both paths before running it again. You can split large files into parts ahead of time. Verify file integrity after uploading, and don't give incomplete files to your inference process.
These examples show what to check from three different perspectives; they aren't screenshots of a live interface. Actual buttons, desktop layouts, and client menus may vary from what you see here.
hostname
pwd
df -h
tmux list-sessionsIf files appear on the desktop but not in the terminal, first check that both connections use the same instance and account. Then verify the absolute path and mounted disk location. Don't immediately upload all your weights again.
This service gives you remote access to a dedicated physical Mac. It doesn't automatically map all your local computer's hardware or browser permissions to the remote machine.
Don't rely on remote sessions to listen to audio or do work that needs real-time sound feedback. If a model generates audio, download the result file to your local machine for testing. Transferring an audio file is different from streaming desktop audio.
USB devices plugged into your local computer won't be available to your rented Mac. Workflows that require a physical device connection aren't suited to this setup. If your data can be imported as files, sync it to the remote machine first.
Closing a browser or VNC client only disconnects your viewing session. Whether an SSH job keeps running depends on session management; tmux won't extend your rental. The machine shuts down when your rental ends unless you renew. Retrieve your results beforehand, and don't use the remote disk as long-term backup.
If you need help with a connection, submit a support ticket through the portal with the node name, order number, time and time zone, access method, and complete error message. Don't include system passwords, private keys, or other sensitive credentials in the ticket.
Choose a rental period by the day, week, month, or quarter. First confirm that your model fits in 16GB of unified memory, then prepare your data paths and persistent session. Retrieve your results when you're done; the machine shuts down when your rental ends unless you renew.