Resources · Blog

Field notes.

Short, practical write-ups from the people building Rig: how to run local projects with less fuss, what changed in each release, and real setups from studios and solo developers. Pick a topic below to narrow the list.

Unfinished workshop bench with tools in use and a paper calendar on the wall

Beta now, Pro later: an honest roadmap

Free while in beta means every feature you can use today. Pro lands later; we will not soft-paywall surprise you mid-sprint.

Read →
Analog industrial panel meter with the needle in a healthy mid range

What running means on the board

Running is a process Rig started and is still watching — not a vibes-based green light.

Read →
Mac restarting at sunrise beside a cooling coffee

Morning after an OS update

macOS updates rearrange permissions and kill long-lived daemons. The board tells you what came back.

Read →
Model shipping container beside loose hand tools on a workbench

Docker Desktop vs Rig for local stacks

Containers are great when you need them. Most studio stacks are processes. Pick the tool that matches the shape.

Read →
Laptop lid closing after a call, headphones down, empty chair across the table

Stop the share when the call ends

Live Links are opt-in and never auto-start. Ending the call without ending the share is how previews linger.

Read →
Two manila envelopes on a desk — studio vs personal — beside a laptop

Env profiles: client vs personal

Fill from .env.example, switch profiles, keep client keys off the personal laptop by habit — not by hope.

Read →
Small padlock resting on a closed silver laptop

Local HTTPS without the cert dance

Managed local services can get HTTPS without you becoming a part-time PKI operator.

Read →
MacBook in a dark quiet studio with only a thin lid glow

The tray as a quiet control plane

Menu bar modes exist so you can start/stop without opening the full window. Quiet is a feature.

Read →
Hardware security key on a desk beside a closed notebook

GitHub connect without folklore

A real token, real validation, and clear errors — not a mock Connect button that pretends you are linked.

Read →
Sealed kraft envelope with a redacted bar on a steel desk

Crash diagnose in one bundle

When Rig or a project falls over, a redacted diagnostics bundle beats a screenshot of a stack trace.

Read →
Four people at a small agency table with laptops, no server racks

Team seats without a devops hire

Shared catalog, devices, and seats are enough for a studio. You do not need Kubernetes to start Vite on the other Mac.

Read →
Brass hourglass beside a closed laptop after a call, headphones off

Why Live Link shares expire when the call ends

Client previews should die when the call ends. Expiration and view limits are product features, not nagware.

Read →
Studio display and laptop sharing the same desk, lamp, and notebook

Appearance that survives another Mac

Density, tray modes, and ports-on-cards should follow you when Continuity syncs prefs — not reset every Teleport.

Read →
Metal toy engine with a sidecar on a workbench — main process plus helpers

Procfile plus sidecars on one board

A Procfile starts the main cast. Rig also keeps Vite, queue workers, and managed databases in the same ordered group.

Read →
Crowded desk cable run with two connectors competing for one port

Reclaim a port from the board

When :3000 is taken, Rig shows which process owns it. Reclaim without another lsof archaeology session.

Read →
Open public mail tray beside a closed locked leather portfolio

Support vs community forum

Public tips belong on the forum. Account, billing, and secrets belong in Support. Mixing them wastes everyone's time.

Read →
MacBook in use on a desk while overcast sky sits beyond the window

Cloud status page: your Mac is still fine

When userig.app has a blip, local projects keep running. The status page is about cloud, not your board.

Read →
Workshop bench with existing hand tools and a closed laptop to the side

What Rig does not replace

Not your IDE. Not Herd. Not Docker. Not git. Rig is the control plane around the tools you already chose.

Read →
A row of project folders on a steel shelf with one folder pulled forward

Project-scoped MCP tokens

Hub-wide tokens are convenient. Project tokens are what you hand an agent that should not see the whole fleet.

Read →
Brass key and sealed envelope on cream paper beside a closed notebook

The Continuity recovery key ritual

Encrypted Continuity backups are useless without the key. Treat the key like a vault item, not a Slack paste.

Read →
Industrial status lamps on a brushed steel panel, one glowing green

Health checks that are not just curl

A green board means the process stayed up and answered. A curl in a sticky note means you remembered to run it.

Read →
Two metal parts trays on a workbench — one grouped, one mixed

Groups vs presets: which one you want

