Start from the file your customer sent.
Drop in an OpenVPN profile, an AnyConnect profile or a FortiClient export and the connection fills itself in. Secrets the vendor encrypted are never imported. You enter them once.
Open any customer network from a browser tab. Trilinear runs each customer's FortiGate, Cisco or OpenVPN connection in its own isolated sandbox, only while someone is working, and logs every session. Nothing to install on your engineers' laptops.
For MSPs and IT teams behind legacy and mandated VPNs. Talk to us
01 — Browser access
02 — Isolated tunnels
03 — Any gateway sign-in
04 — Tunnels on demand
05 — Access and audit
Fig. 1The Trilinear console. Illustrative.
01 — The problem
Every customer picked a different firewall. Every firewall wants its own client, its own login and the same private address range as the last one.
Today
With Trilinear
TodayA VPN client per customer on every laptop, each with its own quirks and updates.
With TrilinearA browser tab. Nothing installed, nothing to patch.
TodayTwo customers on 192.168.1.0/24 collide the moment both are connected.
With TrilinearEach customer in its own sandbox. Same ranges, no conflict.
TodayCustomer VPN logins on laptops and in shared password sheets.
With TrilinearConfigs and shared logins encrypted on the server.
TodayNo single record of who connected where, or when.
With TrilinearEvery sign-in and session in one audit trail.
02 — How it works
The VPN ends inside Trilinear, not on a laptop. Each tunnel gets its own sandbox and its own network, with no route to any other customer or back to you.
Step 1
Drop in the OpenVPN profile, AnyConnect profile or FortiClient export your customer sent. The connection fills itself in.
Step 2
The tunnel comes up on demand. Answer the customer's MFA or SSO prompt in the page.
Step 3
RDP or SSH in a tab. Close it and the tunnel shuts itself down.
03 — What you get
Drop in an OpenVPN profile, an AnyConnect profile or a FortiClient export and the connection fills itself in. Secrets the vendor encrypted are never imported. You enter them once.
Passwords, certificates, one-time codes and browser SSO. Whatever the gateway asks for appears in the page, and you answer it there.
Access is granted per customer. Onboarding is one login and a few ticks. Offboarding is one switch, and their live session ends with it.
Every sign-in, VPN connection and host session is recorded with who, what and when. The record is only ever added to.
Fig. 3Illustrative. Names and addresses are examples.
04 — Built for MSPs
Give every engineer one login, and take the clients, the conflicts and the shared passwords off their laptops.
Also used by software vendors supporting what they sold into customer environments, and internal IT teams giving contractors and auditors access to a legacy VPN without a client on their device.
05 — Security
01
A separate sandbox and network for every tunnel, hardware-virtualised in production.
02
VPN configurations and shared logins are encrypted at rest, and never reach a laptop.
03
A second factor on every account, built in or through Microsoft sign-in.
04
Sign-ins, connections and sessions on an append-only record.
Join the waitlist. Tell us which VPNs your customers use and we'll put them first.
Rather talk first? Email us