Your domain on the Live Link
CNAME a subdomain, add a square logo, hide Rig. The client opens preview.yourstudio.com, not a generic share URL.
Agencies · Pro+ custom domains
The studio board. The client sees your domain.
Run every client stack on the machine that owns it. Send a Live Link on preview.yourstudio.com, with your logo on and Rig's branding off. Source never leaves the machine.
Usually same-day. Custom domains on Pro, Team, and Enterprise.
Studio · client lanes03 LIVE
- acme-storefrontpreview.northstar.studio:3000
- fenwick-wpreview.northstar.studio:8080
- northwind-apilane idle—
✓ Live Link — preview.northstar.studio
GET / 200 · 2 viewers · password on
logo served · Rig chrome hidden
PREVIEW.NORTHSTAR.STUDIO LIVE ◆ LOGO ON ◆ RIG HIDDEN ◆ 3 CLIENT LANES ◆ STUDIO MINI AWAKE ◆ MCP LINKED ◆ CONTINUITY BACKED UP ◆ PREVIEW.NORTHSTAR.STUDIO LIVE ◆ LOGO ON ◆ RIG HIDDEN ◆ 3 CLIENT LANES ◆ STUDIO MINI AWAKE ◆ MCP LINKED ◆ CONTINUITY BACKED UP ◆
The problem
Client reviews eat the afternoon.
The usual way
- Deploy to a staging box for a five minute “does this look right?”
- Send the client a generic share URL with someone else's name on it
- Two client projects fight over port 3000 on the same laptop
- The project is on a Mac in the studio and you are at home
- Feedback arrives as a blurry screenshot and “it's broken”
With Rig
- Share what is already running, with a password and an expiry
- The client opens preview.yourstudio.com with your logo
- Each client gets a lane with its own ports, env and expiry
- Mesh wakes the studio machine and starts the stack there
- Snag sends the click, the screenshot, the device and the server logs
Three things
What agencies get from Rig.
How domains work
One board, every client isolated
Ports, env and expiry per project. Acme on :3000 does not collide with Fenwick on :8080 when both need a review today.
Studio machines, one catalog
See who is running what. Wake a closed lid. Start the stack on the machine that owns it. Source stays on that disk.
Custom domains
The review looks like your agency.
Live Links already share what is running on your computer, with a password and an expiry. On Pro, Team or Enterprise you point a subdomain (preview.studio.com) at Rig, prove it is yours with a TXT record, attach a square logo and hide “Powered by Rig”. Apex domains (studio.com on its own) are not used. The secure HTTPS connection is handled at the Rig edge, so there are no certificates for you to manage.
Client side
Feedback that says exactly what broke.
The Agency plan ($149 a month, 3 seats included) adds the client side on top of Team. Snag client feedback · Custom and white label domains · Client reviews in your branding · Guest access for clients · Priority support.
Snag client feedback
Snag is coming to Rig. Your client clicks anywhere on the shared site and you get the screenshot, the device and the server logs, instead of a vague email.
01Client is looking at the checkout page
Custom and white label domains
Client links on your own subdomain, with your logo and no Rig branding.
Client reviews in your branding
The review page the client sees looks like it came from your studio.
Guest access for clients
Let clients in as guests to see and review their own project.
One Mac, many clients
Every client on its own ports, under your name.
Two reviews can run on the same studio Mac today without touching each other, and each link is yours to switch off.
Your studio Macthe stacks run here
preview.yourstudio.comyour CNAME · your logo
Acme · :3000own env and expiry
Fenwick · :8080own env and expiry
- 01Start the client’s stackVite, the API, WordPress and Laravel sidecars come up health-checked, in order.
start group · health checks · Rig owns the ports - 02Acme gets its own portsTwo reviews run side by side. Neither grabs the other’s port.
:3000 and :8080 · env and expiry per project - 03Fenwick, same MacNo shared env and no collisions, even on one machine.
per-project ports · env · expiry - 04Live on your domainThe client opens your studio’s address, with your logo and no generic share URL.
CNAME → relay · custom subdomain + logo (Pro+) - 05Kill it when the call endsSet an expiry on the link. Nothing is left hanging on a generic URL.
expires_at · revoke when done
How an agency day actually runs
Details that survive a client call.
- 01
Boot the lane
Start the client's whole group in a health-checked order: Vite, API, WordPress, Laravel sidecars. Rig owns the ports, so two reviews do not both grab :3000.
- 02
Share on your host
A Live Link with a password and an expiry. Custom subdomain and logo on Pro and above. Kill the share when the call ends, so nothing is left hanging on a generic URL.
- 03
Wake the studio machine
Mesh reaches the machine that actually has the stack. Screen in if you must. Continuity restores the board on a new laptop, never the repo.
In the product
Screens from the board.
Seats, roles and the studio fleet come from Rig Teams. Live Links and env profiles are part of the free desktop app.
Fleet without a devops hire
Seats, roles, and which machine is running the client stack, from the same catalog.
Kill the link when the call ends
Password, expiry, revoke. Staging boxes do not get to linger for a five-minute “does this look right?”
Client env, not your day-job keys
Lanes and env profiles keep production secrets out of the default local stack.
Questions
Agency questions
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.
Walk the domain on a real client.
Twenty minutes. We will put preview.yourstudio.com on a Live Link and leave Rig off the page.