A PiChamber server is a single-owner workspace server. Any client you pair or authenticate can work with its Pi sessions, project files, Git state, and server-side tools.

Keep the server on 127.0.0.1 unless you need remote access. For LAN or reverse-proxy access, set a strong UI password and use a trusted HTTPS or network boundary. Pair only devices you control, and revoke a client when it is no longer trusted. Docker Compose publishes port 32145 on loopback by default, but still requires PICHAMBER_UI_PASSWORD because the server listens on all container interfaces.

PiChamber keeps Pi provider credentials and the Pi agent directory on the server. Browser clients receive session data needed for the workspace, but not stored provider secrets. Do not share pairing links, client tokens, tunnel URLs with credentials, or redacted logs that still contain private content.

See the repository security policy for private vulnerability reports and the reverse proxy guide for live-stream requirements.

These guides are synced from the PiChamber repository at 720cb33 and may lag behind main. Spot something stale? Propose an edit upstream, then re-run npm run sync:docs here.