Self-Hosted (UnoLock Federated Node)
Overview
UnoLock Self-Hosted runs the same vault on a server you control. The UnoLock Federated Node is free, open-source software under the GNU AGPL version 3, with no trial, purchase or paid activation. You run your own node, create Safes on it, and federate with other independently operated nodes.
Your disks, your jurisdiction, your rules. The browser still encrypts everything before it leaves your device, so the node stores and carries encrypted data.
How It Works
- One container: The node ships as one container with the Safe service, the browser app, the admin app, Tor for communication with other nodes, and automatic HTTPS certificate management. You do not need to install Node.js, Tor or a web server on the host.
- Guided setup: On a 64-bit Intel/AMD Linux server with Docker Engine, a guided setup script asks for your hostname, builds the container, and prints the admin URL and a one-time setup code.
- Admin console: You register as administrator with a passkey and PIN, unlock the node, sign the browser client, and manage Safes from the admin console.
- Safe registration codes: You create a Safe registration code for each person, so you can run a node for yourself or invite others to create their own Safes.
- Federation: Safes on your node can exchange private messages and work in Shared Spaces with Safes on other nodes, over Tor. See Federation.
Security Implications
- Client-side encryption stays the same: The browser encrypts Safe contents before sending them to the node. The node stores encrypted data and transports encrypted messages.
- Admin separation: The node administrator cannot reconstruct missing user recovery material.
- Operator responsibility: As the operator, you are responsible for host security, updates, availability, backups and recovery. See Host Security and Backup and Recovery.
- Clear boundaries: The app delivered from your node and the active device remain trusted, and the node processes operational metadata such as sizes, timing and routing. See Security Model.
Use Cases
- Self-hosters: People who already run a home server or VM and want their vault on it.
- Families and teams: One node for everyone, with invites through Safe registration codes.
- Organisations: Data kept on infrastructure the organisation controls.
- Independent communities: A home service of your own that can still share across nodes.
Why It Matters
Self-Hosted means you do not have to depend on any one provider for your vault. You decide where it runs and who can register, and federation means choosing your own node never cuts you off from people on other nodes.
FAQs
How much does Self-Hosted cost?
Nothing. The UnoLock Federated Node is free, open-source software under the GNU AGPL version 3. There is no trial, purchase, license token or paid activation. The prices in Payment & Pricing apply to UnoLock's managed service.
What do I need to run a node?
A 64-bit Intel/AMD Linux server with persistent local storage, Docker Engine, a permanent hostname you control, inbound TCP 80, 443 and 9001, and a current Chromium-family desktop browser with a passkey or security key. See Requirements.
Does TechSologic run or support my node?
No. Independently hosted nodes are operated and maintained by their own operators, not by TechSologic Inc. The documentation is available for self-service. See Operator Responsibilities and Support.
Can I try it before installing it on a server?
Yes. You can run a local test on your own computer at localhost. See Try It on Localhost.
Integration with Other Features
- Federation: Connects your node with other independently operated nodes. See Federation.
- Open Source: The node and its client are open source under the GNU AGPL version 3. See Open Source.
- Shared Spaces: Work in a Space with Safes on other nodes. See Shared Spaces Across Nodes.
- Vault Messaging: Receive Addresses on a node are fixed to that node's onion service. See Receive Addresses and Messaging Across Nodes.