Repository navigation
Feature Matrix
Dennis Braun edited this page Oct 8, 2026
·
2 revisions
This page keeps public positioning honest by separating shipped capabilities from intentionally out-of-scope work. Shipped means part of the newest tagged release (stable image). Changes that are on main but not released yet are listed in the Roadmap.
DOCSight is a self-hosted evidence system for cable internet problems. It combines DOCSIS signal history, speed tests, latency, modem events, and incident notes into reports you can share with your ISP. It runs locally, collects history over weeks and months, and helps document intermittent problems that are hard to prove from a single modem screenshot or one speed test.
| Area | Status | Notes |
|---|---|---|
| DOCSIS signal monitoring | Shipped | Signal health, channels, modulation, SNR, power history, raw error counters, and comparable-channel error coverage for supported modem families. See Supported Modems. |
| Generic Router mode | Shipped | Useful for fiber, DSL, satellite, and mobile connections, but the strongest DOCSIS evidence needs cable signal data. |
| Demo mode | Shipped | Generates realistic synthetic history for evaluation without a modem. |
| Correlation analysis | Shipped | Combines signal, speed, latency, events, and notes into one investigation view. |
| Evidence Journey | Shipped | Checks which evidence is ready for a case or time window and hands that fixed period to the report. |
| Incident journal | Shipped | Notes, imports, reviewed events, and incident groupings. |
| Complaint workflow | Shipped | Report generation, complaint-ready text, and a sample public proof report. Complaint templates and BNetzA workflows focus on Germany. |
| German TKG compensation | Shipped | Local calculation and editable letter for confirmed complete-outage days or missed appointments. |
| Before/after comparison | Shipped | Helps compare a fix window, technician visit, or provider change. |
| Connection Monitor | Shipped | Per-target latency, packet loss, outages, traceroutes, and raw ping logs. |
| Speedtest, BQM, and Smokeping inputs | Shipped | Optional external data sources for the evidence timeline. |
| Notifications | Shipped | Direct webhooks, Discord, an optional Apprise sidecar, and PWA Web Push. |
| Home Assistant, MQTT, and Prometheus | Shipped | Local automation and monitoring integrations. |
| PWA and offline shell | Shipped | Installable app shell with local-first operation semantics. |
| Community modules and themes | Shipped | Extension path for optional features and themes. |
| Windows Desktop Preview | Shipped | Unsigned portable tryout build; Docker remains the path for 24/7 monitoring. |
| AI/LLM export | Shipped | Locally generated, reviewable export with redaction controls. |
| Task-based navigation and calm Home | Shipped | Top navigation with a mobile bottom bar; Home with a per-channel line status, key figures, findings, recent events, and sources. See Dashboard. |
| Channel status matrix | Shipped | Every channel over time at a glance. See Channels. |
| Correlation lanes and evidence hand-off | Shipped | One lane and scale per source, and Use as evidence for the visible window. |
| Graphite theme and contrast checks | Shipped | Default theme, system light/dark preference, WCAG AA text contrast in built-in themes. See Themes. |
| Community modem drivers | Shipped | Driver modules can add or override modem drivers. |
| Experimental PYUR FAST3896-15 driver | Shipped | See PYUR FAST3896-15. |
| Area | Reason |
|---|---|
| Legal guarantee | DOCSight documents evidence but cannot guarantee ISP or regulator outcomes. |
| Managed cloud monitoring | The project is local-first and self-hosted. |
| Public status-page replacement | DOCSight can help diagnose connection history, but uptime status pages are a different product class. |
| Universal fault detection | Results depend on modem support, configured inputs, and the data available from the local setup. |
- Data stays on the user's own machine unless they export or share it. Optional integrations communicate with the services you configure.
- Public screenshots and sample reports use synthetic or redacted data.
- DOCSight does not provide legal proof or certification, does not guarantee any ISP action, and is not endorsed by any regulator.
- Docker, or a native Python setup (see Running without Docker), or the Windows Desktop Preview for short tryouts
- A supported DOCSIS modem for full signal visibility, or Generic Router mode for broader setups
- Local storage for history and reports
Home | Quick Start | Configuration | API Reference | GitHub
- Quick Start
- Installation
- Windows Quick Start
- Windows Desktop Preview
- Running without Docker
- Podman Quadlet
- Configuration
- Reverse Proxy
- Example Compose Stacks
- Dashboard (Home)
- Connection Monitor
- Signal Trends
- Before/After Comparison
- Channels: Status, Timeline & Compare
- Event Log
- Smart Capture
- Gaming Quality Index
- Modulation Performance
- Cable Segment Utilization
- In-App Glossary
- Incident Journal
- Correlation Analysis
- Evidence Journey
- German TKG Compensation
- Filing a Complaint
- LLM Export
- Speedtest Tracker
- BNetzA Breitbandmessung
- ThinkBroadband BQM
- Smokeping
- Weather
- Netzbremse (Peering)
- Notifications
- Home Assistant (MQTT)
- Prometheus Metrics