Skip to content

Early access · waitlist open

Zero Trust Access
to legacy VPNs.Web-based VPN Client.

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

What Trilinear does

01 — Browser access

Customer hosts in a browser tab.

  • RDP and SSH in the page, nothing to install
  • Several customers open side by side
  • Two in-browser RDP engines to choose from

All capabilities

02 — Isolated tunnels

One sealed sandbox per customer.

  • A separate sandbox and network for every tunnel
  • Customers on the same IP range, connected at once
  • No route between customers, or onto your network

How isolation works

03 — Any gateway sign-in

Answer the gateway's prompts in the page.

  • Passwords, certificates and one-time codes
  • Multi-step MFA prompts, answered in the page
  • FortiGate and OpenVPN browser SSO

Supported VPNs

04 — Tunnels on demand

Connected only while someone is working.

  • A tunnel comes up when an engineer connects
  • It closes itself after the last session
  • Pin one open for up to 12 hours, or cancel in one click

The life of a tunnel

05 — Access and audit

Know who connected where, and when.

  • Engineers see only the customers you grant
  • Every sign-in, connection and session recorded
  • Disable an account and its live session ends

What Trilinear stores

Fig. 1The Trilinear console. Illustrative.

Connects to

  • Fortinet
  • Cisco
  • Palo Alto Networks
  • Ivanti
  • F5
  • WatchGuard
  • OpenVPN
  • IPsec / IKEv2
All 12 VPNs

01 — The problem

Your engineers are running a museum of VPN clients.

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.

  • 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

One browser on your side. One sealed tunnel per customer on theirs.

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.

Fig. 2Where the VPN ends. Sandboxes are hardware-virtualised in production.
  1. Step 1

    Import the file

    Drop in the OpenVPN profile, AnyConnect profile or FortiClient export your customer sent. The connection fills itself in.

  2. Step 2

    Click connect

    The tunnel comes up on demand. Answer the customer's MFA or SSO prompt in the page.

  3. Step 3

    Work in the browser

    RDP or SSH in a tab. Close it and the tunnel shuts itself down.

03 — What you get

The whole job, from the config file to the audit record.

All features

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.

Sign in the way the customer insists.

Passwords, certificates, one-time codes and browser SSO. Whatever the gateway asks for appears in the page, and you answer it there.

Give each engineer only their customers.

Access is granted per customer. Onboarding is one login and a few ticks. Offboarding is one switch, and their live session ends with it.

Answer “who connected?” in seconds.

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

Dozens of customers. Dozens of firewalls. One place to work.

Give every engineer one login, and take the clients, the conflicts and the shared passwords off their laptops.

Onboard in minutes
Add an engineer and grant their customers. No installs, no imaging.
Offboard with one switch
Disable the account and every customer's access ends at once.
Keep customers apart
No route between customer networks, or from them onto yours.
Show your work
Hand a customer the record of every session into their network.

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

Fewer clients, fewer stored passwords, fewer ways in.

How we protect it
  • 01

    Isolated

    A separate sandbox and network for every tunnel, hardware-virtualised in production.

  • 02

    Encrypted

    VPN configurations and shared logins are encrypted at rest, and never reach a laptop.

  • 03

    MFA required

    A second factor on every account, built in or through Microsoft sign-in.

  • 04

    Audited

    Sign-ins, connections and sessions on an append-only record.

Stop installing
VPN clients.

Join the waitlist. Tell us which VPNs your customers use and we'll put them first.

Rather talk first? Email us