Documents
DaemonEye Product Requirements Document
DaemonEye Product Requirements Document
Type
External
Status
Published
Created
Apr 18, 2026
Updated
Apr 26, 2026
Updated by
Dosu Bot
Source
View

⚠️ This page has been superseded.
The canonical DaemonEye Product Requirements Document moved on 2026-04-25 to a consolidated document covering the entire product suite (Community + Business + Enterprise tiers).
See: DaemonEye Product Requirements Document (v1.0)
The content below is preserved for historical reference. Do not update this page; make changes on the new PRD instead.


Historical content (preserved as of 2026-04-25)#

DriverKen Melton
ApproverKen Melton
ContributorsKrystal Melton
InformedTBD
ObjectiveDeliver silent, sovereign observability for defenders in restricted or air-gapped environments — replacing traditional EDR/XDR tools with a stealth platform that operates entirely under the customer's control.
Due datev1.0.0 target: 2026-10-09
Key outcomesContinuous local observability of processes and network activity. Zero-egress telemetry model (customer sees all, shares nothing). Signed audit chains with forensic fidelity. Scalable proxy tree architecture without cloud backend. Fully operational in air-gapped or restricted environments.
StatusSuperseded

Vision#

DaemonEye provides silent, sovereign observability for defenders in restricted or air-gapped environments. It enables organizations to watch from the shadows — tracing attacker behavior across systems without tipping off the adversary. Every endpoint becomes a stealth honeypot; every process chain a forensic record.

"We watch from the shadows, and our eyes never close."

PrincipleDescription
No cloud, no leaksAll telemetry stays under customer control
Observe, don't disruptHuman-in-the-loop tracing and containment
Audit, don't guessEvery action is signed and verifiable
Local-first architectureWorks entirely offline or within enclaves
Design origin: ShadowHunt Concept

Problem statement#

Traditional EDR/XDR tools depend on continuous connectivity, vendor-controlled cloud analytics, and active remediation logic. These traits make them unusable in classified, air-gapped, or compliance-restricted environments.
Organizations need a quiet, controlled hunt and response capability that delivers:

  • Full process and network visibility across enclaves
  • Forensic traceability with cryptographic integrity
  • Human-controlled escalation without automated disruption
    DaemonEye fills this gap by replacing external telemetry with internal trust — sovereign detection and forensics under the operator's control.

Target users and environments#

  • Defense, intelligence, and research networks
  • Critical infrastructure and industrial control systems
  • Incident response teams in sovereign or isolated environments
  • Red/blue exercises requiring covert visibility

Scope#

Must have:Local process and connection collection (PID, PPID, cmdline, hash, IP tuples). Rule engine for heuristic detections (SQL-based queries). TraceCommand: focused tracing on process lineage upon trigger. Signed audit ledger with per-event verification. Multi-proxy store-and-forward architecture for scale. Security Center web UI for alerts, traces, and forensic timeline. Export capability for signed forensic packages. mTLS-only connections using customer-owned certificates. Store-and-forward WAL design (agents never push to the internet).
Nice to have:Federation across multiple Security Centers. Kernel-level telemetry (eBPF, ETW, EndpointSecurity). Behavioral analytics and drift correlation. Compliance mapping (NIST, ISO, CIS). STIX/TAXII threat intel exchange (offline sync). SSO/LDAP and advanced RBAC.
Not in scope:Cloud-hosted analytics or vendor-managed telemetry. Automated remediation or active response (observe-only philosophy). Antivirus or signature-based malware detection. Outbound telemetry or data exfiltration to external services.

Key differentiators#

DomainDaemonEye Advantage
Data SovereigntyNo outbound telemetry; all operations within customer enclave
Stealth OperationSilent rules and trace commands undetectable to adversaries
Focused ForensicsTrace-by-lineage, not bulk telemetry dumps
Scalable ArchitectureFanout-style proxy tree (Agents -> Proxies -> Security Center)
Audit IntegrityEd25519-signed logs with immutable ledger
Offline OperationFully functional in disconnected or classified environments

Architecture overview#

Components#

ComponentFunction
Agent (Procmond)Captures process, file, and network metadata locally
Proxy Node (PX)Store-and-forward buffer for agents; batches and compresses data to Security Center
Security Center (SC)Central management and correlation point. Runs the rule engine, handles trace commands, and aggregates audit logs

Communication model#

  • mTLS-only connections using customer-owned certificates
  • Store-and-forward WAL design: agents never push to the internet
  • Cross-host tracing: SC links process chains across hosts using shared trace IDs

Non-functional requirements#

CategoryTarget
Performance<5% CPU utilization, <100 MB RAM per host
Latency<1s event propagation within enclave
Scalability500 agents per proxy node; horizontal scaling supported
SecuritymTLS, customer PKI, signed rule packs
AuditabilityAll operator actions signed and recorded
AvailabilityOffline survivability via WAL; resilient to link outages

Licensing model#

DaemonEye offers two paid tiers and a community edition (non-commercial DIY build).

TierUse CaseFeaturesPricing
BusinessSingle Security Center, moderate fleetGUI, proxy tree, curated rule packs, connectorsPer-site license (TBD)
EnterpriseMulti-site federation, regulated environmentsAll Business + federation, kernel telemetry, compliance, SSO, SLA supportCustom pricing (TBD)
CommunityNon-commercial DIYAgent, CLI rule engine, single nodeFree / Apache 2.0
  • Community edition is not a paid tier; it serves ecosystem and visibility goals
  • Licensing remains perpetual (no subscription required). Optional annual maintenance (updates/support) may be offered
  • Each tier enforces scale and feature boundaries (number of endpoints, federation, compliance modules)

Risks and mitigations#

RiskMitigation
Government or large buyers purchase Business tierEnforce scale and feature caps contractually; define clear upgrade triggers
Brand unfamiliarityEarly-adopter discount in exchange for references; publish transparent design and audits
Support overheadBuffer baked into pricing; optional paid support add-on
Customer data sensitivityZero-egress policy and cryptographic audit chain
Feature creepStrict MVP roadmap, modular design

Timeline#

PhaseDescription
Phase 1 — Shadow-Hunt MVP (Q1)Agent, Proxy, Security Center, tracing demo
Phase 2 — Business (Q2)GUI, proxy scaling, rule packs, connectors
Phase 3 — Enterprise (Q3-Q4)Kernel telemetry, federation, compliance modules

Milestones and deadlines#

MilestoneOwnerDeadlineStatus
Linux agent with process collectionKen MeltonQ1 2026In Progress
Proxy node with WAL, compression, and replayKen MeltonQ1 2026Not Started
Security Center backend + minimal UIKen MeltonQ2 2026Not Started
TraceCommand and audit signingKen MeltonQ2 2026Not Started
Cross-host trace demo (Apache->bash->ssh)Ken MeltonQ2 2026Not Started
Enterprise: kernel telemetry and federationKen MeltonQ3-Q4 2026Not Started
v1.0.0 releaseKen Melton2026-10-09Not Started

Messaging and positioning#

TierMessage
Community"Build your own observability. We give you the tools."
Business"Professional-grade monitoring you can actually run offline."
Enterprise"Sovereign observability for nations, defense, and critical infrastructure."

DaemonEye is not an antivirus, a telemetry feed, or a cloud service. It is a stealth observability platform designed for defenders who can't rely on anyone else.
Our promise: You own the eyes, you control the data, and nothing leaves your walls.