Every machine, one catalog

Rig Cloud is optional. The desktop app works offline. When a studio has more than one machine, cloud syncs catalog metadata, device presence, invites, and encrypted Continuity backups so a project can be started or restored on another machine without uploading the source tree. Fleet visibility shows what is running where. Roles and seats cover who can start or stop a remote project. Source files stay on disk; Live Links share a preview, not a repo. This is for small teams and freelancers with a studio desktop and a laptop — not a hosted IDE or a cloud coding VM.

https://userig.app/teams

NewSnag is coming: client feedback for web agencies. Join the waitlist
ChangelogStatus
Download
Teams · freelancers, agencies and software houses

Run an agency's worth of stacks.

Every machine in the studio on one board: who's running what, which machine is behind on updates, and one catalog of client projects. Source code never leaves each machine.

Create a teamSee Team pricing

Start free. Team is $25 a seat a month, or $240 a year.

rig / team / fleetlive
Fleet · 3 machines1 behind
MachineRigCPUStatus
Rich's MacBook Pro2 runningbeta.34 · up to dateOnline
Studio Mac mini1 runningbeta.31 · behindOnline
Sam's MacBook Airoffline · seen TuenoneOffline
Source code stays on each machine
The problem

Everyone's machine is set up differently.

A small team usually has three laptops, a Mac mini in the corner and a shared document called “how to run the client site” that nobody updates. That is where the time goes.

Without Teams
  • “Works on my machine” and nobody knows why it fails on yours
  • Nobody knows which Mac is running the client site right now
  • A new starter loses a day getting projects running
  • The studio Mac mini is two updates behind and nobody noticed
  • Someone restarted the API and nobody knows who, or when
  • A stolen laptop means rebuilding the whole setup from scratch
With Rig Teams
  • One fleet board shows every machine, its Rig version and what it is running
  • Client projects are registered once in a shared catalog
  • New people clone or link a project from the catalog and press start
  • Machines that are behind on updates are flagged
  • The activity log shows who started and stopped what, and when
  • Continuity keeps an encrypted backup of each machine's Rig setup
How a team runs it

One board for every Mac in the studio.

Invite someone, their Mac joins the board, and the client projects are one click away for everyone with a seat.

You, the ownerRig Cloud account
Fleet boardevery machine, one view
Teammate’s Macsigns in with its own Rig
Studio Mac miniowns the projects
  1. 01Invite by linkPick a role for each person: owner, member or viewer.invite link · role: owner | member | viewer
  2. 02Their Mac joins the boardIt appears with its name, whether it is online and its Rig version.device registers · cpu · mem · uptime · projects running
  3. 03Projects in one catalogOne list of client projects for the studio. Each entry shows which Macs have it.catalog entry · git clone or link an existing folder
  4. 04Start it where it livesStart, stop or restart on the machine that owns it, from your seat.remote start · stop · restart · bulk across devices
  5. 05Everything written downStarts, stops, restarts, Live Links and invites are logged with who and when.activity log · actor · timestamp · per project
What Teams gives you

Every machine, one catalog.

Each part below is something you can do in the Rig desktop app today once your team is set up.

Fleet board

Every machine on one board

Each computer that signs in shows up with its name, whether it is online, its Rig version, CPU, memory and uptime, and how many projects it is running. Offline machines show when they were last seen.

Shared catalog

Client projects registered once

Add a client project once and the whole team can see it. Clone it via git, link a folder you already have, or Teleport a whole setup to another machine.

Remote control

Start it where it lives

Start, stop or restart a project on the machine that owns it, from your seat. Or restart it in bulk across every device that has that catalog project.

Seats & roles

Owner, member, viewer

Invite people with an invite link and give each one a role. Owners manage the team, members run projects, viewers can look without changing anything.

Shared machines

The office Mac mini belongs to the team

Put a studio machine in the team so everyone with a seat can see it and the projects on it, instead of it being one person's computer that only they understand.

