pi@piper
the paas that runs on hardware you own

Deploy to your own box
with one git push.

Open-source, developer-first, zero-trust. Piper turns any box you own into a real deploy target with a public HTTPS URL — a cloud VM, an old laptop, a home server, even a Raspberry Pi behind CGNAT — without exposing your network to anyone, including the relay.

$curl -fsSL https://get.openpiper.dev/install.sh | sh
why piper

Self-hosting without the tradeoffs

Zero-trust relay

The relay only ever sees ciphertext — L4 SNI passthrough, TLS terminates on your box. Route through a relay you don’t own, safely.

Lean by design

SQLite for state, embedded Caddy for TLS, one lightweight daemon. No Kubernetes, no sprawl — light enough to run on a Pi, happy on anything bigger.

Developer-first

A scriptable CLI and a full-screen TUI, Dockerfile-based builds, and git-push deploys. On the box itself, no login needed.

the relay

Public traffic, private network

TLS terminates on your box; the relay splices ciphertext by SNI over an outbound tunnel — so it works behind CGNAT and never sees plaintext.

visitors & cli
https://app.you.dev
HTTPS →
piper-relay · cloud
SNI passthrough — ciphertext only
← tunnel(CGNAT)
your box · piperd
Docker · Caddy · TLS ends here
how it works

Three commands to a live URL

step 01
$ piper connect

Enroll your box on the public relay (or your own). One outbound tunnel, no ports opened.

step 02
$ piper app link myapp --repo owner/name

Link a repo through your own per-user GitHub App — the private key never leaves your box.

step 03
$ git push

Builds the Dockerfile, health-checks the container, and publishes it live at https://myapp.your-domain.

Every push builds your Dockerfile, health-checks it, and serves it at your domain.