B
Cloud Cost Migration Estimator
3.35
Derivation Chain
Step 1
Major price hikes at European hosts like Hetzner
→
Step 2
Cloud migration cost comparison
→
Step 3
Automated Infrastructure migration cost and risk calculation
Problem
Small teams running SaaS or web services face hosting price hikes (Hetzner 38%, AWS annual increases, etc.) but struggle to pre-calculate the total cost of migrating to alternative hosting — including migration labor, downtime, and new fees. Poor migration decisions can increase costs by 20-40% or cause 3-5 days of downtime.
Solution
Users input their current Infrastructure configuration (server specs, traffic, storage) and receive a real-time cost comparison across 10 major cloud/VPS providers, with automatic estimates of migration complexity, expected downtime, and hidden costs (egress fees, licenses). Key differentiator: reflects Korean billing and Tax considerations (VAT, withholding Tax), and indicates domestic region availability.
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 (70%)
Data Availability
20.8/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 (59/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 [medium]
Data Pipeline [low]