Technology
The foundations we build on
We don't hide our stack. These are the open-source foundations behind Cairn's services — chosen because you can audit them, host them, and own them.
01 The stack
| Technology | Role at Cairn | Why it earns its place |
|---|---|---|
| Wazuh | SIEM / XDR — detection & response | Open detection rules you can read and own; strong on file integrity, log analysis, and compliance mapping. |
| OpenSearch | Log storage & search | Scalable, open analytics behind the SOC; no per-ingest licensing surprises. |
| Zabbix | Infrastructure monitoring | Full-estate visibility with no per-metric licensing; mature, battle-tested. |
| pfSense / OPNsense | Firewall & perimeter | Inspectable, self-hostable perimeter; no opaque appliance firmware. |
| Ansible | Automation & hardening | Configuration and hardening as reviewable, version-controlled code; CIS/STIG at scale. |
| GLPI | Asset management, CMDB, ITSM | One auditable record of every asset and change — the backbone of accountability. |
| Grafana Complementary | Visualisation | Clear dashboards over open data sources. |
| Suricata Complementary | Network IDS / IPS | Open, high-performance traffic inspection. |
02 The trade
Why not just resell a platform?
Reselling a proprietary suite is easier for us and worse for you: you inherit lock-in, foreign control, and a black box your auditors are increasingly unwilling to accept.
Building on open foundations is more work for Cairn and more value for you. That trade is the whole point.
03 Everything as code
Everything as code
Detection rules, firewall policy, and hardening baselines live in version control.
- Every change is reviewed and attributed
- Every change is dated and reversible
- Every change is auditable without an archaeology project
- The platform is documented by construction, not by afterthought
04 Exceptions
When we go proprietary
Occasionally the open option genuinely isn't the right one — a specialised requirement, a certification constraint, an integration that only exists commercially. When that happens we choose the best tool, integrate it cleanly, and record why in writing.
Default open; honest about exceptions.