Roadmap
ChannelWatch v1.0 ships a complete multi-DVR monitoring stack. The items below represent directions the project wants to go next, collected from community feedback and the v1.0 planning process. They’re listed here so you can see what’s coming and weigh in on GitHub Discussions.
Internationalization (i18n)
Section titled “Internationalization (i18n)”ROADMAP: not in v1.0
The v1.0 codebase ships with i18n scaffolding: strings are extracted and the t() translation function is wired throughout the UI. English is the only language that ships. Future releases will add community-contributed translation files for other languages.
Alert-source plugins
Section titled “Alert-source plugins”ROADMAP: not in v1.0
v1.0 ships a notification provider plugin loader at /config/plugins/notifications/. Alert-source plugins (custom event sources beyond Channels DVR) are a separate, more complex API that is deferred to a future release. The plugin architecture is designed to accommodate them, but the hook signatures are not finalized.
UI plugins
Section titled “UI plugins”ROADMAP: not in v1.0
Custom UI panels and dashboard widgets via a plugin API. Deferred until the core UI stabilizes post-v1.0.
Mobile app / PWA
Section titled “Mobile app / PWA”ROADMAP: not in v1.0
A Progressive Web App or native mobile companion for viewing alerts and DVR status on the go. The v1.0 web UI is responsive but not optimized for mobile-first use.
Advanced rate limiting
Section titled “Advanced rate limiting”ROADMAP: not in v1.0
Auto-tuning rate limits based on observed DVR load. v1.0 ships per-DVR fixed defaults that are user-configurable. Automatic adjustment is deferred.
Distributed mode
Section titled “Distributed mode”ROADMAP: not in v1.0
Multi-replica state sharing for high-availability deployments. v1.0 is explicitly single-replica. The Helm chart’s replicaCount defaults to 1 and should not be changed. Distributed mode requires a shared state backend that is not yet designed.
Native HA
Section titled “Native HA”ROADMAP: not in v1.0
Active-active high availability with automatic failover. Depends on distributed mode above.
Historical analytics dashboards
Section titled “Historical analytics dashboards”ROADMAP: not in v1.0
Built-in dashboards for viewing alert trends, DVR usage patterns, and notification delivery rates over time. v1.0 exposes Prometheus metrics that you can feed into Grafana for custom dashboards, but no built-in analytics UI ships.
Scheduled reports
Section titled “Scheduled reports”ROADMAP: not in v1.0
Automated email or PDF summaries of DVR activity and alert history on a schedule. Not in v1.0.
Webhook templating DSL
Section titled “Webhook templating DSL”ROADMAP: not in v1.0
A domain-specific language for customizing webhook payloads without writing code. v1.0 webhooks include dvr_id and dvr_name fields but the payload shape is fixed.
Alert rules engine
Section titled “Alert rules engine”ROADMAP: not in v1.0
An if-this-then-that rules engine for conditional alert routing. For example: “only notify on disk space alerts if free space drops below 50 GB AND it’s after 10 PM.” v1.0 alert configuration is per-type with thresholds, not conditional logic.
Multi-tenant support
Section titled “Multi-tenant support”ROADMAP: not in v1.0
Multiple organizations or user groups sharing a single ChannelWatch instance with isolated data. v1.0 RBAC covers admin/operator/viewer roles within a single tenant.
SSO / OIDC
Section titled “SSO / OIDC”ROADMAP: not in v1.0
Single sign-on via OpenID Connect or SAML. v1.0 ships local username/password authentication with optional API keys. SSO is deferred to a future release.
Aggregate opt-in telemetry
Section titled “Aggregate opt-in telemetry”ROADMAP: not in v1.0
An opt-in anonymous usage telemetry system for understanding how ChannelWatch is deployed in the wild. v1.0 ships zero phone-home by design. Any future telemetry will be strictly opt-in with full disclosure of what is collected.
How to influence the roadmap
Section titled “How to influence the roadmap”The roadmap is not a commitment. Priorities shift based on community feedback, contributor availability, and what turns out to be harder than expected.
The best way to influence what gets built next is to open or upvote issues on GitHub and join the conversation in GitHub Discussions. Items with strong community interest move up.
Related pages
Section titled “Related pages”- Contributing — how to contribute code or docs
- Support — community links and how to get help