Dosu Logo
Home
Documents
Atlas Goals: DaemonEye 2026 Roadmap
Atlas Goals: DaemonEye 2026 Roadmap
Type
External
Status
Published
Created
Apr 12, 2026
Updated
Apr 27, 2026
Updated by
Dosu Bot
Source
View

Atlas Goals: DaemonEye 2026-2027 Roadmap#

⚠️ All deadlines below are explicitly aspirational. The sole maintainer is working two jobs and the schedule reflects realistic solo-founder velocity rather than aggressive commitments. Slips will happen and are acceptable; what matters is consistent forward motion and honest velocity tracking. Re-baselining is expected as v0.2.0 ships and real velocity data becomes available.
Schedule re-baseline 2026-04-26 (per PRD §13, "generous slip" / s3): OSS v1.0 GA moved from 2026-10-09 → 2027-03-31; commercial-v1.0.0 from 2027-01-30 → 2027-09-30. ~24 weeks of additional buffer added vs. original schedule.
This document defines the recommended Atlas Goals for the DaemonEye project, including key results, target dates, and the specific Jira issues to associate with each goal.
How to use: For each goal below, create the corresponding Atlas Goal in the Atlassian Goals UI. Copy the title, description, key results, and target date. Then link the listed Jira issues/versions.
Velocity assumption: 6-13 story points/week (midpoint 9 pts/week). To be re-validated against real measured velocity once v0.2.0 sprints generate enough data.

Goal 1: Ship DaemonEye OSS v1.0.0#

Description: Deliver the production-ready open-source DaemonEye agent with full process monitoring, SQL detection engine, alert system, CLI management, and observability. This is the foundational product that the commercial tier builds on.
Aspirational target date: March 31, 2027
Owner: Ken Melton
Key Results (all dates aspirational):

  • v0.2.0 Process Monitoring shipped by 2026-07-31 (60 pts, 12 issues)
  • v0.3.0 Detection Engine + Foundations shipped by 2026-10-31 (~75 pts)
  • v0.4.0 Alert System shipped by 2026-12-31 (~35 pts)
  • v0.5.0 CLI & Management shipped by 2027-02-28 (~30 pts)
  • v1.0.0 Production Ready shipped by 2027-03-31 (~20 pts)
  • Sustained measured velocity tracked weekly (target band: 6-13 pts/week)
  • Per-issue Jira workflow discipline: every tracked work item moves through In Progress before PR opens
    Link these Jira items:
  • Version: v0.2.0 - Process Monitoring
  • Version: v0.3.0 - Detection Engine
  • Version: v0.4.0 - Alert System
  • Version: v0.5.0 - CLI & Management
  • Version: v1.0.0 - Production Ready
  • Project: END (Endpoint Security)

Goal 2: Complete Schema & Privacy Foundation#

Description: Build the cross-cutting architectural foundation that every collector depends on: deterministic process identity (process_instance_id), composite primary keys for all virtual tables, timestamp normalization, sensitive field handling, and the collector-core framework. This is the most critical blocking dependency for the entire collector roadmap.
Aspirational target date: October 31, 2026 (ships with v0.3.0)
Owner: Ken Melton
Key Results:

  • process_instance_id helper with boot_id resolvers for Linux, macOS, Windows, FreeBSD
  • Composite primary key enforcement in virtual table base trait
  • Privacy framework: sensitive field marking, redaction engine, encryption-at-rest, 30-day retention
  • Compliance mapping documented (GDPR, CCPA, HIPAA, SOC2)
  • collector-core framework: trait abstraction, lifecycle management, IPC contracts, virtual table registration
  • All 3 foundation Epics closed
    Link these Jira items:
  • Epic: END-479 Schema Foundation: process_instance_id, composite keys, timestamp normalization
  • Epic: END-480 Privacy, Compliance & Sensitive Data Handling
  • Epic: END-481 collector-core Framework: Trait, IPC, Lifecycle, Virtual Tables
  • Version: v0.3.0 - Detection Engine

Goal 3: Launch Security Center MVP#

Description: Deliver the minimum viable Security Center for the commercial Business Tier — the centralized command hub that enterprise customers use to manage agent fleets, distribute rules, aggregate alerts, and view dashboards. This is the commercial anchor feature for the Business tier; pricing is under active review (see PRD §10).
Aspirational target date: September 30, 2027 (ships with commercial-v1.0.0; gated on OSS v1.0.0 shipping first)
Owner: Ken Melton
Key Results:

  • Security Center Hub operational (END-453: agent registration, fleet view, real-time status)
  • Database Layer implemented (END-451: PostgreSQL multi-tier with connection pooling)
  • Web API + Dashboard functional (END-438, END-437, END-406, END-405, END-403)
  • mTLS agent authentication working (END-447, END-475)
  • JWT middleware for web UI (END-412)
  • Alert management API (END-413)
  • OpenTelemetry observability (END-411)
  • At least 3 SIEM connectors shipping under Enhanced Log Destinations
    Link these Jira items:
  • Epic: END-477 Security Center MVP
  • Epic: END-280 Expand Enhanced Log Destinations for Enterprise SIEMs
  • Epic: END-278 Enterprise Export Formats Framework (CEF/STIX/JSON)
  • Epic: END-279 Enterprise Agent Licensing and Fleet Management
  • Stories: END-453, END-451, END-438, END-437, END-406, END-405, END-403, END-447, END-475, END-412, END-413, END-411
  • Version: commercial-v1.0.0

