Read the Docs at 10: How Open Source Sustainability Defied the Odds
Share this article
When Read the Docs emerged from a 48-hour open source sprint in 2010, few could have predicted it would become the backbone of Python documentation. Yet as the project gained massive adoption, its founders faced the open source sustainability crisis firsthand. This week marks their 10th anniversary as a company—a milestone proving that ethical open source business models can thrive against overwhelming odds.
The Sustainability Tightrope
Read the Docs' survival stems from a carefully calibrated approach:
- **Community Edition**: Free for open source projects, supported by a single non-tracking ad
- **Business Edition**: Paid tier for enterprises needing private repositories
The model emerged from painful experimentation. Early reliance on donations led to burnout, while consulting work diverted focus from core development. Even grant funding proved unsustainable long-term. "You don't get extra points for being bootstrapped," reflects co-founder Eric Holscher. "We compete by dominating our niche—documentation—while venture-backed rivals chase growth through feature bloat."
Ten Years of Hard-Won Wisdom
Key lessons from their decade-long journey:
Trust is the core currency: "Keeping community trust is everything," Holscher emphasizes. The team routinely makes decisions favoring user values over profit maximization.
Contribution follows simplicity: Complex codebases deter contributors. Read the Docs saw more engagement in focused components like Sphinx extensions than in their monolithic core.
Embrace value leakage: Self-hosted corporate users rarely contribute back. Sustainability requires accepting this while capturing enough value from paying customers.
"You have to be okay doing more with less. Our team ruthlessly prioritizes, which sometimes frustrates users—but that tension is inherent to sustainable open source." — Eric Holscher
The Next Documentation Frontier
Recent architectural shifts position Read the Docs for future resilience. Their "magic removal" initiative eliminated build process modifications that caused local-vs-production discrepancies. The new Addons system now layers enhancements atop any documentation tool's HTML output.
With a team of four full-time engineers and critical infrastructure support from AWS and Cloudflare, Read the Docs demonstrates that open source sustainability requires three pillars: focused value creation, ethical boundaries, and radical prioritization. As proprietary platforms succumb to enshittification, this decade-old project stands as testament to open source's enduring potential when stewardship outweighs shareholder demands.