Lokal.so

A tunnel gives a server on your machine a real HTTPS address that anyone can open. Lokal.so covers HTTP, TCP, and UDP, which matters when the thing you're testing is a database port or a socket rather than a web page. Certificates come from the tunnel, so the browser shows a lock instead of a warning.

You name an endpoint once and reuse it, which beats remembering that the API runs on 4000 and the front end on 5173. A short .local address such as my-app.local resolves on the local network over HTTPS, so tablets and phones reach the build through the same name your desktop uses.

Every request that crosses a tunnel lands in a list with headers, body, and timing. You can change a request and send it again, replay a captured response to see how the client copes, or copy a call straight into a bug report. This replaces the separate proxy you'd otherwise keep running.

The app runs an S3-compatible server on top of a folder on your disk. Code that uploads to a bucket talks to it without Docker, without a second daemon, and without a cloud bill. Useful when you're building an upload flow and don't want test objects in production storage.

A JSON payload can be prettified, queried with JMESPath, or converted into a typed model for the language you're using. That last one saves the hand copy of a response into a schema file, which is the step people skip and then regret.

An assistant sits next to the request log. Ask what a response means, have it draft the client code for an endpoint, or get a plain explanation of a header you don't recognize. The vendor lists GPT-4o as the model behind it.

The desktop app exposes a local REST API, and the project publishes clients for JavaScript, Python, Go, PHP, Ruby, Rust, .NET, C++, and Elixir. A Vite plugin, a Webpack plugin for Next.js and other bundlers, and a Laravel artisan command start the tunnel for you.