Public Data Migration Compliance Checker

3.50

Derivation Chain

Step 1 Public data private cloud migration policy

→

Step 2 Cloud migration vendors

→

Step 3 Automatic classification of personal information and security levels, and regulation matching for migration target data

Problem

As the government pushes to migrate public data to private clouds, migration vendors must manually verify applicable regulations—including the Personal Information Protection Act, Cloud Security Assurance Process (CSAP), and the Public Records Management Act—for dozens to hundreds of datasets. Regulation review takes an average of 3-5 hours per dataset, and omissions carry risks of fines and project cancellation.

Solution

When dataset metadata (column names, sample values, agency classification) is entered, an LLM-based system automatically classifies personal information inclusion, security level, and applicable laws, and generates a pre-migration checklist of required actions (de-identification, encryption, approval procedures). The service also automatically alerts users when legislative amendments affect their datasets.

Target: Public SI and cloud migration SMEs (20-100 employees), public institution IT officers in charge of informatization.

Revenue Model: Per-transaction billing: 5,000 KRW (approx. $3.75) per dataset review. Monthly plan: 199,000 KRW/month (approx. $149.25) (includes 100 datasets per month, 3,000 KRW per additional dataset).

Ecosystem Role: Regulation

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

3.0/5

U Urgency

4.0/5

M Market

3.0/5

R Realizability

4.0/5

V Validation

3.0/5

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.

N=.15 U=.20 M=.15 R=.30 V=.20

Feasibility (70%)

Tech Complexity

29.3/40

Data Availability

20.8/25

MVP Timeline

20.0/20

API Bonus

0.0/15

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 (57/100)

Competition

8.0/20

Market Demand

9.4/20

Timing

14.0/20

Revenue Signals

10.5/15

Pick-Axe Fit

10.5/15

Solo Buildability

5.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] AI/ML [medium] Frontend [low]

Dashboard