Platform roadmap

This roadmap records directions for discussion. It is not a feature availability table, a release schedule or a promise of parity with another observability product.

The 2.0 alpha operator workflows are documented in Services, Explore and saved queries, Perses dashboards and AI Gateway. Use those manuals and the release's tested limits for current behavior.

Proposed directions

Every page below separates existing evidence from a candidate extension and names proof required before any release claim.

• Observability pipelines
• Collector fleet governance
• Resource catalog
• Software catalog
• Application performance
• Incident response
• Topology and fault analysis
• Automation action catalog
• Platform governance
• Security observability
• Data observability
• Digital experience
• Software delivery
• Cloud cost
• AI observability
• Developer integrations

How a direction becomes a release commitment

A maintainer must agree the operator problem, source/API ownership, smallest implementation and executable acceptance scenarios. Missing data, permissions, cancellation, compatibility and native backup/restart behavior remain explicit gates. Local developer results do not establish scale, GA or an SLO.

The external directory reference helps organize questions; it does not set product scope automatically. Follow the contribution process with a bounded proposal.