The hospitality networking problem
A hotel group or restaurant chain has two networks at every property that must never be confused: the management network that runs the business — property management, POS, reservations, CCTV — and the guest network that serves WiFi to customers. Head office needs the management networks of all properties joined into one, so reservations, billing, and reporting work centrally. The guest networks must stay isolated, per property, from all of that.
Getting central management without ever letting a guest near the business systems — that's the hospitality networking problem, and most properties have no IT staff to solve it.
What you're connecting
- Property-management systems (PMS) — each property's PMS reaching central reservations and rate management.
- Point-of-sale — restaurant, bar, and front-desk POS feeding central sales reporting.
- CCTV / NVR — so a security office and head office can view any property's cameras.
- Back-office computers — property finance reaching the central books.
- Door-lock and building systems — where these report to a central management console.
Guest WiFi must stay separate
This is the non-negotiable. A guest connecting to the hotel WiFi must have no path to the property-management system, the POS, or CCTV. A breach of guest WiFi reaching the business systems is both a security incident and, where card payments are involved, a compliance failure.
MeshWG operates only on the property's management network. Guest WiFi runs on its own separate network and is never part of the mesh — a guest device simply has no route to anything MeshWG connects. Within the management network, MeshWG's policy rules add the second layer: the PMS reachable from reception, CCTV restricted to the security office and head office, each device reaching only what its role requires.
How MeshWG connects properties
MeshWG runs on the management router each property already has. Per property: add it in the dashboard, paste the generated configuration into the management router, and the property's management systems join the group's private mesh — about two minutes. No appliance, no truck roll.
From head office: one private network spanning every property's management systems, central policy, a single dashboard showing each property's link status, and 24/7 support. It works with the router brands hospitality properties typically run — see the supported router families.
Restaurant and QSR chains
A restaurant or QSR chain has the same shape with different systems: each outlet's POS, kitchen-display systems, back-office PC, and CCTV connect to head office for central menu and price management, sales reporting, and inventory. The customer-WiFi separation is just as critical — card-payment environments depend on the POS network being isolated from anything a customer can touch.
MeshWG handles a 30-outlet QSR chain the same way it handles a 10-hotel group: each outlet's management router joins the mesh in two minutes, customer WiFi stays separate, head office gets one view. Per-outlet pricing means the cost scales linearly and predictably as the chain grows.
The cost, for a real group size
| 10-property group | SD-WAN appliances | MeshWG |
|---|---|---|
| Hardware | Several lakh | ₹0 (uses existing routers) |
| Monthly cost | Licensing + managed service | ~₹2,800 (10 routers, 2 free) |
| IT staff needed | Typically yes | No; 24/7 support included |
| New property onboarding | Days | ~2 minutes |
Frequently asked questions
How do hotel groups connect multiple properties?
A hotel group needs each property to reach the central property-management system (PMS), the central reservations system, and head-office finance — while keeping that traffic completely separate from guest WiFi. The right tool is a private network connecting each property's management router into one encrypted overlay. MeshWG does this on the routers the properties already have: the PMS, POS, and CCTV at each property join a private mesh; guest WiFi stays on its own separate network and never touches it.
Can MeshWG keep guest WiFi separate from hotel systems?
Yes — and this separation is the single most important thing a hospitality network must get right. MeshWG operates on the property's management router and management VLAN; guest WiFi runs on its own separate network. They do not mix. A guest on the WiFi has no path to the property-management system, the POS, or CCTV. MeshWG's policy rules add a second layer: even within the management network, you control which devices reach which — the PMS reachable from reception, CCTV restricted to the security office and head office.
Do restaurant chains need the same kind of network as hotels?
The shape is the same, the systems differ. A restaurant or QSR chain connects each outlet's point-of-sale, kitchen-display systems, back-office computer, and CCTV to head office for central menu management, sales reporting, and inventory. Like hotels, restaurants must keep any customer-facing WiFi entirely separate from the POS network — card-payment environments depend on it. MeshWG handles both: outlets join a private management mesh, customer WiFi stays separate.
What does it cost to network a 10-property hotel group?
With MeshWG: 10 property routers at ₹349/month each, first 2 free, is about ₹2,800/month — roughly $34 — for the whole group, using existing routers. The SD-WAN appliance approach for 10 properties typically runs into lakhs of hardware plus ongoing licensing and a managed-service contract. For an independent hotel group or a growing restaurant chain, the mesh-VPN approach makes central management affordable without an enterprise networking budget.
Will the property keep working if the internet drops?
Yes — the property's local systems keep running. The PMS, POS, and door systems operate on the local network regardless of the internet link. If the internet drops, the MeshWG tunnel to head office pauses; the property still functions and the tunnel re-establishes automatically when connectivity returns (persistent keepalive handles the reconnection), syncing any queued data. The mesh going down never takes down a property's ability to check guests in or process bills locally.
Does MeshWG work with the routers hotels already have?
Yes. MeshWG runs on TP-Link, MikroTik, OpenWrt, OPNsense, pfSense, Ubiquiti, Asus, and GL.iNet routers — the brands hospitality properties typically already run for their management network. There's no appliance to buy or install; you paste a generated configuration into the property's existing management router. See the full list of supported router families on the WireGuard router guide.
Next steps
Connect head office and your first property free — two routers, no card.