Mesh · wake · screen

Your other computer, from anywhere.

Wake it while it’s asleep. Screen into it. Run projects on it. Your machines get a private network only they can see: one you build yourself, with your own addresses, your own names and rules written in plain English.

rig / mesh · paired machineslive
Paired machines3 machines
  • this Macyou’re here
  • studio-macawake
  • mac-miniawake · sends the signal
Screen studio-mac · lock screen
Sign in, same as sitting in front of it.
What Mesh does

Wake it. See it. Build it.

01

Wake

A sleeping machine isn't an offline machine. Wake it from your laptop, your browser, or by asking your AI editor. It stays on the list; another machine running Rig that is already awake sends the signal.

02

Screen

Full screen sharing over the private connection. Apple’s Screen Sharing on a Mac, Remote Desktop on Windows, so it behaves exactly as you expect. After a wake, you sign in at the lock screen.

03

Build

Your addresses, your hostnames, your rules. A network you designed, not one handed to you.

The paid bit

Wake, Screen and Teleport

Each one in a few seconds, from whichever machine you have with you.

Rig 1.1.0 Mesh switch: each Mac on a port, with online, asleep and blocked lights
The Mesh switch in Rig 1.1.0: each Mac on a port, lit when it is online, asleep or blocked.

Wake

Bring a sleeping Mac back online from anywhere, then get straight to the project you left running.

macbookyou, on hotel wifi
studio macawake · 4 running

Peer to peer is never metered

You only pay for relay, because relay is the bit that costs money to run.

0p

Screen

Control that machine’s environment from another device.

Teleport

Hand a live project from one machine to another mid task, and carry on where you were.

Tuesday, 3pm, a client’s office

The project is on the Mac at home. It’s asleep.

Fourteen seconds from a sleeping Mac to its screen in front of you.

  1. 01

    0s · Open Rig

    Open Rig on the laptop. Studio Mac is there, asleep, with a Wake button.

  2. 02

    9s · It wakes

    The Mac mini next to it sends the signal. Studio Mac wakes up.

  3. 03

    14s · Screen in

    Screen in. Sign in at the lock screen, same as sitting in front of it.

  4. 04

    Or Teleport

    Or skip the screen entirely: Teleport the running project to the laptop.

Peer to peer vs relay

Direct when it can be. Relayed when it has to be.

Most of the time your machines talk straight to each other. When a network gets in the way, a relay passes the traffic along.

Peer to peer

Never metered

Your machines connect directly, encrypted end to end with WireGuard. Nobody in between can read it, including us. Use it as much as you like.

Relay

The bit that costs money

When two machines can’t reach each other directly, Tailscale’s relay servers pass the traffic along. They see which addresses are talking, not what they say. Plans include a relay allowance.

How Mesh is built
HobbyFree
  • Mesh taster: 1 linked machine, 5 GB relay
Pro$15/mo
  • 5 machines on Mesh
  • 25 GB relay a month
  • Wake, Screen and Teleport
  • Unlimited peer to peer Mesh
Team$25/seat/mo
  • 10 machines per seat, pooled
  • 75 GB relay per seat, pooled
  • Shared machines

Machine limits and relay allowances are on pricing.

How it works, in pictures

How a route is picked, and what a teleport does.

Two diagrams: the route your traffic takes, and what a teleport does, step by step. Switch to Geek mode for the mechanism.

Address bookHeadscaleKnows each Mac’s address and public key. Never sees files.node map · public keys · mesh addresses
Your Mac, at homenode: home
Your Mac, at the officenode: office
Rig’s relay, LondonDERP rig-lonPasses on encrypted packets it can’t openTLS 443 · relayed bytes metered per Mac

The two Macs talk straight to each other. Fastest, and nothing in the middle.WireGuard over UDP · hole-punched with STUN (UDP 3478) · ChaCha20-Poly1305

Same encrypted traffic, one hop through London. Used only when a direct path is blocked.Relayed WireGuard packets · DERP region 900 · TLS 443 on the mesh NLB

Old MacsourceStops here at the endhandoff: stop + move Live Link
Rig Cloudfleet command queueCarries the job, step by stepteleport_to_device · progress reported per step
New MactargetDoes the workcheck → fit → clone → secrets → make
  1. 01Find it in your catalogcheckRig looks the project up and needs a Git address to clone it from.catalog lookup · git url required (or a linked local path)
  2. 02Make sure there’s roomfitThe target needs free disk space before anything is copied.free disk ≥ 2 GB and roughly 3× the repo size
  3. 03Copy the code overcloneA fresh clone on the new Mac, or the folder you already have there.git clone into ~/Developer/<repo> · or register an existing path
  4. 04Bring the secretssecretsYour encrypted vault comes down. If that fails, the run goes on without it.vault pull · on failure fills .env from .env.example and continues
  5. 05Make it workmakeInstall the packages, set up the database and start the app.makeProjectWork: install → database → start · recover on port conflict
  6. 06Hand it overhandoffThe old Mac stops the project and its Live Link moves to the new one.source stopped · Live Link moved · only when the handoff flag is set

Want to push your last commits first? Teleport can do that on the old Mac before it starts.push_first: pushes unpushed commits on the source before the target clones

The part nobody else lets you touch

Build the network, don’t just join one.

Most private networks hand you an address and a config file. Rig gives you the network itself: pick the address range, name every machine, and decide what can reach what, in sentences, not JSON.

  1. 01 Your range. 10.10.0.0/24 if that’s what you like. Rig checks it doesn’t clash with the Wi-Fi you’re on.
  2. 02 Your names. studio-mac.rig works from any of your machines: browser, SSH, file share.
  3. 03 Your rules. Group machines into tags and write what each group can reach. Nothing else gets through.
  4. 04 Undo built in. A change that would lock you out reverts itself unless a machine confirms it still works.
rig / mesh / ruleslive

Your rules, as they actually read

  • Macs tagged trusted can reach studio on Screen Sharing.
  • Macs tagged studio can reach studio on everything.
  • Macs tagged personal can reach studio on nothing.

100.64.0.1 → .254 · 4 in use

Mesh docs → · Tags and rules →

Honest limits

What it doesn’t do

Wake needs a second machine

Another machine running Rig has to be awake on that network to send the signal. One machine alone can’t wake itself, and Rig tells you so instead of spinning.

It’s not a VPN for browsing

This connects your machines to each other. It doesn’t route your web traffic through anything or change where you appear to be.

Both ends need Rig

Every machine on your mesh runs Rig, on a Mac or a Windows PC. The Rig iPhone app can reach them too. Linux isn’t supported.

Two machines. Ten minutes. One network.

Pair them in Rig. Wake and screen come with that. Machine limits are on pricing.