B
Domain Infrastructure Healthcheck SaaS
3.70
Derivation Chain
Step 1
Manjaro site down due to certificate expiry
→
Step 2
Open-source project Infrastructure management
Problem
Open-source projects, nonprofits, and small SaaS operations teams run websites without dedicated infrastructure engineers, causing them to miss basic infrastructure issues—SSL certificate expiry, DNS misconfigurations, CDN outages, domain renewal lapses—resulting in 1–3 unexpected downtimes per year. Even projects with millions of users like Manjaro have repeatedly experienced site outages due to expired certificates.
Solution
Register a domain and get comprehensive monitoring of SSL certificates, DNS records, HTTP responses, and domain registration expiry dates, with instant alerts when anomalies are detected. Core features: (1) Unified healthcheck across SSL + DNS + HTTP + domain registration, (2) Instant alerts via Slack/Discord/email on anomaly detection, (3) Automated monthly Infrastructure status Report delivery.
NUMR-V Scores
NUMR-V Scoring System
| N Novelty | 1-5 | How uncommon the service is in market context. |
| U Urgency | 1-5 | How urgently users need this problem solved now. |
| M Market | 1-5 | Market size and growth potential from proxy indicators. |
| R Realizability | 1-5 | Buildability for a small team with realistic constraints. |
| V Validation | 1-5 | Validation signal quality from competition and demand data. |
SaaS N=.15 U=.20 M=.15 R=.30 V=.20
Senior N=.25 U=.25 M=.05 R=.30 V=.15
Feasibility (74%)
Data Availability
19.4/25
Feasibility Breakdown
| Tech Complexity | / 40 | Difficulty of core implementation stack. |
| Data Availability | / 25 | Practical availability and cost of required data. |
| MVP Timeline | / 20 | Expected time to ship a usable MVP. |
| API Bonus | / 15 | Bonus for viable public API leverage. |
Market Validation (55/100)
Solo Buildability
10.0/10
Validation Breakdown
| Competition | / 20 | Signal quality from competitor landscape. |
| Market Demand | / 20 | Demand proxies from search and mention patterns. |
| Timing | / 20 | Fit with current shifts in tech, behavior, and regulation. |
| Revenue Signals | / 15 | Reference evidence for monetization viability. |
| Pick-Axe Fit | / 15 | How well the concept serves participants in a trend. |
| Solo Buildability | / 10 | Practicality for lean-team implementation. |
Technical Requirements
Backend [medium]
Frontend [low]
Infrastructure [low]