Connection paths
Private work. A separate path for client reviews.
The shared workspace can stay in the studio.
- TeammateSupported laptop or mobile device→WireGuard
- Fibmesh routing nodePermitted private access→WireGuard
- Studio gatewayRoute to approved resources→LAN
- NAS / workstationFiles or remote work session
People in different places can reach the same approved tools and files without moving all of them to a public service.
File locks, access rights and remote desktop software belong to the applications. Transfer speed depends on both internet connections, latency and the host.
Explore team tools →Share the work without adding the client to the network.
- ClientOpens a review URL→HTTPS
- Publish gatewayOne selected web application→WireGuard
- Project hostTunnel reaches the app
A Publish link can give a client browser access to a review app while administration stays private.
Protect confidential work with application login; a hard-to-guess URL is not access control.
Explore Publish →Keep an integration recognisable when the team moves.
- Integration workerStarts the provider request→WireGuard
- Fibmesh public sourcePublic IPs or suitable exit→HTTPS
- Client / SaaS APISource allowlist + API login
An assigned source can support external systems that expect requests from a known address.
Choose which traffic uses Fibmesh. Changing office Wi-Fi does not itself transfer allocations or keep active sessions alive; the supported connection must recover.
Plan outgoing identity →Put it to work
The project should travel better than the hardware.
A designer works from home, a developer uses a studio workstation and a contractor joins for one delivery. Networks can connect their approved devices to the project’s private resources. Client reviews and external integrations can use separate public paths.
Work with studio resources
Use Networks to reach a shared NAS, supported workstation or build server from another location. Use existing file permissions, remote desktop software and project tools.
Shared team resources →Bring in collaborators
Give a contractor access to the resources needed for the assignment. Remove that access and the relevant application accounts when the engagement ends.
Work across locations →Review work with clients
For a browser-based review app, Publish can provide a public link. A client opens the app without joining the team’s private network.
Preview and review scenarios →A review link and access to the studio’s private resources are different permissions. If work devices also need Outbound, check the full-tunnel scope before changing their internet route. Compare the connection options →
Your first working result
One project, with the right people connected.
Connect a colleague or contractor to a project folder, tool or workstation. Evaluate a real working session before extending access across the studio.
- Open a representative file or use the workstation
- Check employee and contractor permissions separately
- Verify removal of network and application access
A practical first deployment
Connect one project before the whole studio.
Name the working resources
Identify the project folder, app or workstation, its administrator and the tools people will use to reach it.
Separate the audiences
Decide what employees, contractors and clients each need. A client review link and a contractor’s private resource access are different arrangements.
Test the actual work
Open a file, run a build or use the remote workstation. Check performance on realistic connections, then record how to remove access at handover.
Questions, answered
Before you connect.
Can a team work from different countries and providers?
The model is independent of the access provider, using supported existing internet connections. Check service regions, local restrictions, endpoint support and latency. It does not promise service availability in every country.
Can access end automatically on a project date?
Do not assume an automatic expiry feature. Set a review date and have an administrator remove membership, public mappings and application access when the work ends.
Can we use render machines or large media files?
Private connectivity can provide a path to supported workstations, render services and storage. The application, licensing and hardware must support remote use. Test large transfers and interactive sessions before relying on them for a deadline.
Does every project need a new product subscription?
Start with the connection needs, then confirm commercial scope. Not every project needs all four products, and Public IPs and Outbound are alternatives for some outgoing-identity requirements.
Choose one project and a real working session. A useful trial ends with completed work, not just a connected device.
Plan your first deployment →