Open Source (AGPL-3.0)
Overview
The UnoLock Federated Node and its bundled web client, including UnoLock Drop, Safe-App and the service worker, are free, open-source software under the GNU AGPL version 3 (AGPL-3.0-only). Audit it, build it, run it.
The source is published at github.com/TechSologic/unolock-federated-node.
How It Works
- No activation: No trial, purchase, license token, renewal or paid activation is required.
- Use, modify, redistribute: You may use, modify and redistribute the software under the AGPL terms.
- Corresponding source: The AGPL terms include corresponding-source requirements for covered distribution and for modified versions that you run as a network service.
- Notices: Preserve applicable copyright, license and third-party notices. Separately licensed dependencies keep their own terms.
- Scope: The license covers the federated-node distribution. It does not relicense the managed UnoLock service, its separately supplied client, or other products.
Security Implications
- Inspectable: Anyone can read the code that encrypts Safe contents in the browser and the code the node runs.
- Reproducible: You can build the node yourself from the published source instead of relying on a prebuilt image.
- Independent of one company: Operators can build and run the node independently and configure their own bootstrap peers.
Use Cases
- Security review: Researchers and organisations can audit the client and node before trusting them.
- Self-hosting: Operators can build and run their own node. See Self-Hosted.
- Contribution: Developers can study, fix and improve the software under the AGPL terms.
Why It Matters
A vault asks for trust. Publishing the node and client under the AGPL means you do not have to take that trust on faith: you can read every line, build it yourself and run it on your own hardware.
FAQs
Is UnoLock's managed service open source too?
The AGPL license covers the federated-node distribution. It does not relicense the managed UnoLock service, its separately supplied client, or other products. For client-side source review of the managed service, see Client Source Access.
Do I have to publish my changes?
The AGPL terms include corresponding-source requirements for covered distribution and for modified versions that you run as a network service. Read the license for the exact obligations.
Can I use the UnoLock name and logo for my node?
Trademarks are covered separately from the software license. See Operator Responsibilities and Support.
Integration with Other Features
- Self-Hosted: The open-source node is how you run UnoLock on your own server. See Self-Hosted.
- Federation: Independent operators running the open-source node form the federation. See Federation.