Paperboat vs ngrok

ngrok puts a local service on a public URL, with traffic tools such as a request inspector and policies. Paperboat does previews and permanent tunnels too, and it also gives you terminals, SSH, files and secrets on the same machines.

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

Choose ngrok when

  • You only need public URLs, with traffic features such as policies, load balancing and an API gateway.
  • You want traffic policies, OAuth or rate limiting in front of your app, or an inspector that is always recording.

Choose Paperboat when

  • You also want to reach and work on the machine itself.
  • You want your own domains and permanent tunnels on a free plan.

Where they differ

A port, or the whole machine

ngrok is built for one thing: getting traffic to a service. It doesn't give you a shell, files or secrets on the machine behind it.

Paperboat gives you the link and the machine: open a terminal on it, copy files to it, run a command, from your laptop or a browser.

ngrok
$ ngrok http 3000
Paperboat
$ pb preview 3000

Your own domains

On ngrok, bringing your own domain starts at the Pay-as-you-go plan; Free has one development domain and Hobbyist ngrok-branded ones.

Paperboat tunnels take your own domains on every plan, including Free, with the DNS records shown for you and the certificate issued automatically.

ngrok
$ ngrok http 3000 --url api.example.com
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

Request inspection

ngrok's traffic inspector shows each request and lets you replay it; that is one of its strongest features.

Paperboat records requests on your own machine once you turn capture on, and lists and replays them from pb or the console, on every plan. ngrok's inspector is always on and keeps traffic for 24 to 72 hours depending on the plan, which is handier when you did not know you would need it.

How you pay

ngrok plans add charges per user, per active domain hour and for data and requests beyond what is included.

Paperboat plans differ only in bandwidth through its relays and edges; previews, tunnels and domains have no separate charges, and direct traffic between your machines is free.

Feature by feature

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

Paperboat
ngrok

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
ngrok: No 1
Shows the output you missed
Paperboat: Yes, replays what you missed on reconnect
ngrok: No 1
From a browser
Paperboat: Yes, in the web console
ngrok: No 1
Share a live session
Paperboat: Yes, view-only or interactive, by invite
ngrok: 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
ngrok: No 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
ngrok: No 1
ssh, scp, sftp and rsync
Paperboat: Yes, pb ssh, scp, sftp, rsync and plain ssh
ngrok: Only as a TCP endpoint 1
VS Code Remote-SSH
Paperboat: Yes, through generated SSH host names
ngrok: No 1

Files

Send a file to a machine without setting anything up.

Send files to a machine
Paperboat: Yes, pb send, resumes if interrupted
ngrok: No 1
An inbox for received files
Paperboat: Yes, an Inbox on each machine
ngrok: 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
ngrok: No 1
Where they are available
Paperboat: Terminals, pb exec, scripts, plain SSH and VS Code
ngrok: 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
ngrok: 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
ngrok: Yes, ngrok http 3000 2
See and replay requests
Paperboat: Yes, inspect and replay, in pb and the console
ngrok: Yes, traffic inspector with replay 2

Tunnels

A public address for a service that stays the same.

Permanent addresses
Paperboat: Yes, names that stay
ngrok: Yes, a fixed dev domain; more on paid plans 3
Your own domains
Paperboat: Yes, on every plan
ngrok: Yes, from Pay-as-you-go 4
Protocols
Paperboat: HTTP/1.1, HTTP/2, HTTP/3, WebSocket, raw TCP
ngrok: HTTP, HTTPS, TCP, TLS 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
ngrok: No 1

Encryption

Who could read your traffic on the way.

Between your own devices
Paperboat: End to end; direct when possible
ngrok: n/a
Public links
Paperboat: TLS ends at Paperboat's edge
ngrok: TLS ends at ngrok; end-to-end TLS optional 5

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
ngrok: Yes, users from Pay-as-you-go 4
Access rules, groups and tags
Paperboat: Yes, a policy file with groups, tags and deny rules
ngrok: IP policies; roles as a paid add-on 4
Tokens for automation
Paperboat: Yes, scoped API tokens that expire
ngrok: Yes, API keys 4

Self-hosting

Which parts you can run on your own servers.

Run it yourself
Paperboat: Relays and tunnel servers
ngrok: No 1

Platforms

Where it runs.

Operating systems
Paperboat: Linux, macOS and Windows; no mobile apps
ngrok: Linux, macOS, Windows, FreeBSD, Docker 6

Pricing

How you pay, and what is free.

How you pay
Paperboat: By relay and edge bandwidth; Team per seat
ngrok: Plan plus usage: $10 or $20 a month 4
Free plan
Paperboat: Every feature for personal use, 5 GB a month
ngrok: 3 endpoints, 1 GB out, 20k requests 4

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

ngrok

  • Free: $0, 3 endpoints, 1 GB out, 20,000 requests a month
  • Hobbyist: $10 a month, 5 GB, ngrok-branded domains
  • Pay-as-you-go: $20 a month plus usage; your own domains
  • Enterprise: by quote

ngrok.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. Replace ngrok http <port> with pb preview <port> for short-lived links.
  3. For lasting addresses, create a tunnel and move your domain's CNAME record to it.
  4. Stop the ngrok agent once nothing points at it.

Questions

Does Paperboat support WebSockets and HTTP/2?

Yes: HTTP/1.1, HTTP/2, HTTP/3 and WebSocket go through previews and tunnels.

Can I keep a preview private?

Yes. A preview can be public, only for you, or for your team.

Does Paperboat have raw TCP endpoints?

Public links are for web traffic (HTTP and WebSocket). For other protocols, your own machines reach each other's ports privately.

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