Skip to content
Trilinear

Features

Browser access to any customer network.

Everything Trilinear does today, how the parts fit together, and how it compares with what your team does now.

VPN types
9 today
3 more planned
Sessions
RDP · SSH
In a browser tab
On the laptop
Nothing
No client, no agent
Gateway sign-in
4 methods
Password, MFA, certificate, SSO

01 — Capabilities

What's in the product today.

No roadmap items in this list. What's planned lives on the roadmap.

01

Connect and work

  • RDP and SSH to customer hosts in a browser tab
  • Several customers open side by side
  • Two in-browser RDP engines to choose from
  • Start a tunnel without opening a session

02

Import and set up

  • Drop in an OpenVPN .ovpn profile
  • Drop in a Cisco AnyConnect XML profile
  • Drop in a FortiClient export, IPsec settings included
  • Or enter it by hand, with fields for each vendor

03

Sign in and verify

  • Passwords, certificates and one-time codes
  • Multi-step MFA prompts, answered in the page
  • FortiGate and OpenVPN browser SSO
  • Gateway certificates pinned, with a prompt if one changes

04

Isolate and contain

  • A separate sandbox and network for every tunnel
  • Customers on the same IP range, open at once
  • No route between customers, or onto your network
  • Hardware-virtualised sandboxes in production

05

Share and scope

  • One shared VPN login per customer, or one per engineer
  • Engineers see only the customers you grant
  • Tunnels close themselves after the last session
  • Pin a tunnel open for up to 12 hours, or cancel in one click

06

Audit and account

  • Every sign-in recorded, failed attempts included
  • Every VPN connection and host session, open to close
  • Filter history by person, customer or event
  • Disable an account and its live session ends

02 — The life of a tunnel

Connected only while someone is working.

A tunnel isn't a standing link into a customer. It exists for the length of the work, then it's gone.

  1. 01

    Idle

    No tunnel. Nothing is connected to the customer.

  2. 02

    Connect

    An engineer clicks connect and answers the gateway's password, MFA or SSO prompt in the page.

  3. 03

    Work

    Hosts open in tabs over RDP or SSH. Open as many as the job needs.

  4. 04

    Grace

    The last session closes and a short grace period starts, in case you're coming straight back.

  5. 05

    Closed

    The tunnel is torn down on its own. Nothing stays connected.

Fig. 1The green rail marks when a tunnel exists.

Need it to stay up? Lock a tunnel open for up to 12 hours, and cancel in one click.

03 — Compared

Against the two things MSPs do today.

Most teams install a VPN client per customer on each laptop, or keep one shared jump server with the clients on it. In general terms:

WhatClients on laptopsShared jump serverTrilinear
Installing and patching clientsOn every laptopOn one serverNothing to install
Customers with overlapping rangesRouting conflictsNeeds careful manual setupIsolated per tunnel
Where VPN credentials liveOn endpointsOn a shared serverEncrypted, server-side
Per-engineer access to customersHard to scopeHard to scopeBuilt in
Offboarding an engineerChase every deviceRotate shared accountsDisable one account
Who connected where, and whenScattered across logsLimitedOne audit trail

04 — How it's organised

Four things to learn.

The model matches how an MSP already thinks about its work, so there is nothing to map.

  1. 01

    Organisation

    Your company. Owns the customers and the engineers.

  2. 02

    Customer

    One end-customer and the VPN you use to reach them.

  3. 03

    Host

    A machine behind that VPN, reached by RDP or SSH.

  4. 04

    Session

    One engineer on one host. Logged from open to close.

Works with the VPNs your customers already run.

9 VPN types today, from FortiGate and AnyConnect to OpenVPN and IPsec.

See compatibility

05 — Questions

What people ask first.

Something else? Email us, or read how we handle security.

Do my engineers still need VPN clients?

No. Nothing is installed on their machines. Trilinear connects to the customer's VPN on the server side and gives your engineer an RDP or SSH session in a browser tab.

What happens when two customers use the same IP range?

Nothing, which is the point. Every connection runs in its own isolated environment, so two customers on 192.168.1.0/24 can be open side by side without ever seeing each other.

Does one VPN account have to be shared across the team?

Your choice, per customer. Use one shared account, or have each engineer sign in with their own. Per-engineer accounts keep concurrent logins working and make the audit trail personal.

What happens when someone closes the tab?

The session ends. When the last session for a customer closes, the tunnel is torn down automatically after a short grace period. Nothing stays connected.

Do you record sessions?

Not yet. Every sign-in, connection and session is logged, and recording with playback is on the roadmap.

Is it hosted or self-hosted?

Early access runs as a managed service. Dedicated and self-hosted deployments are being scoped. Tell us what you need when you join the waitlist.

See it on your own customers.

Early access is opening to a small group of MSPs first.