Skip to content

Use case · Remote development

A Mac for remote development, always on

Keep a Mac with Apple silicon running in the datacenter and work on it from whatever laptop you have with you: editors over SSH for code, Screen Sharing when you need Xcode, Instruments or the Simulator on screen.

Why a dedicated Mac

Built for this, not borrowed for it

Any laptop, one Mac

Teammates on Linux or Windows can build and run Apple-platform code without owning a Mac, and Mac users can keep heavy builds off their battery.

Always on

Long builds, indexing and background jobs keep running when you close your laptop. Reconnect to the same tmux session from anywhere.

Private by default

There is no public SSH port to scan. The machine is reachable only from your own tailnet or your WireGuard peers.

Shared with your team, not the world

Invite teammates to your organization; everyone sees the same machines, connection details and metrics in the console.

Setup

From order to first job

  1. 1

    Join it to your tailnet

    Paste a Tailscale auth key in the console and choose a hostname; the machine appears in your tailnet with MagicDNS.

  2. 2

    Add an SSH host

    Point your SSH config at the tailnet hostname and the username from the console, then add your public key.

  3. 3

    Open your editor

    Connect VS Code Remote-SSH or JetBrains Gateway to that host, or just ssh in and attach to tmux.

  4. 4

    Switch to the desktop when needed

    Open Screen Sharing over the same tunnel to use Xcode, Instruments or the Simulator interactively.

~/.ssh/config (on your laptop)
Host mac-dev
  HostName <hostname>.<your-tailnet>.ts.net
  User <username-from-console>
  ServerAliveInterval 30
Connect
ssh mac-dev                         # terminal, tmux
code --remote ssh-remote+mac-dev ~/src/app   # VS Code
open vnc://<hostname>.<your-tailnet>.ts.net   # Screen Sharing from a Mac

Values in angle brackets are placeholders for your own details.

Good to know

  • Change the initial password after your first login and prefer SSH keys for everyday access.
  • No Tailscale? Generate a WireGuard configuration per device in the console instead.
  • Screen Sharing works from any VNC client; on a Mac, the built-in Screen Sharing app is enough.

Choosing a plan

Large workspaces and indexing benefit most from extra memory; storage matters if you keep many repositories and simulators.

Compare plans and live availability →

Your own Mac mini in Spain, ready in minutes.

Monthly plans, billed in EUR. Cancel any time, effective at the end of the billing period.