The studio board. The client sees your domain.
Digital agencies use Rig as the studio control plane for local development. Each client project sits in its own lane with its own ports, environment, and Live Link. Share what is already running on a developer's computer — password and expiry included — without standing up a staging box. On Pro, Team, or Enterprise you attach a custom subdomain such as preview.yourstudio.com, add a square logo, and hide Rig chrome so the client opens your brand. Apex hosts are not used; you CNAME the subdomain and verify with TXT. Source never leaves each machine. Optional Cloud syncs catalog metadata and encrypted Continuity backups across the studio fleet. Mesh wakes a sleeping machine so a review is not blocked by a closed lid. Cursor and Claude connect through the local MCP hub to logs and restarts. Rig is not a hosted IDE and not a cloud coding VM. Book a call to walk white-label domains on your next client review.
- Custom Live Link subdomain on Pro, Team, and Enterprise
- Square logo and hide Rig chrome on the preview page
- Per-client lanes for ports, env, and expiry
- Fleet catalog across studio machines — source stays on disk
- Book a call — mailto:help@userig.app
Can the client preview use our own domain?
Yes on Pro, Team, or Enterprise. Point a subdomain such as preview.studio.com with a CNAME, verify TXT, attach a square logo, and hide Rig chrome. Apex domains are not supported.
Does the repo leave the computer when we send a Live Link?
No. The link proxies the process already running on that machine. Source stays on disk. Kill or expire the share when the call ends.
How is this different from the freelancer page?
Freelancer covers one-person client preview. Agencies adds studio fleet, seats, custom domains, and a book-a-call path for white-label setup.