Raising your own pen
Hogman is open source. Run it on a server you own and nobody upstream holds your gate: not us, not anyone. Same software as the pens we host.
What you need
- A server running Ubuntu 24.04 with 2 GB of memory and a public IPv4 address. A small cloud server (about $12 a month) is plenty, and one server holds many pens.
- A hostname you control for each pen's control address, such as
hs.example.com, pointed at the server. - A password manager, for the pen's root key once it's off the server.
- Recommended: a free Tailscale account, so you manage the server over your own tailnet and close SSH to the internet. Hogman runs side by side with it.
The short version
# on the server: updates, Docker, firewall, Hogman itself $ curl -fsSL https://hogman.network/install.sh | sudo bash # raise a pen and make yourself its keeper $ hogman-host add mypen hs.example.com $ hogman-host pen mypen member add you --role owner # a one-time link for your laptop $ hogman-host pen mypen device key you personal
Open that link on your laptop and copy the one command. From then on, run the pen from its home page like any other pen (see Running your pen).
The full guide
The keeper's guide goes step by step from an empty server, and covers what the short version leaves out:
- locking SSH down to your own tailnet;
- taking the pen's root key off the server;
- nightly encrypted backups, pulled to a machine you own, and restoring them;
- alerts on your phone when the server or its backups stop;
- updating (under a minute per pen; members stay joined);
- moving a pen to another server (a pen is one folder);
- hosting pens for other people, with a sign-up page and a waiting list.
Already have a hosted pen?
A pen we host is the same software. Ask, and you get your pen's folder (members, names, its certificate authority) to run on your own server. Its control address changes to a hostname of yours, so each member's devices join once more, with a new link, keeping their names.
Something wrong or unclear on this page? Its source is in site/docs-src; issues and fixes welcome.