The path to Phantom XDR.
A transparent, public roadmap. Each phase must be complete, tested, and stable before the next begins. No skipping steps, no shipping broken foundations.
Kernel Driver Restoration & Compilation
All kernel modules exist as written code, but the codebase is in early-draft state. Phase 1 is module-by-module restoration: cleaning up each unit, resolving compilation errors, eliminating kernel-mode security vulnerabilities (pool overflows, use-after-free, null dereferences), and getting the driver to a clean, loadable, Verifier-clean state. Roughly half complete.
User-Space Detection Engines
Core detection infrastructure modules are fully written and working. The data store layer (ThreatIntel, SignatureStore, HashStore, PatternStore) and full Utils library are complete. The remaining work is restoration and integration of the detection engines and the Windows service layer.
Phantom Home & Phantom EDR — Product Split
The shared engine is mature enough to split into two distinct products. This phase defines the repository strategy (monorepo vs. multirepo), extracts the shared core into a common library, and builds product-specific layers on top. Phantom Home targets consumers; Phantom EDR targets enterprise endpoints. Both ship their own agent, UI, and update pipeline.
Phantom XDR
Extend detection and response beyond the endpoint — cloud telemetry correlation, identity signals, network gateway integration, and SIEM connectivity. Phantom XDR correlates signals across multiple data sources into unified attack stories.
Phases 1 and 2 are running in parallel. Kernel restoration and user-space data stores are both active.