Groups are the morning stack. Presets are the reusable start shape. Mixing the words is how settings pages get scary.

Read →
Paper wireframes and a laptop on a wood-and-steel desk for local theme work

WordPress local without Local WP drama

Rig can stand up a PHP built-in server with pretty permalinks for WordPress folders — without adopting another stack product.

Read →
Local web-development desk with a laptop, second display, and coffee

Valet sites open from the board

When Rig detects Valet linkage, Open site hits the *.test URL. Herd/Valet stay the runtime; Rig stays the board.

Read →
Mac mini on a dark studio shelf with a faint status light, the room asleep

Mesh wake vs leaving the studio Mac on

Burning watts overnight is a habit. Wake-on-mesh is the other option when the Mac at home is asleep.

Read →
Three people working around a small studio table with laptops

Soft Free quotas during beta: what they mean

Devices, seats, and orgs have soft caps while Rig is free. They exist so the fleet stays usable, not to surprise-charge you.

Read →
Calm hands at a keyboard beside a laptop, no emergency cable-yank

Ask Cursor to restart without kill -9

Pasting shell into chat is how you nuke the wrong pid. Scoped MCP restart is the boring alternative.

Read →
MacBook in a quiet locked studio with blinds half closed

When to stay local-only on purpose

Cloud sync is optional. Some studios should never turn it on — and that is a feature, not a gap.

Read →
Single wide monitor on a desk with a spare laptop stacked unused beside it

One log pane beats two laptops

Unified logs are not vanity. They are how you stop owning a second Mac just to watch stderr.

Read →
Closed MacBook on a walnut desk surrounded by peeling sticky notes

Sticky notes are not a control plane

The board is for the stack you run every day. Sticky notes are for the one-off. Mixing them is how mornings get expensive.

Read →
Rig fleet board with processes running

Morning boot without six tabs

The same stack every day should not be a ritual. Rig starts the group in order, health-checks it, and leaves Terminal for the one-off commands.

Read →
Rig control plane dashboard with Continuity in the catalog

Backup the setup, not the repo

Continuity stores encrypted env shape, ports, and catalog — not your source tree. Restore a new Mac without handing the cloud a git host.

Read →
Two MacBooks on a desk — studio and laptop workflow

Client preview without a staging box

Live Link publishes your local server at a userig.app/live URL for a client review. No Cloudflare tunnel required, and the repo never leaves the Mac.

Read →
Rig project workspace showing a port conflict

Port already in use: without lsof

Rig owns the ports your projects bind. When :3000 is taken, you see which process has it and reclaim it from the board instead of another lsof ritual.

Read →
Developer desk with a MacBook running a terminal session

Scoped MCP, not a pasted terminal

Giving Cursor your shell is a trust fall. Rig's local MCP hub hands the agent health, logs, ports, and restart — with a token you can rotate.

Read →
Rig project workspace with live logs

Herd is the runtime. Rig is the board.

Laravel Herd should keep serving PHP. Rig starts Vite, the queue, and MCP around it. Many studios run both — here is when that split is honest.

Read →
Rig control plane dashboard with running projects

What is a local process control plane?

Rig is a Mac app that discovers, starts, stops, and watches every process in your local project from one window — with logs, ports, and MCP. Not a hosted IDE.

Read →
Rig project workspace with live logs

Fleet control without a CI babysitter

Remote start/stop across the studio's Macs — and why we didn't build another dashboard-shaped cron job.

Read →
Rig control plane dashboard with running projects and MCP hub online

Why Rig keeps your code on the Mac

Cloud dev boxes want your repo. Rig takes the opposite bet: sync the setup, never the source. Here's the architecture and the trade-offs.

Read →
Developer desk with a MacBook running a terminal session

MCP that isn't a raw shell

Giving an agent your terminal is a trust fall. Scoped runtime tools are the safer contract — here's ours.

Read →
Two MacBooks on a desk — studio and laptop workflow

Teleport a project between Macs

Publish from one machine, pull the whole working setup on another — clone, env, ports, the lot.

Read →
Guest notes

Write a field note with us

Studio workflows, MCP setups, Laravel/WordPress mornings — if you have a real story from the bench, pitch a guest post. We edit lightly and keep your byline.

Pitch a guest post

Notes from the bench, monthly.

No growth-hack drivel — release notes and engineering write-ups.

Works with

Available for any MCP client — including