Traffic between your sites that stays genuinely private — and one team accountable for the whole thing, end to end.
For a multi-site business, the network between offices is rarely just a convenience. It carries the records that regulators care about, the systems the business runs on, the data that can’t leak. “Encrypted over the public internet” is a reasonable answer for some of that traffic; for a lot of it, it isn’t. Private Networks keeps your inter-site traffic separated at the carrier layer itself — your own routing domain, your own address space, your own policy, walled off from other customers and from the public internet.
Because we run the carrier-grade network underneath, there’s no handover gap to manage and no third party to chase when something needs attention. One team designs the separation, runs the routing, manages the edge devices and answers the phone when the network needs a change. That accountability is the point: you get a single relationship for the whole network rather than a stack of vendor finger-pointing.
The most common way we deliver that is Layer 3 customer-private routing across our carrier mesh — your own routing that keeps your estate to itself, linking your sites into one private network. Where Layer 2 customer separation is the cleaner answer, we deliver that instead. Where the customer wants SD-WAN flexibility on top of the private underlay, we deploy that together. The design follows the requirement, not a fixed product template.
Common designs
Multi-site enterprise with mixed access. Head office on Business Ethernet, branches on Business NBN, regional or temporary sites on 4G/5G — all bound into one customer-private network with consistent routing and policy. Different access at each site, one network design.
Private routing plus SD-WAN. A customer-private VRF (Virtual Routing and Forwarding) as the underlay, SD-WAN on top for application-aware routing and integration of off-net services such as cloud SaaS, internet breakout and third-party platforms. Common where a customer wants both the carrier-grade private network and the operational flexibility of SD-WAN.
Managed customer-edge. We deploy and operate the customer-edge devices — routers at each site, firewalls, switches — managed end to end from our network through to the customer LAN handover.
DC-anchored private network. Workloads in our datacentres (see Colocation) or on cloud via Megaport and IAA, with the customer’s sites bound into the same private network. One routing domain across access, transport and DC.
Where this sits in the stack
Private Networks is the customer-private layer on top of the carrier infrastructure. Underneath it sits our Carrier Services mesh — Real World as the operating carrier, interconnecting directly with carriers including NBN Co, Telstra, Vocus and Optus — plus cloud and DC interconnect at Megaport, IAA and Equinix. The access layer at each site is whichever of Business Ethernet, Business NBN or 4G/5G suits. SD-WAN sits on top where the customer wants the overlay, and Cyber Security integrates where the design includes managed firewalls and security policy.
Who Private Networks is for
- Multi-site businesses needing real customer separation rather than an internet VPN
- Regulated industries — finance, health, government-funded organisations — where traffic separation is a compliance requirement
- Enterprises with cloud presence binding sites, DC and cloud into one private routing domain
- Customers replacing legacy MPLS with modern equivalent functionality
What's included
- VRF-separated Layer 3 customer networks across our carrier mesh
- Layer 2 customer services where L2 is the right design choice
- Inter-site links across metro and intercity reach
- Integration with Business NBN, Business Ethernet and 4G/5G Data Solutions for the access layer
- Managed routing on the customer's behalf — BGP, static, dynamic, as the customer estate calls for
- Managed endpoints — routers, switches, edge devices we deploy and operate
- Managed firewalls — appliance or virtual, designed and operated by our team
- SD-WAN integration where flexibility or off-net service inclusion needs it
Why it matters
Customer-private, real network separation
VRF separation gives you a Layer 3 customer-private network across the carrier mesh — your routing, your address space, your policy. Not a public-internet VPN dressed up as a private network.
Multi-site, multi-carrier, one design
Your head office on Business Ethernet, branches on Business NBN, regional sites on 4G/5G, all bound into one customer-private network with consistent routing and policy. The access layer can vary; the network design is one piece of work.
Managed from the carrier layer down to the endpoint
We don't just deliver the underlay. Where customers want it, we manage the routing, the customer-edge devices, the firewalls and the security posture. One relationship for the whole network, not a stack of vendor handovers.
SD-WAN where it adds flexibility
Private Networks and SD-WAN aren't competing products. VRF gives you the carrier-grade underlay and policy; SD-WAN can sit on top where the customer needs extra flexibility, faster failover, integration of off-net SaaS or cloud services. Sometimes we deploy both.
Technologies we use
- VRF (Virtual Routing and Forwarding) across our carrier mesh
- Layer 2 customer VLANs where L2 is the design
- Inter-site connectivity over Business Ethernet, NBN, 4G/5G
- BGP / OSPF / static routing as customer requirement
- Managed customer-edge devices
- Managed firewall platforms (appliance and virtual)
- SD-WAN integration (Fortinet, Aruba, IPsec on UniFi, depending on fit)
- Multi-carrier underlay (NBN Co, Telstra, Vocus, Optus)