Your network should not
chain people to a desk.

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.

Keep your ERPNo file migrationKeep your existing network

The tools were not designed around how you actually work

These problems often coexist, so adding one VPN or remote desktop only fixes part of the issue.

01 · Office-bound

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.

02 · Exposed ports

A router port you are afraid to close

Port forwarding has been open for years. Anyone can attempt access, but closing it may interrupt business operations.

03 · Access sprawl

Contractor access is never revoked

Sharing an account often exposes an entire PC or network. Access remains long after the project or employment ends.

04 · Branch data

Branch data still moves by hand

Stores without public IPs cannot send inventory, CCTV or POS data back to headquarters in real time.

05 · Work from home

A home PC is not an office PC

Large files bounce through chat apps, approvals stall and shared drives are unreachable.

06 · Multi-cloud

Servers in different clouds cannot see each other

Test, production and office environments sit on separate networks. Opening security groups and public ports is slow and hard to audit.

One network, with each person seeing only what they need

Owner / manager

“I do not want to learn who has access after an incident.”

Devices, members and access history are visible in one place. Revoke access immediately when a contractor leaves or a device is lost.

Part-time IT / admin

“We have no full-time IT team, but the network must keep working.”

Approve devices, assign permissions and inspect connectivity from a graphical console without maintaining complex VPN and firewall rules.

Business / finance

“I just want to finish this spreadsheet at home.”

Sign in and open the same shared drive, ERP and OA systems. The path and work habits stay unchanged.

The difference: you do not expose the whole internal network. You expose only the systems and ports that person needs.

Four scenario groups — start with the most urgent one

No company-wide rebuild. Each group below has something you can try today; pick one and start.

01

Mobile & remote work

Reach office systems from a hotel, home or customer site.

Customer site

Demo from a customer site

Reach the internal demo environment without publishing it to the public internet.

On the move

Approve and read files on mobile

Handle OA approvals and open contracts or quotations while travelling.

Working from home

Your home PC on the company share

Read and write large files directly instead of pushing them through chat apps.

02

Branches & retail stores

Stores, warehouses and headquarters staying in sync.

Data back to HQ

Branch-to-headquarters

Send POS, inventory and CCTV data to headquarters without a public IP at the store.

New store

A new store goes live without a leased line

One node plus one subnet route and it is connected in minutes — not weeks of carrier scheduling.

Store to store

Stores talk directly when they can

ACLs decide which stores may reach each other; traffic bypasses HQ when hole punching works.

03

Private cloud & NAS

NAS boxes, cloud hosts and rack servers in one private network.

Home NAS

Home NAS access

Reach photos, files and media from a hotel or a family home as if you were there.

Multi-cloud

Cross-cloud connectivity

Join machines across cloud providers and the office into one private network with far less public exposure.

Environments

Test, production and office can see each other

Each environment exposes only the ports it needs, instead of opening a whole segment for debugging.

04

Vendor & ops access

Contractors, vendors and temporary collaborators get exactly one slice.

Controlled entry

Contractors see only what they need

Expose one server and port; unrelated devices and subnets stay invisible.

Revoke now

One click at project end

Disabling an account or device takes effect immediately — no password sweep, no stale door left open.

Audit

Every change is traceable

Approvals, revocations and policy edits are logged, so incidents can be reviewed by timeline.

Headquarters, branches, stores and travelling staff on one network

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.

Branch 01 · HQ to branch

No leased line, no fixed public IP at the branch

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.

Branch 02 · Branch to branch

When direct, branch traffic bypasses HQ

Networks and ACLs decide which branches may reach each other. When both sides can connect directly, traffic bypasses headquarters; otherwise it relays through DERP.

Branch 03 · Bounded access

One boundary per branch, revoke in one place

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.

Branch 04 · Coexistence

Keep existing subnets instead of renumbering

When a branch already has its own addressing, subnet routing brings it in without renumbering existing devices. Overlapping subnets must be planned before rollout.

Branch 05 · New site

Open the next branch from a template

Follow the same steps: install the client, register the subnet route, apply the agreed permission policy. Reserve node capacity based on branch size.

Branch 06 · Sizing

Count networks first, then nodes

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.

A common way to start: connect headquarters and the one branch that needs it most, run real business traffic for a week, and once latency and permissions check out, replicate the same template to the remaining branches. Plans are billed by networks plus nodes — verify the limits on the pricing page before adding a branch.

Three matches out of ten make a pilot worthwhile

Select the statements that describe your company. The result updates immediately.

0 / 10
Start with one use case

A full rollout is not urgent yet, but monitor exposed ports and account access.

Where it does not fit

RequirementFitNotes
Access internal business systemsYesERP, OA, shared drives, NAS, CCTV and internal APIs.
Connect branches or officesYesSubnet routing reaches the branch network without a public IP.
Replace a consumer VPN serviceNoBuilt for private enterprise networking, not public internet access.
Zero maintenanceNoThe control plane is self-hosted and requires basic server operations.
Overlapping branch subnetsNot yetThere is no automatic address translation; re-plan subnets before rollout.
Access outside company audit scopeNoAccess 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 →

Turn the company from a place into a network that follows your people

No full purchase and no network rebuild. Validate one urgent workflow with a few devices first.