Why we build on open source
Not on principle, exactly. On the practical grounds that a monitoring stack you cannot inspect or leave is a liability dressed up as a product.
1You can leave
Hand your monitoring to a closed platform and your visibility becomes something you rent. Renewal conversations stop being about value and start being about how much disruption switching would cause — which the vendor also knows. We build on Prometheus, Grafana, OpenSearch, and Wazuh, so the exit is a migration rather than a rebuild.
2The data is yours
Your flow records and logs describe how your business runs. They belong in infrastructure you control, not in a pool where the terms of use decide what else they get used for. Everything runs inside your own tenant.
3It can be audited
A proprietary agent asks you to take its behaviour on faith. Open components can be read — by us, by your security team, by anyone you ask to review them. When a compliance auditor wants to know what a collector does, the answer is a repository rather than a datasheet.
A network you cannot see into is not secure — it is quiet. Those are different things, and only one of them is worth paying for.
The trade-off, stated plainly
Open components need someone to run them well. That work is the service we sell — the software is not where the value is, and pretending otherwise would be the same lock-in with a different label. If you would rather run the stack yourself one day, nothing in how we build it stops you.