Paperboat vs Cloudflare Zero Trust

Cloudflare Zero Trust (Access, the WARP client and Tunnel together) puts a company's apps and networks behind Cloudflare, with identity policies and web filtering. Paperboat is a tool for working on your own machines, end to end encrypted, without moving your DNS.

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

Choose Cloudflare Zero Trust when

  • You secure a whole company: web filtering, device posture and app access in one place.
  • Your domains are already on Cloudflare.

Choose Paperboat when

  • You want terminals that survive disconnects, previews and file sending on your own machines.
  • You want your machines to talk to each other directly, encrypted end to end.

Where they differ

A company's perimeter, or your machines

Cloudflare Zero Trust secures a whole company: who may reach which app, from which device, with web filtering and logs.

Paperboat is one install per machine and a sign-in. There is no network, gateway or proxy to plan, and nothing to keep running besides the machines themselves.

Who can read the traffic

With WARP, your traffic goes through Cloudflare, which applies policies and can inspect it.

Paperboat encrypts between your own devices end to end and connects them directly when it can; relays forward traffic they can't read. Only public links end TLS at Paperboat's edge.

Terminals that survive a dropped connection

Access can render SSH in the browser; the session ends when the tab or connection does.

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

Your DNS stays where it is

Public hostnames on Cloudflare need the domain's DNS on Cloudflare.

Paperboat asks for two CNAME records at whichever DNS provider you already use.

Paperboat
$ pb tunnel route add api --name web --to http://127.0.0.1:3000 --wait
$ pb tunnel domain add api api.example.com --route web

Feature by feature

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

Paperboat
Cloudflare Zero Trust

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
Cloudflare Zero Trust: No 1
Shows the output you missed
Paperboat: Yes, replays what you missed on reconnect
Cloudflare Zero Trust: No 1
From a browser
Paperboat: Yes, in the web console
Cloudflare Zero Trust: Yes, browser SSH and RDP 1
Share a live session
Paperboat: Yes, view-only or interactive, by invite
Cloudflare Zero Trust: 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
Cloudflare Zero Trust: Through SSH 2

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
Cloudflare Zero Trust: Yes, short-lived certificates 2
ssh, scp, sftp and rsync
Paperboat: Yes, pb ssh, scp, sftp, rsync and plain ssh
Cloudflare Zero Trust: Yes, through WARP or cloudflared 2
VS Code Remote-SSH
Paperboat: Yes, through generated SSH host names
Cloudflare Zero Trust: As SSH through WARP 2

Files

Send a file to a machine without setting anything up.

Send files to a machine
Paperboat: Yes, pb send, resumes if interrupted
Cloudflare Zero Trust: No 1
An inbox for received files
Paperboat: Yes, an Inbox on each machine
Cloudflare Zero Trust: 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
Cloudflare Zero Trust: No 1
Where they are available
Paperboat: Terminals, pb exec, scripts, plain SSH and VS Code
Cloudflare Zero Trust: 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
Cloudflare Zero Trust: No 1

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
Cloudflare Zero Trust: Through Tunnel, set up in the dashboard 3
See and replay requests
Paperboat: Yes, inspect and replay, in pb and the console
Cloudflare Zero Trust: No 3

Tunnels

A public address for a service that stays the same.

Permanent addresses
Paperboat: Yes, names that stay
Cloudflare Zero Trust: Yes, named tunnels 3
Your own domains
Paperboat: Yes, on every plan
Cloudflare Zero Trust: Yes, on a domain using Cloudflare DNS 4
Protocols
Paperboat: HTTP/1.1, HTTP/2, HTTP/3, WebSocket, raw TCP
Cloudflare Zero Trust: HTTP, HTTPS, TCP, SSH, RDP and more 4

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
Cloudflare Zero Trust: Yes, routed through Cloudflare 5

Encryption

Who could read your traffic on the way.

Between your own devices
Paperboat: End to end; direct when possible
Cloudflare Zero Trust: Through Cloudflare, which can inspect it 5
Public links
Paperboat: TLS ends at Paperboat's edge
Cloudflare Zero Trust: Ends at Cloudflare 3

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
Cloudflare Zero Trust: Yes, seats in your organization 6
Access rules, groups and tags
Paperboat: Yes, a policy file with groups, tags and deny rules
Cloudflare Zero Trust: Yes, identity and device policies 7
Tokens for automation
Paperboat: Yes, scoped API tokens that expire
Cloudflare Zero Trust: Yes, Cloudflare API tokens 8

Self-hosting

Which parts you can run on your own servers.

Run it yourself
Paperboat: Relays and tunnel servers
Cloudflare Zero Trust: The connector only 3

Platforms

Where it runs.

Operating systems
Paperboat: Linux, macOS and Windows; no mobile apps
Cloudflare Zero Trust: Linux, macOS, Windows, iOS, Android, ChromeOS 9

Pricing

How you pay, and what is free.

How you pay
Paperboat: By relay and edge bandwidth; Team per seat
Cloudflare Zero Trust: Per user: $7 a month 10
Free plan
Paperboat: Every feature for personal use, 5 GB a month
Cloudflare Zero Trust: Up to 50 users 10

Pricing

Cloudflare Zero Trust

  • Free: up to 50 users
  • Pay-as-you-go: $7 per user a month
  • Contract plans: by quote

www.cloudflare.com/plans/sase-zero-trust.md, 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 your own machines; keep Zero Trust for company apps and filtering.

Questions

Can Paperboat replace a company VPN?

Not as a whole: it connects the machines it is installed on, not whole networks, and has no web filtering.

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