Lenny's PodcastMatt Mullenweg: Why he picked a fight with WP Engine
Through GPL four freedoms and the trademark fight with WP Engine and Silverlake; he argues WordPress is a movement, not a product, and powers 40% of the web.
CHAPTERS
- 0:00 – 1:05
Cold open: taking a stand in open source amid controversy
Matt and Lenny jump straight into the current backlash around Matt and WordPress, framing the episode as an attempt to address criticism head-on. Matt sets the tone: protecting open source sometimes means confronting bad actors, even at personal cost.
- •Matt argues that openness requires defending ideals against “bullies”
- •Lenny highlights the sudden shift in public sentiment toward Matt
- •High-level tease of the WP Engine conflict and public fallout
- •Theme established: truth vs. viral misinformation in tech disputes
- 1:05 – 5:13
Episode setup: who Matt is and why this moment matters
Lenny introduces Matt’s background—WordPress’s scale, Automattic’s portfolio, and the drama prompting the conversation. The show frames two parallel goals: understanding open source’s future and unpacking the WordPress/WP Engine dispute.
- •WordPress’s reach and Automattic’s product ecosystem are summarized
- •Lenny previews topics: open source, AI, community-building, and acquisitions
- •Acknowledges ongoing “drama” and intent to cover criticisms directly
- 5:13 – 11:15
Matt’s career journey: WordPress, Automattic, and building a remote giant
Matt walks through co-creating WordPress at 19, dropping out of college, working at CNET, and founding Automattic to commercialize complementary services. He details Automattic’s scale, remote-first operating model, and broad product lineup.
- •WordPress evolved from blogging to a platform and new runtimes (e.g., Wasm/local)
- •Automattic formed to offer hosted/services layer (Akismet, Jetpack, WordPress.com)
- •Remote, distributed, async from the beginning; now ~1,700 people across ~90 countries
- •Product portfolio spans publishing, commerce, apps, and open-web utilities
- 11:15 – 17:26
Bay Lights and a philosophy of philanthropy through public art
Matt explains how the Bay Lights project came together, his early support, and his later decision to help close critical fundraising gaps. He connects the project to a broader view: art as accessible “soul-raising” infrastructure alongside basic-needs philanthropy.
- •Bay Bridge LED installation as algorithmic public art; complex public approvals
- •Matt’s early funding and later major contribution to complete the project
- •Bay Lights 360 plans: expand visibility to both sides of the bridge
- •Philanthropy framing: address fundamentals and also invest in inspiration (art)
- 17:26 – 23:15
Becoming “open source–pilled”: early life, influences, and the GPL worldview
Matt traces his path from Houston—music, economics, and early web-building—to discovering open source through forums and tools he used to learn. He argues open source is foundational to freedom as software shapes modern life, then explains GPL freedoms and why WordPress began as a fork.
- •Jazz and economics shaped collaboration + systems/incentives thinking
- •Bartering websites for music lessons led to early internet and open source exposure
- •Open source as a civil-liberty issue when software controls daily life
- •GPL’s four freedoms and why “viral” licensing matters
- •WordPress originated as a fork of the abandoned b2 project
- 23:15 – 29:53
“Fake open source” in AI: why Meta’s LLaMA doesn’t qualify (and what might explain it)
Matt explains why LLaMA’s license constraints violate core open source freedoms, focusing on usage restrictions tied to scale and permissioning. He also offers a pragmatic hypothesis: Meta may be labeling it open source to navigate regulatory regimes, despite a strong history of genuine open source contributions.
- •Key objection: permission required above a user threshold undermines freedom of use
- •Ambiguity in thresholds (users vs. visitors) creates legal/product uncertainty
- •OSI-style definitions matter; licensing language is the decisive factor
- •Meta’s broader open source track record (React, PHP contributions) acknowledged
- •Speculation: regulatory incentives may be driving the “open source” branding
- 29:53 – 35:26
How to contribute to open source—and how AI changes security and maintenance
Matt gives concrete guidance on getting involved in open source (beyond coding) and predicts AI-assisted contributions will rise sharply. He emphasizes AI’s potential for automated security scanning across WordPress’s massive plugin/theme ecosystem, then pivots to maintenance, technical debt, and building atop stable open source foundations.
- •Practical entry point: contribute to projects you use; WordPress hub is make.wordpress.org
- •Non-code roles matter: docs, support, translation, events, accessibility, design
- •AI-assisted code will likely become majority within ~5 years (prediction)
- •AI as a security force-multiplier for scanning large third-party plugin ecosystems
- •Maintenance and technical debt as enduring product risks; focus on simplifying and improving UX
- 35:26 – 39:13
Building a successful online community: ‘don’t build a product, build a movement’
Matt distills community-building into incentives and shared identity, arguing WordPress succeeded by creating belief, rituals, and participation pathways—not just features. He contrasts open platforms with proprietary “platforms” that can rug-pull ecosystem builders, positioning open source as the durable alternative.
- •Systems + collaboration mindset: incentives and culture are core to community longevity
- •Movement-building: philosophy, rituals (“Code is poetry,” jazz-themed releases)
- •Ecosystem moat: 60,000+ plugins/themes are difficult to replicate
- •Proprietary platforms can extract value from successful third parties; open source reduces that risk
- •Forking as a safeguard: users and builders retain agency if leadership fails
- 39:13 – 51:46
The WP Engine controversy: trademarks, product changes, and escalation to lawsuits
Matt lays out his version of the conflict: WP Engine’s post-PE acquisition shift, reduced contributions, confusing trademark usage, and product modifications that he believes harm WordPress’s brand. He recounts failed negotiations, a public WordCamp presentation, and subsequent litigation he characterizes as aggressive and PR-driven.
- •WP Engine’s ownership change (Silver Lake) as a turning point in behavior
- •Claims: confusing use of WordPress trademarks/logos and marketplace misrepresentation
- •Claims: cost-cutting changes (e.g., disabling revisions) degrade the WordPress experience
- •Negotiations and term sheets dragged on; Matt alleges bad-faith behavior
- •WordCamp talk precedes lawsuit naming Matt, WordPress.org, and Automattic
- 51:46 – 1:08:30
Facing backlash: platform stability fears, trademark governance, and social media distortion
Lenny presses on community concerns: perceived instability, trademark ownership complexity, and why Matt is viewed as the villain. Matt argues usage metrics remain healthy, explains the WordPress Foundation/Automattic/.org structure, defends “benevolent dictator” governance, and critiques outrage-driven social platforms for amplifying misinformation.
- •Enterprise/community anxiety about WordPress stability vs. Matt’s “numbers look healthy” claim
- •Trademark structure explained: foundation ownership, Automattic commercial license, .org under Matt
- •Governance defense: great software rarely built by committee; unpopular bets (e.g., Gutenberg) needed
- •Succession framed as passing stewardship to an individual, not a committee
- •Sentiment varies by network; Twitter/X seen as the most outrage-amplifying
- 1:08:30 – 1:16:42
Forking Advanced Custom Fields: security updates, directory control, and the injunction
Matt explains why WordPress.org intervened with a WP Engine-owned plugin when WP Engine’s access was blocked during litigation and security issues emerged. He describes creating a renamed fork (“Secure Custom Fields”), notes the controversy, and explains that a judge ordered changes that resulted in a separate listing and reversal of the original directory swap.
- •WordPress.org plugin directory as an “app store” dependency for updates
- •WP Engine access blocked; ACF updates stalled despite security issues
- •WordPress.org ships security updates and renames the fork to distinguish ownership
- •Legal outcome: preliminary injunction leads to reversing the initial approach
- •Current state: separate Secure Custom Fields project with an official team maintaining it
- 1:16:42 – 1:24:29
Acquiring and reviving Tumblr: stewardship, moderation realities, and migrating to WordPress
Matt recounts Tumblr’s rise, its Yahoo/AOL/Verizon era decline, and Automattic’s 2019 acquisition for a low headline price but significant liabilities. He describes the operational difficulty of running a social network, the goal of making Tumblr sustainable, and a massive backend migration of Tumblr sites onto WordPress while keeping the user experience stable.
- •Tumblr as an early innovator in media-rich social blogging formats
- •Acquisition history: Yahoo → AOL/Verizon → Automattic (reported ~$3M)
- •“Free like a puppy”: liabilities, investigations, burn, and moderation challenges
- •User base traits: younger demographics and significant LGBTQ+ presence
- •Major engineering effort: migrate hundreds of millions of Tumblr sites to WordPress backend
- •Exploring business models beyond third-party ads (subscriptions, first-party promotion)
- 1:24:29 – 1:34:26
Automattic’s acquisition strategy, PE comparisons, and what Matt wants next (Beeper + hiring)
Matt explains that most Automattic acquisitions aim to accelerate healthy products rather than perform turnarounds like Tumblr. He distinguishes PE “control” dynamics from minority investors, argues stewardship is proven by long-term founder satisfaction, and closes with what he’s excited about next—especially Beeper—and where to follow or apply for roles.
- •Default acquisition model: strengthen good products; occasional acquihires
- •WooCommerce as a standout success story; Automattic revenue shared (~$0.5B ARR)
- •Hot-seat: differences vs. PE—control, incentives, and long-term stewardship track record
- •Beeper mission: unify messaging across apps; early-stage energy akin to WordPress’s beginnings
- •Where to find Matt and Automattic; remote-first with globally consistent pay; hiring focus on design/product
