Open Model Distillation Lineage Tracker

2.80

Derivation Chain

Step 1 AI model distillation controversy

→

Step 2 Open-source AI model lineage/derivation tracking service

Problem

In the open-source AI model ecosystem, companies like DeepSeek, MiniMax, and Moonshot are creating derivative models by distilling from superior models, yet there is no systematic way to track which model was derived from which. Legal teams at Korean companies adopting AI models spend 40–80 hours per model on manual investigation to verify whether the license chain is clean.

Solution

A service that visually tracks the lineage of open-source AI models (derivation, distillation, and fine-tuning relationships) and automatically checks license compatibility. Key features: (1) model lineage visualization graph, (2) automated license chain compatibility checks, (3) pre-adoption legal risk report generation.

Target: Legal teams and CTOs at IT companies (10–100 employees) integrating AI models into their products

Revenue Model: Basic lookups free (5/month), Pro ~$37/month (unlimited lookups + reports), Enterprise ~$142/month (API access + custom reports)

Ecosystem Role: Regulation

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

3.0/5

U Urgency

2.0/5

M Market

3.0/5

R Realizability

3.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.

SaaS N=.15 U=.20 M=.15 R=.30 V=.20 Senior N=.25 U=.25 M=.05 R=.30 V=.15

Feasibility (72%)

Tech Complexity

29.3/40

Data Availability

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

Competition

8.0/20

Market Demand

6.2/20

Timing

16.0/20

Revenue Signals

7.5/15

Pick-Axe Fit

9.0/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

Data Pipeline [medium] Frontend [medium] Backend [low]

Dashboard