No public IP required
Your serving devices stay private. Outbound HTTPS is the only network requirement — no port forwarding, no NAT punching, no static IP.
Edgible
Run your services on your own hardware. Edgible handles the public internet, the encryption, and the certificates.
Automatic TLS
Edgible provisions and rotates TLS certificates for every public hostname. Bring a custom domain or use a generated one.
Declarative deployments
Describe your application in YAML. edgible stack deploy reconciles the live state. Multi-workload, multi-device, dependency-ordered.
Anywhere Linux runs
A Raspberry Pi in a closet, a beefy workstation, or a VM in someone else’s cloud — if it can run Docker and reach the internet outbound, it’s a candidate serving device.