Installation
Choose how to run PNeX — Raspberry Pi, a Linux server or VM, Windows with WSL 2, or Kubernetes
PNeX runs the same stack everywhere: the PNeX server and its job worker, Rauthy for identity, PostgreSQL, OpenObserve, Valkey and, optionally, RustFS. Pick the target that matches your hardware.
Standalone
Raspberry Pi
Pi 4 or 5, 64-bit OS. One command, memory-tuned profile, served on https://pnex.local.
Linux server or VM
Debian or Ubuntu, amd64 or arm64: bare metal, Proxmox, VirtualBox or a cloud VM.
Windows (WSL 2)
The same installer inside WSL 2, with mirrored networking so devices reach it.
Cluster and cloud
Kubernetes
Helm chart: generated secrets, horizontal scaling, hardened pods.
Cloud providers
Terraform + Ansible recipes for the major clouds.
No domain name? Still HTTPS
Every install is TLS everywhere. On a LAN, PNeX uses <hostname>.local and
its own certificate authority. A public VM without a domain gets a free
wildcard DNS name such as pnex-203-0-113-7.sslip.io, and with it a Let's
Encrypt certificate that every device already trusts. See
Names and TLS.
Which one?
| Raspberry Pi | Linux server / VM | Windows (WSL 2) | Kubernetes | |
|---|---|---|---|---|
| Best for | a workshop, a lab, a home | a permanent site server, a cloud VM | trying PNeX on a PC | many sites, high availability |
| Installer | install.sh | install.sh | install.sh in WSL | helm |
| Day-2 | pnexctl | pnexctl | pnexctl | helm upgrade |
| Scaling | one box | one box | one box | several API replicas |