Edge Gateway & Runtime Quickstart
Get up and running with CloudyPi in under 5 minutes. Learn how to connect physical Raspberry Pi nodes, AMD64 VPS instances, and route encrypted traffic across our edge Anycast fabric.
1. System Requirements
- Operating System: Linux kernel >= 5.15 with eBPF support enabled (Ubuntu 22.04+, Debian 12+, Alpine 3.19+).
- Architectures: ARM64 (aarch64), AMD64 (x86_64), RISC-V 64.
- Memory: Minimum 512MB RAM (2GB recommended for high-throughput gateway nodes).
- Network: Outbound TCP/UDP ports 443, 80 accessible.
2. One-Line Node Bootstrap
Execute the official node bootstrap agent on your physical or virtual edge host:
#curl -sSL https://cloudypi.cfd/install.sh | sudo bash
[✓] Installing cloudy-edge daemon to /usr/local/bin/cloudypi...
[✓] Initializing cryptographic keypair in /etc/cloudypi/enclave.key...
[✓] Service registered with systemd: cloudypi.service active (running).
3. Joining a Cluster Mesh
Pair the node with your cluster coordinator token:
Pairing Command
#cloudypi node register --coordinator="https://cloudypi.cfd:443" --token="<CLUSTER_SECRET>"
Performing TLS 1.3 mutual handshake...
Successfully joined cluster mesh [IR-TEH-01]. Node ID: cpi-node-7b89f
4. Ingress & TLS Security
All edge traffic routed through CloudyPi ingress endpoints is safeguarded by strict TLS 1.3 forward-secret cipher suites, HSTS preloading, and automated certificate lifecycle rotation. Edge endpoints reject insecure legacy ciphers (SSLv3, TLS 1.0, TLS 1.1) by policy to guarantee cryptographic compliance.