Paperboat vs VS Code Tunnels

VS Code Remote Tunnels opens a remote machine in VS Code or vscode.dev through Microsoft's dev tunnels service, and VS Code can forward ports, also publicly. Paperboat works with any terminal, editor or browser, and adds persistent terminals, files, secrets, permanent tunnels and sharing.

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

Choose VS Code Tunnels when

  • You only want to open a remote folder in VS Code.
  • You already sign in to VS Code with GitHub and need nothing else.

Choose Paperboat when

  • You use other editors, plain terminals or agents.
  • You want permanent tunnels, your own domains, sharing with a team, or plain SSH.

Where they differ

One editor, or any tool

Remote Tunnels is built for VS Code: the machine opens in VS Code or vscode.dev, signed in with the same GitHub or Microsoft account on both ends.

Paperboat works with any terminal, editor or agent, including VS Code through plain Remote-SSH.

VS Code Tunnels
$ code tunnel
Paperboat
$ pb devbox
$ ssh devbox.{localDomain}

Terminals that survive a dropped connection

The machine is reachable while VS Code runs there, and one person uses it at a time.

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.

Public links and domains

A forwarded port can be made public, and dev tunnels can keep a stable address on Microsoft's domain; your own domains aren't supported.

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.

VS Code Tunnels
$ devtunnel host -p 3000 --allow-anonymous
Paperboat
$ pb preview 3000

Files, secrets and settings

VS Code syncs its own settings; it has no file sending or encrypted environment variables.

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.

Feature by feature

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

Paperboat
VS Code Tunnels

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
VS Code Tunnels: No; only while VS Code runs there 1
Shows the output you missed
Paperboat: Yes, replays what you missed on reconnect
VS Code Tunnels: No 1
From a browser
Paperboat: Yes, in the web console
VS Code Tunnels: Yes, in vscode.dev 1
Share a live session
Paperboat: Yes, view-only or interactive, by invite
VS Code Tunnels: No, one user at a time 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
VS Code Tunnels: 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
VS Code Tunnels: Signs in with GitHub or Microsoft 1
ssh, scp, sftp and rsync
Paperboat: Yes, pb ssh, scp, sftp, rsync and plain ssh
VS Code Tunnels: No; Remote-SSH is separate 2
VS Code Remote-SSH
Paperboat: Yes, through generated SSH host names
VS Code Tunnels: It is VS Code's own alternative 2

Files

Send a file to a machine without setting anything up.

Send files to a machine
Paperboat: Yes, pb send, resumes if interrupted
VS Code Tunnels: No 1
An inbox for received files
Paperboat: Yes, an Inbox on each machine
VS Code Tunnels: 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
VS Code Tunnels: No 1
Where they are available
Paperboat: Terminals, pb exec, scripts, plain SSH and VS Code
VS Code Tunnels: 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
VS Code Tunnels: VS Code settings sync only 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
VS Code Tunnels: Yes, a forwarded port made public 3
See and replay requests
Paperboat: Yes, inspect and replay, in pb and the console
VS Code Tunnels: In browser DevTools; no replay 4

Tunnels

A public address for a service that stays the same.

Permanent addresses
Paperboat: Yes, names that stay
VS Code Tunnels: Yes, persistent dev tunnels 5
Your own domains
Paperboat: Yes, on every plan
VS Code Tunnels: No 5
Protocols
Paperboat: HTTP/1.1, HTTP/2, HTTP/3, WebSocket, raw TCP
VS Code Tunnels: HTTP, HTTPS, WebSocket 5

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
VS Code Tunnels: No 1

Encryption

Who could read your traffic on the way.

Between your own devices
Paperboat: End to end; direct when possible
VS Code Tunnels: End to end (SSH inside the tunnel) 1
Public links
Paperboat: TLS ends at Paperboat's edge
VS Code Tunnels: TLS ends at Microsoft's service 6

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
VS Code Tunnels: Share with a tenant or GitHub org 5
Access rules, groups and tags
Paperboat: Yes, a policy file with groups, tags and deny rules
VS Code Tunnels: Per tunnel and port 5
Tokens for automation
Paperboat: Yes, scoped API tokens that expire
VS Code Tunnels: Yes, tunnel tokens (24 hours) 6

Self-hosting

Which parts you can run on your own servers.

Run it yourself
Paperboat: Relays and tunnel servers
VS Code Tunnels: No; the relay runs on Azure 7

Platforms

Where it runs.

Operating systems
Paperboat: Linux, macOS and Windows; no mobile apps
VS Code Tunnels: Where VS Code Server runs 1

Pricing

How you pay, and what is free.

How you pay
Paperboat: By relay and edge bandwidth; Team per seat
VS Code Tunnels: Free, with usage limits 8
Free plan
Paperboat: Every feature for personal use, 5 GB a month
VS Code Tunnels: 10 tunnels, 5 GB a month per user 8

Pricing

VS Code Tunnels

  • Free with a GitHub or Microsoft account
  • Dev tunnels limits: 10 tunnels and 5 GB a month per user

learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits, 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. Connect VS Code with Remote-SSH to the generated host name.
  3. Move public ports to pb preview or a tunnel.

Questions

Does VS Code Remote-SSH work with Paperboat?

Yes. Paperboat generates SSH host names; pick one in Remote-SSH and it connects with keys handled.

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