Connecting branch offices into one secure network: the options, plainly

Most companies with more than one branch know the signs: files sent back and forth by email, a remote-desktop app installed on every PC, stock or accounts that only match at the end of the month, and a different setup in each location.

Connecting branches properly fixes most of that. Here are the options, and what each one asks of you.

Start with what has to be shared

Before choosing any technology, list what the branches actually need from each other: one accounting or ERP system, shared files, a phone system, cameras that head office can see. The list decides how much speed and reliability you need, and that decides the cost.

The main options

1. A VPN between sites, over normal internet lines. Each branch keeps its own internet line, and the routers build an encrypted tunnel to head office. It is usually the cheapest option and works well for most small and medium companies. It depends on good routers and on each branch's line, so a second line for failover is worth it in the branches that cannot stop.

2. Managed SD-WAN. The same idea, with a service that manages the tunnels, picks the best line automatically and gives you one screen for every branch. It costs more every month, and saves effort when you have many branches or no one on staff to manage the network.

3. Leased private lines. A dedicated connection from the provider between sites. Stable and predictable, and usually the most expensive. It makes sense when a system truly cannot tolerate the variation of normal internet.

What matters whichever you choose

• One account per employee, managed centrally, instead of a separate username in every branch. When someone leaves, one change removes their access everywhere.
• Separate what should not mix. Cashier machines, cameras and guest Wi-Fi each belong on their own network segment, so a problem in one does not reach the others.
• Close remote desktop to the internet. Reach systems through the VPN, not through ports opened on the router.
• Monitor the links. Know when a branch goes offline before the branch calls you.
• Write it down. Addresses, passwords in a proper vault, and a simple diagram. The next engineer, or you in a year, will need it.

About cost

Connecting branches is a project and an ongoing cost: lines, licences for some options, and support. Ask for both numbers before you start, so the monthly part does not come as a surprise.

Planning to connect your branches? Tell us how many branches and what they need to share, and we will suggest the simplest option that fits.