Skip to content

Guides for tunnels and remote access

Start with one of the two setup guides, or find the guide for your job below.

Tunnels

Give a Local App a Public HTTPS URL

For developers sharing work in progress. Your app gets a persistent HTTPS address with a trusted certificate, and you decide who can open it.

  1. 1 Create a tunnel and copy its command
  2. 2 Start it on the machine running your app
  3. 3 Choose your subdomain
  4. 4 Control who can open it
  5. 5 Serve it on your own domain

Remote Access

Set Up Remote Access to a Device Fleet

For teams with machines on networks they do not control. Each device is reachable over SSH by the people you grant, and every session is recorded.

  1. 1 Create the fleet and add your devices
  2. 2 Run the agent as a service on each device
  3. 3 Grant your team access
  4. 4 Connect over SSH
  5. 5 Review who connected
Start the guide

Remote Access is included in the Pro, Business and Enterprise plans.

Tunnel guides

A public address for something running on your machine.

  • Test Stripe, GitHub and Slack Webhooks Locally

    Point the provider at your tunnel and real events reach the handler on your machine. With Fanout, every teammate receives each one.

    Read the guide
  • Pull Request Previews from Your CI Runner

    Start the tunnel inside the CI job, with the token in a CI secret, and post its URL on the pull request. The address stops answering when the job ends.

    Read the guide
  • Access Your Ollama API from Another Device

    Call a model running on your own hardware from a laptop, a phone or a hosted app, with a header rule in front of it.

    Read the guide
  • Host a Minecraft Server Without Port Forwarding

    Friends join a Java Edition server on your PC at one address. No router changes, and it works behind CGNAT.

    Read the guide
  • Reach Home Assistant and Nextcloud from Anywhere

    Open your self-hosted services away from home, behind CGNAT, with access control on every address.

    Read the guide

Remote Access guides

Private access to devices and services, with a record of every session.

  • SSH into Devices Behind NAT, CGNAT or Firewalls

    Open a shell on a gateway on a cellular link or a server on a customer network with your normal ssh command. No port forwarding or public address.

    Read the guide
  • RDP and VNC Access to Remote Machines

    Open the desktop of a Windows PC or a Linux screen on another network with your usual Remote Desktop or VNC client. The desktop has no public port.

    Read the guide
  • Access PLCs and HMIs Through a Site Gateway

    One gateway on the same local network forwards to equipment that cannot run software, such as a PLC, an HMI or a camera.

    Read the guide
  • Private Access to an Internal Web Dashboard

    Open Grafana, an admin panel or an internal tool in your browser with no public URL and no VPN. Each person is identified, and each session is recorded.

    Read the guide
  • Deploy to Devices from CI Without a Stored Secret

    A CI job proves its identity with OIDC and reaches only the devices you grant it. The repository holds no credential.

    Read the guide
  • Review Who Connected to Each Device

    Every session is recorded with the identity, the device and port, and the source address, and so is each refusal for a missing grant. Export it as CSV for a security review.

    Read the guide

One agent for tunnels and remote access.

A tunnel gives an app on your machine a public address. Remote Access reaches machines on networks you do not control, for the people and machines you grant.