Admin controls

Owners decide who does what

Manage seats, roles and invites in one place, and sign in with passkeys and two factor authentication. On the Mac, Touch ID can confirm it is you.

Activity

Who started what, and when.

When something changes on a shared project, the team activity log records it. No more “did someone restart staging?” in the group chat.

Team activity log

Every start, stop, restart, Live Link and invite is written down with the person and the time. It is the first place to look when a client site suddenly changes.

01
rig / team / activitylive
richrestarted api-gateway on Studio Mac mini
samopened a Live Link for storefront · password protected
richinvited sam@studio.dev as member

Seats & roles with invite links

Send an invite link, pick a role, done. The person signs in to Rig on their own computer and their machine joins the fleet board.

02
rig / team / seatslive
  • rich@studio.devOwner
  • sam@studio.devMember
  • maya@studio.devViewer
Invite link copied

Shared catalog

One list of client projects for the whole studio. Each entry shows which machines have it, so you know where to start it.

03
rig / team / cataloglive
  • acme-storefront3 machines · clone via git
  • fenwick-wp2 machines · local folder
  • northwind-api1 machine · teleported
Machines and relay

Pooled per seat, so the team shares the allowance.

Team includes everything in Pro, including Mesh to Wake, Screen and Teleport between your own machines. The machine and relay allowances add up for every seat and are shared across the team.

Machines

10 machines per seat, pooled

Five seats means fifty machines between you. A busy person with a laptop, a desktop and the studio mini does not run out while someone else uses one.

Relay

75 GB relay per seat, pooled

Relay is the fallback route Rig uses when two machines cannot reach each other directly. It costs us bandwidth, so it is the bit that is metered.

Peer to peer

Never metered

When machines can reach each other directly, that traffic is free and unlimited, exactly as on Pro.

How Mesh works
Getting started

A team in an afternoon.

  1. 01

    Create the team

    Make a free Rig cloud account and start a team. The account links your desktop apps together; it does not host your code.

  2. 02

    Invite people

    Send invite links and choose owner, member or viewer for each person.

  3. 03

    Sign in on each Mac

    Each person signs in from the Rig desktop app. Their machine registers itself and appears on the fleet board.

  4. 04

    Register projects once

    Add client projects to the shared catalog. Teammates clone or link them and start them with one click.

Continuity

A stolen laptop costs you an afternoon, not a client.

Each machine keeps an end-to-end encrypted backup of its Rig setup: the project list, groups, preferences and MCP settings. Never the source code. Restore it on a new computer, then link or Teleport the folders back.

Encrypted on your computer

The backup is encrypted before it leaves the machine. You get a recovery key once and nobody can open the backup without it, including us.

Backs itself up

Daily or weekly backups run while Rig is open, so the latest setup is there when you need it.

More about the account

What the cloud account syncs, what never leaves your computer, and how Continuity works.

Cloud & Continuity
Related

Doing client work?

Rig for agencies

Client previews on your own domain, client lanes, Snag client feedback and reviews in your branding.

Agencies

Mesh

Reach your own machines from anywhere: wake a sleeping Mac, see its screen, move a project across.

Mesh

Pricing

Rig is free on your own computer. Team adds seats, shared machines and admin controls.

Compare plans
Questions

Fair questions

Does our source code go to Rig's servers?

No. Each project's code stays on the computer it lives on. Teams shares the catalog, machine status and the activity log, and Continuity backups are encrypted setup only.

Do I need Teams if I work alone?

No. Rig is free on your own computer, and Pro covers one person with several machines. Teams is for when more than one person shares projects and machines.

Can I control a teammate's machine?

You can start, stop or restart catalog projects on a machine in the team, from your seat. What each person can do depends on their role.

Start free. Team is $25 a seat.

Run Rig on your own machine for free, then create a team when the second person joins.

Create a teamDownload Rig