ERP only opens inside the office
Business systems run on an office server without a public address. Travelling or working from home means calling someone for help.
Not a spec sheet — the problems that happen every week: an invoice system you cannot open while travelling, branch data that never reaches headquarters, contractor accounts you cannot revoke. VirtuaMesh makes work possible wherever it happens.
These problems often coexist, so adding one VPN or remote desktop only fixes part of the issue.
Business systems run on an office server without a public address. Travelling or working from home means calling someone for help.
Port forwarding has been open for years. Anyone can attempt access, but closing it may interrupt business operations.
Sharing an account often exposes an entire PC or network. Access remains long after the project or employment ends.
Stores without public IPs cannot send inventory, CCTV or POS data back to headquarters in real time.
Large files bounce through chat apps, approvals stall and shared drives are unreachable.
Test, production and office environments sit on separate networks. Opening security groups and public ports is slow and hard to audit.
Devices, members and access history are visible in one place. Revoke access immediately when a contractor leaves or a device is lost.
Approve devices, assign permissions and inspect connectivity from a graphical console without maintaining complex VPN and firewall rules.
Sign in and open the same shared drive, ERP and OA systems. The path and work habits stay unchanged.
No company-wide rebuild. Each group below has something you can try today; pick one and start.
Reach office systems from a hotel, home or customer site.
Reach the internal demo environment without publishing it to the public internet.
Handle OA approvals and open contracts or quotations while travelling.
Read and write large files directly instead of pushing them through chat apps.
Stores, warehouses and headquarters staying in sync.
Send POS, inventory and CCTV data to headquarters without a public IP at the store.
One node plus one subnet route and it is connected in minutes — not weeks of carrier scheduling.
ACLs decide which stores may reach each other; traffic bypasses HQ when hole punching works.
NAS boxes, cloud hosts and rack servers in one private network.
Reach photos, files and media from a hotel or a family home as if you were there.
Join machines across cloud providers and the office into one private network with far less public exposure.
Each environment exposes only the ports it needs, instead of opening a whole segment for debugging.
Contractors, vendors and temporary collaborators get exactly one slice.
Expose one server and port; unrelated devices and subnets stay invisible.
Disabling an account or device takes effect immediately — no password sweep, no stale door left open.
Approvals, revocations and policy edits are logged, so incidents can be reviewed by timeline.
The hard part is not whether a branch can connect. It is whether branches should talk to each other, who may reach whom, and whether opening the next branch means rebuilding the configuration.
Place one node behind the branch router and enable subnet routing. The whole branch subnet becomes reachable by authorized users, with existing IP planning and internet egress unchanged.
Networks and ACLs decide which branches may reach each other. When both sides can connect directly, traffic bypasses headquarters; otherwise it relays through DERP.
Branches, departments and contractors each form a group. Reassigning staff or closing a store means changing the ACL for that group, not editing every device.
When a branch already has its own addressing, subnet routing brings it in without renumbering existing devices. Overlapping subnets must be planned before rollout.
Follow the same steps: install the client, register the subnet route, apply the agreed permission policy. Reserve node capacity based on branch size.
A branch usually counts as one network plus one or two always-on nodes. Up to six branches can start on Team; more branches or dedicated relays point to Enterprise.
Select the statements that describe your company. The result updates immediately.
A full rollout is not urgent yet, but monitor exposed ports and account access.
| Requirement | Fit | Notes |
|---|---|---|
| Access internal business systems | Yes | ERP, OA, shared drives, NAS, CCTV and internal APIs. |
| Connect branches or offices | Yes | Subnet routing reaches the branch network without a public IP. |
| Replace a consumer VPN service | No | Built for private enterprise networking, not public internet access. |
| Zero maintenance | No | The control plane is self-hosted and requires basic server operations. |
| Overlapping branch subnets | Not yet | There is no automatic address translation; re-plan subnets before rollout. |
| Access outside company audit scope | No | Access must follow policy; permissions and logs support controlled management. |
With the boundaries clear, the usual next step is a comparison: see VirtuaMesh against ZeroTier, Tailscale and Pgy →
No full purchase and no network rebuild. Validate one urgent workflow with a few devices first.