Weft Start free trial

Use case · Branch networking

Branch office connectivity over any internet link

Join your offices into one network over the broadband, fibre or 4G each one already has: encrypted, with a second line that keeps the office connected if the first fails, and set up from a browser rather than router by router.

What branch office connectivity has to do

A branch is connected when the people in it can work as if they were at head office: the file server, the printer, the accounts system and the phones all reachable, from every office, without anyone thinking about which building they are in. In practice that asks four things of the network between offices:

  • Every office reaches every other office, not only head office, so a branch can print to a printer at another branch.
  • It keeps working when a line fails, quickly enough that a call or a file copy does not notice.
  • Adding an office is routine, not a project that touches every existing router.
  • Someone can see what it is doing: which links are up, how fast they are, and what changed.

The usual ways to connect branch offices

What it isGood atWhere it hurts
Leased line or MPLSA private circuit from a provider to each officePredictable performance, the provider manages itThe most expensive option, ordered and paid for per office, and every office tied to one provider
Router-to-router IPsec VPNTunnels configured on each office's routerNo extra cost if the routers support itEach new office means tunnels on several routers, usually needs fixed public addresses, and failures show up in router logs
Mesh VPN (Tailscale, NetBird)A client on each device, with a gateway for things that cannot run oneConnecting people to machinesWhole office networks reaching each other takes extra routing in each; see NetBird, Tailscale or Weft?
SD-WAN, such as WeftA gateway at each office forming one encrypted network over ordinary internet linesMany offices, several lines each, central controlNeeds a small machine at each office

For a handful of offices on business broadband, a private circuit is usually more than the job needs, and hand-built router VPNs are what most people are trying to get away from. That is the gap Weft fills.

How Weft connects branch offices

  • Every site reaches every other site over WireGuard. Adding an office is one enrolment from the console; nothing on the existing sites is edited by hand.
  • Two lines per site. Weft builds a tunnel over each and watches them with BFD at 300 ms intervals, so a dead line is detected in under a second and traffic moves to the other. While both lines work, traffic between offices is shared across them, so the second line carries part of it all the time rather than waiting idle. A line that comes back is watched for about a minute and a half before it is trusted again, so a flapping line does not drag traffic back and forth. Our two-lines test pulled the first line while a PC was busy, and not one request failed.
  • No fixed address needed at the branch. One office, the hub, accepts incoming connections on UDP 51820. The others connect out to it, so a branch behind an ordinary broadband router with nothing forwarded still joins. If two branches cannot reach each other directly, their traffic passes through the hub, which is one of your own offices, and the console lists the pair so you can see it.
  • Every path is measured. The console shows the latency and loss between every pair of sites, worst first, with a history for each.
  • Changes are tried on one site first. Each change goes to a canary site and reaches the rest only once that site reports healthy.
  • Your existing routers stay. A site can exchange routes with them over OSPF or eBGP, or hand off a routed network on a dedicated port. Or the Weft box can be the office's gateway itself, with its own DHCP and VLANs.
  • People away from the office use the same network. The Weft app for Mac and Windows reaches every office's network, and on full tunnel its internet traffic can follow the same rules as the offices'.

Adding a branch, in outline

  1. On Add a site in the console, name the office and copy the one-line installer onto its Weft box. The box generates its own key; only the public half leaves it.
  2. Choose which port faces the internet and give the office-facing port its address. The office's network is then routed to every other office, with its real addresses.
  3. Point the office's devices at the box for the other offices' addresses: usually one route on the office router, or nothing if the box is the office's gateway.

When we timed it from scratch, two offices were connected and a PC in one was loading a printer's page in the other 9 minutes after the first click, including both installs. Connecting two offices, step by step walks through that test with screenshots.

Where each branch's internet goes

Connecting offices to each other does not have to change how they reach the internet. Devices that keep using the office router as their gateway carry on as before. If you want branch internet to leave through one place, send it through your head-office firewall, and let latency-sensitive services such as Microsoft 365 break out locally at each branch.

What you need at each office

A small machine running Ubuntu 24.04 or 26.04 (x86-64 or ARM64) with one or two internet connections and a port into the office network. Choosing a box for the office covers what works. An office in AWS or Azure can be a site too.

What it costs

£30 per site and £4 per roaming client a month, excluding VAT, with every feature on one plan. A head office, three branches and ten people working from home would be £160 a month. The 30-day free trial covers three sites and ten clients.

Questions

Do our branches need a fixed IP address?

No. Only the hub office needs to accept incoming connections, on UDP 51820. Branches connect out to it.

What happens when a branch's broadband fails?

With a second line at that office, traffic moves to it in under a second. With one line, the office is offline until the line returns, and the console shows which site and when.

Can a branch use 4G or 5G?

Yes, as its only line. As a second line beside broadband, remember that Weft shares traffic between offices across both lines while both work, so a 4G or 5G line carries part of it every day and uses data. Weft can't yet mark a line as backup only, so if the SIM has a data cap, talk to us before you add it. A 4G or 5G line usually can't accept incoming connections, so it can't be the hub's only line.

Is the traffic between offices encrypted?

Yes, end to end between your own boxes, with WireGuard. No traffic between your offices passes through a relay run by anyone else.

Can we keep our existing firewall and routers?

Yes. Weft sits alongside them: it can exchange routes over OSPF or eBGP, hand internet traffic to your firewall, or simply be the route to the other offices.