The network
that powers it all.
Run a Zippytal Node on any machine you have lying around. Laptop, Pi, old ThinkPad, VPS. You become the infrastructure behind Meet, Chat, Community, and Drive.
Runs anywhere
From a $35 Pi to a 96-core bare metal. The same binary. Same config.
Modular services
Enable only what you need. Ship custom services as WASM modules.
Encrypted by default
Noise protocol transport. Identity via ed25519. No plaintext on the wire.
Federated discovery
DHT-based peer discovery. Optional rendezvous relays. NAT-friendly.
Ludicrous mode
io_uring, QUIC, zero-copy paths. Designed to saturate a gigabit link.
Open service registry
Install community services with a single command. Signed. Sandboxed.
Architecture
Four layers.
One elegant daemon.
Every Zippytal service is a module that plugs into the same core. That's why Meet can stream video through the same transport that Drive uses for file shards, and Chat uses for messages. One network. One identity. One install.
Services
meet · chat · community · drive · your-app
Runtime
WASM sandbox · signed modules · per-service quotas
Protocol
libzippy · noise · QUIC · DHT · federation
Kernel
storage · identity · scheduler · telemetry (opt-in)
Run anywhere
If it has a CPU and a network cable,
it can host a Zippytal Node.
Linux
x86_64 · aarch64
macOS
Intel · Apple Silicon
Windows
11 · Server 2022
Raspberry Pi
3 · 4 · 5
Docker
compose · swarm · k8s
NAS
Synology · unRAID · TrueNAS