About Latchbox
A small tool for a small, recurring problem: home routers and home files that quietly go unbacked up.
Why it exists
Home routers hold configuration that took real effort to get right — port forwards, VLANs, NAT rules, static leases — and most of them have no built-in way to keep history of it. A firmware update or a factory reset wipes it out. At the same time, general-purpose backup tools are built around pushing everything to someone else's cloud, which is more than most home setups need or want.
Latchbox does one narrow job: snapshot router configs and copy local files, on a schedule, onto storage the user already owns.
Who maintains it
A small group of people who use the tool on their own networks and maintain it in their spare time. There is no company behind it and no roadmap driven by anything other than what the maintainers and contributors need.
Principles
Local-first
Backups stay on disk or on a NAS the user controls. Latchbox has no cloud component and does not talk to any remote service.
Simplicity
One binary, one config file. Features that would need a second daemon or a database are left out.
No telemetry
Latchbox does not phone home, does not check for updates on its own, and does not collect usage data.
Version history
| Version | Date | Notes |
|---|---|---|
| 0.1.0 | 2023-02 | Initial CLI, Keenetic config backup only. |
| 0.2.0 | 2023-05 | Added local file backup mode. |
| 0.3.0 | 2023-09 | Added MikroTik support. |
| 0.4.0 | 2024-01 | Added the local web interface. |
| 0.5.0 | 2024-07 | Added OpenWrt and TP-Link support, integrity checks. |
| 0.6.0 | 2025-02 | Rewrote snapshot storage around versioning. |
| 0.6.4 | 2025-11 | Bug fixes, NAS destination handling. |
License
Latchbox is released under the MIT license. The full license text ships with the source and with every release archive.
Contributing
Bug reports, support for additional router vendors, and documentation fixes are all welcome. Open an issue or a pull request in the repository to get started.