Core EDR
Selected self-hosted agent, server and community components for lab evaluation. Working code is not a production-readiness or vendor-parity claim.
Evaluate the core →Product portfolio
One security system.
Four clearly labeled lanes.
Capability, maturity, licensing and commercial availability are separate questions. This page keeps them separate.
One portfolio, four honest lanes
Different maturity. Different delivery. One shared boundary.
Community, planned limited Free, Pro and negotiated Enterprise describe delivery or contract modes—not equal technical maturity.
AutoXDR
The shared correlation, investigation and supervised-response plane. Autonomous response remains gated and is not a current product claim.
Review the boundary →AI Runtime Security
The market category often called AIDR, implemented as a subordinate AutoXDR profile for AI sessions, tools and artifacts—not a separate autonomous platform.
Read the experiment scope →App Guard
A closed managed commercial service for app-specific Android and future iOS builds. No upload-and-protect workflow, protected APK delivery or GA claim exists today.
See gates and fit →How the pieces fit
Shared evidence, explicit boundaries.
Shared plane
AutoXDR is the common correlation, investigation and supervised-response plane. It is roadmap/pilot scope, not an autonomous operator.
Subordinate AI profile
AI Runtime Security—often called AIDR in the market—uses the AutoXDR evidence and promotion path instead of claiming a separate mature platform.
Component-scoped OSS
Only explicitly published Core EDR component mirrors are open source. Portfolio-wide or blanket OSS claims are inaccurate.
Managed mobile delivery
App Guard is planned as a closed managed commercial service for a specific customer app/build, not a public SDK parity or no-code upload product.