What Matt Mullenweg Actually Is
Matt Mullenweg co-created WordPress in 2003 alongside Mike Little, forking an earlier blogging platform called b2/cafelog. He is the founder and CEO of Automattic, the company behind WordPress.com, Jetpack, WooCommerce, Tumblr, and other commercial products built on or adjacent to WordPress.
He also leads the WordPress Foundation, the 501(c)(3) non-profit that holds the WordPress trademark and protects the open-source project’s independence. And as the project’s lead developer by historical authority, he has steered major decisions in WordPress core, including the decision to make Gutenberg the default editor, over substantial community objection.
That concentration is the defining structural tension in WordPress today: one person holds the commercial entity, the non-profit stewardship, and the open-source project leadership simultaneously.
Why It Matters for Your WordPress Site
Mullenweg’s influence over WordPress core means that major product decisions, the block editor, the Site Editor, the direction of Full Site Editing, reflect his vision for what WordPress should become. If you use WordPress professionally, you are, to a meaningful degree, betting on his judgment about where the platform goes.
His position at Automattic also means the commercial layer of WordPress is shaped by the same person who steers the open-source project. Whether that is a feature or a conflict of interest depends on which side of a specific decision you find yourself on.
What Most People Get Wrong
Many WordPress users conflate Matt Mullenweg with “the WordPress community.” He is not that. The open-source project has thousands of contributors. Mullenweg holds influence through two things: historical authority as co-creator, and Automattic’s resources, which fund a significant share of core development. That is influence, not ownership. The distinction matters.
The WP Engine dispute in 2024 tested this distinction publicly. His decision to revoke WP Engine’s access to WordPress.org resources raised serious questions about the limits of any single person’s authority over an open-source project, regardless of how that authority was earned. The community’s response was divided, which is itself informative.
The CaptainBirb Take
Understanding Mullenweg’s role is not optional if you take WordPress seriously as a platform. You do not need to hold a personal opinion about him. But you do need to understand that his decisions have shaped every version of WordPress for the past two decades, and that the structural ambiguity of his position has real implications for the platform’s future. WordPress without him is an open question. WordPress with him is the situation we are currently in, and it deserves clear-eyed understanding rather than either uncritical deference or reflexive hostility.