The Future of Infrastructure Observability
Netdata is evolving from infrastructure monitoring into a complete, AI-native observability platform. This page outlines our strategic direction and the investments we are making across the product.
Strategic Investment Areas
The four pillars guiding product development, engineering priorities, and platform decisions
AI-Native Observability
Extending unsupervised ML toward proactive anomaly surfacing, automated root cause analysis, and autonomous AI SRE capabilities that triage incidents and recommend remediation.
Full-Stack Signal Coverage
Building toward a single platform covering infrastructure metrics, application traces, network topology, and cloud service health with OpenTelemetry compliance across all signal types.
Operational Intelligence
Investing in richer custom dashboards, cloud-evaluated alert aggregation, SLO/SLA compliance reporting, and deeper integration with incident management workflows.
Enterprise Platform Maturity
Deepening support for external secret stores, expanding ITSM integrations (ServiceNow, PagerDuty), strengthening access controls, and hardening for air-gapped environments.
Open Ecosystem
Expanding OpenTelemetry compatibility, Prometheus remote write, Grafana plugin capabilities, and third-party integrations so Netdata fits into any existing monitoring stack.
Edge-First Architecture
Continuing to push compute to the edge for predictable costs, low latency, and full data sovereignty while improving streaming protocols and parent scalability.
Trusted by organizations worldwide
Where We're Investing
From Detection to Autonomous Response
Netdata already runs unsupervised ML on every collected metric. We are extending this foundation toward proactive anomaly surfacing, automated root cause analysis, and autonomous AI SRE capabilities.
18 ML models per metric, trained every 3 hours
Explore AI FeaturesMetrics, Logs, Traces, Topology
We are building toward a single platform covering all signal types. OpenTelemetry compliance, network flow analysis, distributed tracing, and service dependency mapping are active areas of investment.
One platform for all observability signals
See IntegrationsFlexible, Role-Appropriate Views
Enterprise teams need views tailored to their role and workflow. We are investing in richer custom dashboards, drag-and-drop chart composition, and configurable views per team.
Custom dashboards for every team
View Dashboard FeaturesCloud-Evaluated Alert Intelligence
Alert aggregation, SLO/SLA compliance reporting, deeper incident management integration, and centrally managed alert configurations are key focus areas.
Smarter alerts, less noise
Explore AlertingSecurity, Compliance, and Scale
External secret stores, ITSM integrations (ServiceNow, PagerDuty), strengthened RBAC, and hardened support for air-gapped and compliance-sensitive environments.
Built for regulated environments
Enterprise Features
How We Ship
Continuous Delivery, Working Software
Agent every 6 weeks, Cloud continuous
GitHub Releases
Community-Driven Priorities
78,000+ GitHub stars, 615+ contributors
Join the Community
Enterprise Roadmap Briefings
Direct access to the product team
Request a Briefing
Product Principles
The commitments that inform every product decision at Netdata
Zero Configuration
Every new capability auto-discovers, auto-configures, and delivers value out of the box. No setup wizards, no manual instrumentation.
Edge-First Architecture
We distribute compute to the edge instead of centralizing data. This keeps costs predictable, latency low, and data under your control.
Open Source Foundation
The Netdata Agent, including the ML engine, database, and query engine, is licensed under GPLv3+. That commitment is permanent.
Cost Efficiency by Design
Monitoring should cost a fraction of the infrastructure it monitors. Our architecture eliminates the data pipelines and storage costs that make observability expensive.
Per-Second Fidelity
Virtualized infrastructure demands high-resolution data. We collect at per-second granularity as a standard, available to every user.
Data Sovereignty
Metrics stay on your infrastructure. Only dashboard metadata reaches the cloud. This is a design decision, built into the architecture.