Goal 4: Validate DaemonEye Product Direction via JPD#

Description: Use Jira Product Discovery to validate or reject the product ideas in the ENDI backlog. The goal is not to ship all ideas — it's to make evidence-based decisions about what goes into the roadmap and what gets parked. By end of Q3, every active idea should have a clear disposition.
Aspirational target date: December 31, 2026 (extended from Sep 30 to align with v0.4 cycle)
Owner: Ken Melton
Key Results:

  • 3+ ideas moved from Impact to Ready for Delivery (committed to a future version)
  • Cross-Node Session Tracing (ENDI-1) scope clarified: Business+ cross-host only; will be promoted to a formal END epic when OSS v1.0 ships and Security Center MVP scoping starts (per OSS-first sequencing)
  • Collector roadmap sequenced: memmond, netanalymond, regmond (ENDI-5/6/7) prioritized for post-v1.0 Enterprise tier work
  • Advanced Kernel-level Data Collection (ENDI-3) has a technical spike completed (eBPF vs EndpointSecurity vs ETW tradeoffs documented)
  • At least 2 new ideas added from user feedback / market research
    Link these Jira items:
  • Idea: ENDI-1 Cross-Node Session Tracing (Discovery)
  • Idea: ENDI-3 Advanced Kernel-level Data Collection (Impact)
  • Idea: ENDI-5 memmond: Memory Analysis Collector (Impact)
  • Idea: ENDI-6 netanalymond: Network Analysis Collector (Impact)
  • Idea: ENDI-7 regmond: Registry/Configuration Collector (Impact)
  • Project: ENDI (Endpoint Products Ideas)

Goal 5: Establish Delivery Discipline#

Description: Build the muscle of regular sprint cadence, velocity tracking, and scope control. As a solo founder working two jobs, the biggest risk is not a lack of ability — it's diffuse focus and scope creep. This goal is about process, not features. The In Progress workflow discipline (move issues through In Progress before opening a PR; to Done on merge) is the operational core of this goal.
Aspirational target date: July 31, 2026 (extended to align with v0.2.0 ship date)
Owner: Ken Melton
Key Results:

  • Consistent 1-week sprint cadence from Apr 13 through v0.2.0 ship
  • Real velocity measured and stable (known pts/week with <30% variance) by end of v0.2 cycle
  • Zero sprints with scope added mid-sprint
  • Sprint retrospective notes after each sprint (even 1 sentence: what worked, what didn't)
  • All v0.2.0 work tracked through Jira's In Progress state — no To Do → Done jumps
  • v0.2.0 shipped on or before 2026-07-31 target
    Link these Jira items:
  • Board: END Sprint Board (id 135)
  • Sprint: v0.2.0 Sprint 1 (and subsequent sprints)
  • Version: v0.2.0 - Process Monitoring

Goal 6: Ship Commercial DaemonEye v1.0.0#

Description: Deliver the commercial Business Tier product: Security Center MVP + SIEM connectors + enterprise deployment + installer packages. This is the revenue-generating product built on the OSS foundation. Strictly gated on OSS v1.0.0 shipping first (per OSS-first sequencing decision); commercial work begins only after that.
Aspirational target date: September 30, 2027 (gated on OSS v1.0 GA at 2027-03-31)
Owner: Ken Melton
Key Results:

  • Security Center MVP launched (Goal 3 completed)
  • Business Tier with 5+ SIEM connectors (Splunk, Elastic, Kafka, QRadar, LogRhythm)
  • Enterprise installer packages: MSI, DMG, DEB/RPM (END-276)
  • Container/K8s deployment framework (END-277)
  • Enterprise configuration management (END-274)
  • Code-signed packages with certificate chain (END-276)
  • Integration test suite passing (END-275)
  • At least 1 pilot customer or internal deployment validating the full stack
    Link these Jira items:
  • Epic: END-477 Security Center MVP
  • Epic: END-280 Enhanced Log Destinations
  • Epic: END-278 Enterprise Export Formats Framework
  • Epic: END-279 Enterprise Agent Licensing and Fleet Management
  • Epic: END-276 Enterprise Code-Signed Installer Packages
  • Epic: END-277 Enterprise Container & Kubernetes Deployment
  • Epic: END-274 Enterprise Configuration Management
  • Epic: END-275 Enterprise Integration Test Framework
  • Epic: END-273 Enterprise Agent Performance Monitoring
  • Epic: END-433 Enterprise Alert Delivery & Routing
  • Version: commercial-v1.0.0

Goal dependency map#

Goal 5 (Delivery Discipline)
  └─► Goal 1 (OSS v1.0.0, target 2027-03-31)
        ├─► Goal 2 (Schema & Privacy Foundation) [blocks v0.3.0+]
        └─► Goal 6 (Commercial v1.0.0, target 2027-09-30)
              └─► Goal 3 (Security Center MVP)
Goal 4 (JPD Validation)
  └─► feeds future versions beyond v1.0.0

Start with Goals 2 and 5 — they're the near-term enablers for everything else.

Generated from the DaemonEye GitHub → Jira migration session (Apr 11-12, 2026), re-baselined 2026-04-26 per PRD §13. Strategy source: DaemonEye Detailed Product Strategy (Confluence).