Legal / Commercial Data
#2 Rebuilding Market Data After Learning Yahoo/Finnhub/Finviz Could Not Be Used Commercially
· Build Log
Licensing constraints forced a full data-source redesign and stricter production governance.
commercial data licensemarket data migrationFMP FRED sources
1) TL;DR
- Prototype-friendly feeds were not always production-safe for commercial use.
- Legal constraints became architecture constraints.
- Source governance was standardized across pages and worker logic.
2) What I Tried
Early prototypes prioritized speed and broad feed experimentation.
3) What Broke
Commercial readiness was blocked because source terms and usage model were misaligned.
4) Root Cause
Licensing and redistribution constraints were not integrated into technical planning early enough.
5) Before (Code Path)
public pages
- mixed source assumptions
worker paths
- heterogeneous feed expectations
6) After (Code Path)
worker/worker.js
+ approved-source-first policy
public pages
+ consistent source attribution blocks
7) Evidence (Git History)
- ed9bb52 feat(blog): Build Log corpus includes licensing migration narrative.
- c5e01ff fix(news): filter paywalled sources for safe accessibility.
- f5c08f5 fix(news): exclude strict commercialization-risk sources.
8) What I Learned
Data architecture is legal, operational, and technical at the same time.
9) Frequently Asked Questions
Did this reduce feature breadth initially?
Yes, but it increased long-term reliability and legal safety.
Why is this SEO/GEO relevant?
Search and citation quality depend on truthful source provenance.
What changed for users?
Fewer sudden feed removals and more consistent data behavior.