Host a Zipper Node

A node is the place a room assembles. You don't need to run one to use Zipper — but if you'd rather rooms build in your memory, on your server, this is everything you need.

What it takes

The node itself is one small, hardened container. It holds many rooms at once, writes nothing to disk, keeps no logs, and evaporates every room the moment it empties. Nothing to maintain — it runs or it doesn't.

Where to run it

A node needs very little, so a low-cost VPS covers it. We run our own Zipper nodes on Contabo — their entry Cloud VPS runs about $5 a month* and comes with 4 vCPUs, 8 GB of RAM and 75 GB of NVMe storage. A Zipper node uses a fraction of that, so even the smallest plan has room to spare.

Get a VPS at Contabo
* Approximate — see Contabo for current pricing.

How you set it up

1
Unpack the package on your server One folder: the node, a docker-compose file, an example nginx config, a setup script, and a full README.
2
Run the setup script sh setup.sh builds the container and starts it on loopback. It tells you the two steps it leaves to you.
3
Point a domain and add the reverse proxy Copy the example nginx config, drop in your domain, reload nginx.
4
Turn on HTTPS One certbot command issues a free certificate and switches the node to HTTPS. Done — your node is live.
Download Node Package
Everything above, in one zip. The README walks every step in full — read it before you start.

Public nodes

Status is checked live from your browser when this page loads.

Loading nodes…

Listing your node

Every node has a built-in management page at /manage.html. Open it on your own node and unlock it with the admin key you set as ZIPPER_ADMIN_KEY. Flip the Listed switch on, give the node a name, region and public URL, and save — it announces itself to the directory and appears here within a few minutes.

Flip the switch off and save to delist; the node drops off the list within 15 minutes. No restart, no editing files — you list and unlist yourself, whenever you want.