Skip to content

Using NativePi

Browser access

NativePi can present the running desktop workspace in a browser. Access is off until you start it and ends when you stop it or close the app.

Local network access

Start local access from NativePi to open an HTTP and WebSocket server on this computer. The generated link includes an access token and can be opened by another device that can reach the machine over the local network.

Your firewall, router, and VPN determine which devices can connect. NativePi does not make the local address reachable through the internet on its own.

Temporary public access

Start public access to create a throwaway Cloudflare quick tunnel to the same local server. NativePi shows the generated address and closes the tunnel after twelve hours at the latest. It does not register a permanent hostname or operate a hosted relay.

Access token

Local and public links use the same token. Treat a copied link or QR code as a credential: anyone who receives it can use the exposed workspace while the server is running. Replacing the token invalidates every link issued with the old value.

NativePi shows connected devices, the route they used, and the links this window has copied or displayed. Stop access when the other device no longer needs it.

Availability

The desktop app must remain open. Quitting NativePi ends the server, active browser sessions, and any public tunnel. The quit confirmation reports connected browser clients before closing them.