Introduction

Jetty is a tunneling service that gives your laptop a public HTTPS URL so teammates, devices, and third-party webhooks can reach apps you run on localhost. Traffic is encrypted to the edge; the CLI (or PHP client) maintains an outbound connection—no inbound firewall rules on your machine.

The fastest path is to create an account, mint an API token in Bridge, and use Jetty’s hosted control plane and edge. You get automatic TLS, ephemeral or stable hostnames under your tunnel domain, teams and organizations, and a web dashboard to inspect traffic.

If you self-host the Laravel app and jetty-edge, you control DNS, regions, and verification—at the cost of running TLS terminators, wildcard certificates, and edge processes yourself. Operators can follow the in-app guide Network and edge deployment (signed-in users).

Jetty ships a Go CLI (jetty + jetty-edge for WebSocket forwarding), a PHP client (jetty/client Composer package or PHAR), and the Bridge dashboard. The CLI and Bridge both help you see requests, debug integrations, and copy replay-friendly details.

Ready to install? Continue to Installation, then Sharing local sites for jetty share patterns (by port, upstream host, and subdomain). Or create an account and open Bridge → Getting started for copy-paste commands against this deployment.