Paperboat vs Twingate

Twingate gives a company's people access to private resources without a VPN, through connectors you deploy and policies tied to your identity provider. Paperboat is for working on machines directly: terminals, SSH, files, secrets, previews and tunnels.

Checked against Twingate's own documentation and pricing, November 2026. Sources are listed under the table.

Choose Twingate when

  • You run a company network and need people to reach internal resources with device checks.
  • You want access policies tied to your identity provider for many users.

Choose Paperboat when

  • You want to work on your own machines from anywhere, with terminals and files.
  • You want public previews and permanent tunnels.

Where they differ

People to resources, or machines to each other

Twingate connects users' devices to resources in private networks through connectors; it is built for giving employees access.

Paperboat connects the machines you install it on to each other, and lets you work on them from anywhere.

Terminals that survive a dropped connection

Twingate's Privileged Access for SSH signs SSH connections with short-lived certificates; the session ends with the connection.

Paperboat terminals run on the machine and keep running when your laptop sleeps or the network drops. When you come back, from the same computer, another one or a browser, you see what happened while you were away, and you can let someone watch or type along.

Paperboat
$ pb devbox

Public links

Twingate only makes resources reachable privately.

pb preview gives a port a public HTTPS link in one command, and pb tunnel keeps a permanent address with your own domain, on every plan.

Paperboat
$ pb preview 3000

Files, secrets and settings

Twingate moves files over SFTP or rsync and has no environment variables or config sync.

pb send puts files in the other machine's Inbox, resuming if the connection drops. ENV delivers encrypted variables to the commands and terminals that need them, and config sync keeps settings the same everywhere from a Git repository.

Paperboat
$ pb send report.pdf --to laptop

Feature by feature

Every answer in the Twingate column carries a number that links to the page of theirs that says it. Put a second tool beside it

Paperboat
Twingate

Terminals

A shell on your machine that you can leave and come back to.

Keeps running when you disconnect
Paperboat: Yes, sessions keep running on the machine
Twingate: No 1
Shows the output you missed
Paperboat: Yes, replays what you missed on reconnect
Twingate: No 1
From a browser
Paperboat: Yes, in the web console
Twingate: No 1
Share a live session
Paperboat: Yes, view-only or interactive, by invite
Twingate: No 1

Remote commands

Run one command on another machine and get its output and exit code.

Run a command on another machine
Paperboat: Yes, pb exec, with exit codes
Twingate: Through SSH 1

SSH

Use ssh and the tools built on it, without managing keys or opening ports.

Keys handled for you
Paperboat: Yes, keys and host trust handled
Twingate: Yes, short-lived certificates (Privileged Access) 1
ssh, scp, sftp and rsync
Paperboat: Yes, pb ssh, scp, sftp, rsync and plain ssh
Twingate: Yes, ssh, sftp and rsync 1
VS Code Remote-SSH
Paperboat: Yes, through generated SSH host names
Twingate: As SSH to a resource 1

Files

Send a file to a machine without setting anything up.

Send files to a machine
Paperboat: Yes, pb send, resumes if interrupted
Twingate: Through sftp or rsync 1
An inbox for received files
Paperboat: Yes, an Inbox on each machine
Twingate: No 1

Environment variables

The secrets your programs need, delivered to the machine that runs them.

End-to-end encrypted variables
Paperboat: Yes, end-to-end encrypted
Twingate: No 2
Where they are available
Paperboat: Terminals, pb exec, scripts, plain SSH and VS Code
Twingate: n/a

Config sync

The same settings on every machine, from a repository you control.

Settings from a Git repository
Paperboat: Yes, from your Git repository
Twingate: No 2

Previews

A public link to a port on your machine, for as long as you need it.

Public link in one command
Paperboat: Yes, pb preview 3000
Twingate: No 2
See and replay requests
Paperboat: Yes, inspect and replay, in pb and the console
Twingate: No 2

Tunnels

A public address for a service that stays the same.

Permanent addresses
Paperboat: Yes, names that stay
Twingate: No, private resources only 3
Your own domains
Paperboat: Yes, on every plan
Twingate: Private names only 3
Protocols
Paperboat: HTTP/1.1, HTTP/2, HTTP/3, WebSocket, raw TCP
Twingate: TCP, UDP and ICMP, privately 3

Private network

Your machines reach each other's ports without exposing them.

Machines reach each other
Paperboat: TCP ports and private names; not a full network
Twingate: People reach resources, not machines each other 3

Encryption

Who could read your traffic on the way.

Between your own devices
Paperboat: End to end; direct when possible
Twingate: End to end, client to connector 4
Public links
Paperboat: TLS ends at Paperboat's edge
Twingate: n/a

Teams and access

Working with other people, and deciding who may do what.

Members and roles
Paperboat: Yes, five roles; SSO and SCIM from 10 seats
Twingate: Yes, users and admin roles 5
Access rules, groups and tags
Paperboat: Yes, a policy file with groups, tags and deny rules
Twingate: Yes, groups, policies and approvals 5
Tokens for automation
Paperboat: Yes, scoped API tokens that expire
Twingate: Yes, API tokens 6

Self-hosting

Which parts you can run on your own servers.

Run it yourself
Paperboat: Relays and tunnel servers
Twingate: Connectors only 7

Platforms

Where it runs.

Operating systems
Paperboat: Linux, macOS and Windows; no mobile apps
Twingate: Linux, macOS, Windows, iOS, Android, ChromeOS 8

Pricing

How you pay, and what is free.

How you pay
Paperboat: By relay and edge bandwidth; Team per seat
Twingate: Per user: $5 or $10 a month 9
Free plan
Paperboat: Every feature for personal use, 5 GB a month
Twingate: Starter: 5 users 9

Sources

What each product does, from its own documentation, as of November 2026. “No” means its documentation describes no such feature. Found something out of date? The other product's page wins; tell us and we fix ours.

Pricing

Twingate

  • Starter: free, up to 5 users
  • Teams: $5 per user a month (yearly)
  • Business: $10 per user a month (yearly)
  • Enterprise: by quote

www.twingate.com/pricing, November 2026

Paperboat

  • Free: $0, every feature for personal use, 5 GB of relay and edge bandwidth a month
  • Pro: $8 a month or $80 a year, 100 GB
  • Team: $15 per seat a month or $150 a year, 100 GB per seat; 14-day trial
  • Direct traffic between your machines is never counted

Paperboat pricing in full

Switching

  1. Install Paperboat on each machine with the one-line installer and sign in.
  2. Use Paperboat for access to your own machines; keep Twingate for company resources.

Questions

Does Paperboat check devices before giving access?

Access is per signed-in account and machine; device posture checks are not part of Paperboat.

Start with the machine in front of you

Install Paperboat here, then on a second machine. Free for personal use, no card needed.

$ curl -fsSL https://get.pprbt.dev/install | bash
> irm https://get.pprbt.dev/install.ps1 | iex