Solution
Sites joined by policy, not by leased lines.
One Inlinea Agent at each site becomes its routing device. Sites reach each other over direct encrypted paths, routes are granted to groups by rule, and a second routing device per site keeps traffic flowing when one is lost.
Before and after
What changes
Today
- MPLS circuits or site-to-site VPN tunnels on exposed firewalls
- Every site reachable from every site
- A single appliance per site, and an outage when it fails
- Changes that take a ticket to the carrier
With Inlinea
- Routing devices that dial out; nothing listens inbound
- Routes granted to groups, so a branch reaches what it should and no more
- Two routing devices per network with automatic failover
- A new site in minutes: install the agent, enrol, assign the route
What solves it
The capabilities behind it
- Networks and routing devicesAny agent with network access connects the network behind it.
- High availabilityTwo routing devices per network; the Control Center flags a single point of failure.
- DNS servers and zonesPrivate names resolve privately across sites.
- Traffic LogsWhich site talked to which, with the rule that allowed it.
A scenario
How a day goes
- 1A new branch opensA small server runs the agent as a routing device and enrols with an Enrollment Key. The Branches group's rule grants it the head-office applications.
- 2A link failsThe second routing device carries the traffic. Pulse shows the failover and the single point of failure until the first returns.
- 3An auditTraffic Logs show the flows between sites for the period, exported in a minute.
Questions buyers ask
Does site traffic pass through Inlinea?
No. Sites reach each other directly over encrypted paths; a relay is used only when a direct path cannot be made, and it cannot read the traffic.
Can we keep our existing firewalls?
Yes. Routing devices sit inside and dial out, so nothing new is exposed.