Documentation
lanowl watches every device on your network, tells you once per incident, and has a local model explain what broke. These pages cover installing it, setting it up for your own network, and living with it. They describe what lanowl does today; what is planned is on the roadmap.
Let an AI assistant write your configuration. You do not need to learn lanowl's YAML. Describe your network to Claude, ChatGPT, Gemini or any assistant, point it at the example files, and it writes
config.yamlandinventory.yamlfor you;lanowl --checktells you both what to fix. Your passwords never leave your machine. How, and the prompt to copy.
The screenshots and messages come from a made-up house played through lanowl's own code: a family home behind a MikroTik with fibre and an LTE backup, and a cabin reached over WireGuard. None of it is a real network.
Getting started
Setting it up
- config.yaml
- Devices: inventory.yaml
- Secrets and logins
- Your router (MikroTik)
- A backup internet line
- Remote sites
- Device kinds of your own
- The model
Using it
- How alerts work
- The dashboard
- Settings: config, devices, the first-run setup
- Telegram commands
- Asking the owl
- Actions and approvals
- Updates, backups and the security review
- Pausing a device
Running it
Reference
- Device kinds and features
- Profiles: operations and parsers
- Command line
- Environment variables
- MQTT topics
- Webhook
- The security model
- Roadmap
Edit this page on GitHub.