User truth
Real browsers over real ISP and mobile routes, not only checks from datacenters.
PUBLIC PRODUCT ROADMAP
From proving the incident to understanding its cause.
EyeballMonitor already shows what real users see across real ISP networks. Our next objective is to connect that evidence with the external services a website depends on — showing not only that something failed, but where the most likely cause lives.
Available now
Next phase
Planned
Long-term vision
This roadmap describes product direction. Only items marked “Available now” are currently part of the product; the order and scope of future phases may change after real-world validation.
THE PRODUCT THESIS
Why this system matters
A website can return HTTP 200 while a real customer sees a blocked page, a broken checkout, or a failed third-party service. Cloud monitoring sees the server. EyeballMonitor is building visibility across the entire user experience — from the real network path to the dependency most likely to be causing the incident.
Evidence, not assumption
Screenshot, timestamp, HTTP, latency, route and incident timeline in one verifiable record.
Context for the cause
The next layer will compare site behaviour with the status of its providers and components.
BUILD STATUS
How far the platform has progressed
The roadmap is organised into product phases, not marketing promises. Every future layer builds on the operating network and the evidence already being collected.
00
AVAILABLE NOW
PHASE 00
Proof-based monitoring foundation
The operating foundation: real observation from multiple locations and a visual record of every important incident.
- Real ISP points in Warsaw, Milan, Istanbul and London
- Real-browser rendering for desktop, Android, iPhone and tablet
- Uptime, latency, HTTP status and regional results
- Screenshot evidence with timestamp, route and metadata
- Incident timelines, check history and evidence archive
- Full Website Check with visual evidence and DAX technical analysis
- Customer workspaces, sites, monitors and alert settings
Outcome: see what users actually see and retain verifiable evidence of the incident.
01
NEXT PHASE
PHASE 01
Third-Party Dependency Intelligence
The first intelligence layer for the external providers a website depends on.
- A unified provider framework with adapters, components and official status sources
- An initial catalogue of 5–10 critical providers across CDN/WAF, cloud, DNS, payments, identity and messaging
- Normalised states, incident history, caching, ETag support and safe rate limits
- Manual site → provider → component mapping
- Dependency dashboard and provider detail pages
- Baseline explainable correlation between a site incident and provider incident
- Incident timeline integration and controlled alerts without alert storms
- Administration for providers, sources, mappings and sync health
Goal: during an outage, see both the evidence from the real network and the condition of the likely external dependency.
02
PLANNED
PHASE 02
Discovery, Correlation & Root Cause
Broader coverage and explainable intelligence connecting symptoms with the most likely cause.
- Automatic dependency discovery from DNS, TLS, headers, scripts and network calls
- Suggested mappings with human confirmation and confidence scores
- Expanded provider catalogue for hosting, SaaS, APIs, email, SMS, AI and developer infrastructure
- Correlation using region, ISP, latency patterns, DNS/TLS signals and browser evidence
- Provider disagreement: official status compared with what real users actually see
- Ranked root-cause candidates with clear explanations of the signals used
- Grouping and suppression of duplicate incidents and notifications
- Dependency graph, API and signed webhooks for enterprise integrations
Goal: reduce investigation time, avoid false attribution, and route incidents to the right team or provider faster.
03
LONG-TERM VISION
PHASE 03
Incident Agent & Autonomous Evidence
A controlled agent that gathers additional evidence and prepares next actions without executing risky transactions.
- Targeted verification from selected ISP points when a regional or provider issue is suspected
- Safe browser workflows up to checkout/login boundaries, without purchases or sensitive actions
- Automatic incident enrichment with screenshots, network facts and provider history
- Evidence packages for SLA claims, audits, provider disputes and internal escalation
- Incident Agent driven by deterministic facts, traceability and human approval
- Visual dependency graph and impact analysis across sites, components and providers
Vision: the system not only detects the incident, but prepares a verifiable picture of what is affected, why, and what should be checked next.
PLATFORM SCOPE
Every capability in the plan
New capabilities will be introduced incrementally and marked as available only after accuracy, security and load validation.
Provider intelligence
- Official status sources
- Components and regions
- History and normalisation
- Reliable background sync
Mapping & discovery
- Manual dependencies
- Automatic suggestions
- Confidence and approval
- Dependency graph
Correlation & RCA
- Regional and ISP patterns
- DNS/TLS/latency signals
- Root-cause candidates
- Explainable scoring
Evidence & timeline
- Browser screenshots
- Incident enrichment
- Comparisons over time
- SLA-ready packages
Alerts & operations
- Event grouping
- Suppression and cooldown
- Recovery logic
- Email, push and webhook
Admin & integrations
- Provider/source control
- Health and sync monitoring
- API and signed webhooks
- Tenant limits and audit
Security & governance
- SSRF protection
- Privacy by design
- Rate limits and caching
- Human-in-the-loop actions
Incident Agent
- Targeted verification
- Safe browser workflows
- Automatic evidence packs
- Next-best-check guidance
DELIVERY PRINCIPLES
How we decide what ships
Evidence first
A causal claim appears only when clear, traceable signals support it.
No false certainty
Official provider status is a signal, not absolute truth; we compare it with real user experience.
Production-safe
No purchases, account changes or sensitive actions in automated browser workflows.
Incremental and measurable
Each phase is validated against real incidents, accuracy, system load and customer value.
THE DEFENSIBLE ADVANTAGE
Why this can become a defensible platform
The advantage is not a dashboard alone. It is the combination of physical monitoring points, real-browser rendering, a proprietary history of evidence and explainable dependency correlation. With every verified incident, the context becomes richer and the time to the correct diagnosis becomes shorter.
Real networks
+Real browsers
+Evidence history
+Explainable intelligence
See the foundation we are building on.
The working demo shows what is available today. The roadmap shows the next product frontier.