When you buy a device, you should be able to keep using it, repair it, and know what it does. Too often that is not how it works. Some products stop working when the maker turns off a server. Some need the maker’s permission before a replacement part works. Some keep working only while a subscription is paid.
For a security device that sits on your internet connection, this matters more than usual. You should be able to see how it works, and it should keep protecting you whatever happens to the company that sold it.
The right-to-repair movement argues that if you bought something, you should be able to repair it, or have it repaired where you choose. Laws are starting to follow:
- European Union. Directive (EU) 2024/1799, of 13 June 2024, requires manufacturers to repair goods that are covered by EU repairability requirements, and to offer spare parts at a reasonable price. Member states must apply it from 31 July 2026.
- Oregon, United States. Oregon’s right-to-repair law, SB 1596, passed in 2024, requires manufacturers to make repair manuals, tools and parts available, and bans software-based parts pairing for devices made after 1 January 2025 (Repair.org). Parts pairing is when a replacement part does not work until the manufacturer’s software approves it.
¶ Open and Closed, Side by Side
- The XZ Utils backdoor (2024). On 29 March 2024, Andres Freund reported a backdoor in the release files of xz 5.6.0 and 5.6.1, a compression library used across Linux. He noticed it after “a few odd symptoms around liblzma”, such as SSH logins using a lot of CPU. Because the code was open, he could trace it, and Linux distributions could check and fix their own builds.
- CrowdSec. CrowdSec’s engine, and the parsers and scenarios on its hub, are open source. You can read exactly how an attack is detected before you trust a ban. The Defend-O-Tron’s threat detection is built on it.
- Insteon (April 2022). The smart-home company shut down its servers without telling its customers. The app and the hub’s automation stopped working. The physical switches still worked, and because the devices’ protocol had been reverse-engineered, open-source software could still control them.
- Cisco Meraki. Cisco’s own Meraki licensing FAQ says that on its Co-Term and PDL licensing, when a licence is not renewed, the hardware “will be non-operational” and “your network products will no longer allow traffic to pass to the Internet.”
Closed devices work well while the vendor’s plans match yours. Open ones leave you a way forward when they don’t.
- Open where it counts. The V100’s board schematics, board layout and pinouts are published. The V200’s hardware design is not open source, but its firmware is: it runs Dasharo instead of a closed BIOS. See Open Source Hardware.
- Open-source software. The firmware is built from open-source software: Debian, the Linux kernel, CrowdSec, Suricata, AdGuard Home, Traefik and VictoriaMetrics. See Open Source Licences.
- No cloud kill switch. The protection runs on the device. Firmware updates and remote support use the Awesome-O console, but detection, the firewall, DNS filtering, the dashboards and the audit evidence do not depend on it. If our company disappeared, your Defend-O-Tron would keep protecting your network. That is a design decision, not a promise.
- No licence to keep it protecting. The device protects your network without a licence or subscription. Firmware updates are available when they are published. Support is a separate, paid service.
- Replaceable parts. The NVMe SSD and the power supply are standard parts you can replace. The device’s identity with the Awesome-O console is tied to its management port, so after a board or network-chip swap, Awesome-O support issues the identity again. See Enrollment.
- Recovery you control. A V100 can run from an SD card, using its MASK ROM button. A V200 reinstalls from a USB installer. See Recovery and Reinstall.
- End of life. When the hardware reaches the end of support, we intend to publish the final firmware and what you need to keep the device running on your own.
Someone has to design the hardware, build and test the firmware, answer support requests and run the update servers. The Defend-O-Tron is sold as a product, and support is a paid service, because that is what pays for this work.
What “open” means here is that the device has no hidden levers: you can see what it runs, keep it running without us, and repair it.
- The CrowdSec community. Every Defend-O-Tron reports the attackers it bans to the CrowdSec community, and uses the community blocklist in return. See The CrowdSec Community for exactly what a report contains.
- Public documentation. This wiki, so that you never have to reverse-engineer what the device does.