Written for the person who has to operate it
The parts that prove what this software does are public: both forks, and a map of every change we made to them. The operations handbook comes with a deployment.
Everything we changed, and how to read it.
Shipped with your deployment, whoever runs it.
Deployment
Topology, ports, TLS termination, and the constraint the client's API-address derivation puts on your hostnames — including the misconfigurations that produce no log line at all.
Build and branded clients
Toolchains per target for both Rust applications, and how a client is preconfigured with your server, your key and your login requirement so that nobody ever types an address.
Upgrades and updates
How a fork tracks upstream releases, what happens to the auto-update channel when you own the build, and how to roll a client fleet forward without stranding a device.
Licensing and AGPL compliance
What has to be published when you distribute a modified client, what the About screen must say, and the release checklist that keeps both true on every build.
Need a document before you commit?
Deployment guides, the security model in writing, or the licensing position — ask and we will send the one you need to evaluate this properly.