Solution
Your traffic leaves from your addresses.
SaaS allowlists, regulators and partners want to know where your traffic comes from. Sovereign Outlinks send a group's internet traffic out through exit gateways on your own devices, in your own country, with a second gateway for failover.
Before and after
What changes
Today
- Traffic leaves from wherever each device happens to be
- SaaS allowlists need every home and hotel address, or none
- A single egress appliance, and an outage when it fails
- No answer to where data left the country from
With Inlinea
- A group's traffic leaves from your exit gateway's address
- One address to allowlist, from any device, anywhere
- Two gateways per Outlink with automatic failover
- Egress in your data center, in your jurisdiction
What solves it
The capabilities behind it
- Sovereign OutlinksExit gateways on your own devices with failover and a fixed egress address.
- Inlinea OutlinksRegional exit gateways run by Inlinea with fixed addresses, for groups without a data center.
- Per groupFinance through the Outlink, contractors not; precedence decides when two apply.
- Traffic LogsWhat left through the Outlink, when, from which device.
A scenario
How a day goes
- 1The payroll SaaS allowlistAllowlist 203.0.113.10, your Outlink's address. The Finance group reaches payroll from any device; nobody else's address works.
- 2A gateway goes downTraffic fails over to the second gateway. The Control Center shows amber and the single point of failure until the first returns.
- 3A regulator asksTraffic Logs show the Finance group's internet flows left from your data center for the whole quarter.
Questions buyers ask
Does this route all traffic through Inlinea?
No. A Sovereign Outlink is your gateway, in your data center. Inlinea Outlinks are an option for groups that need a fixed address without hosting one.
Can different groups use different exits?
Yes. Outlinks are assigned to groups, with a metric that decides precedence when more than one applies.