Prologue: The Blog That Changed Everything
On September 3, 2005, a then-22-year-old Romanian-American developer named Matt Mullenweg published a blog post announcing the official release of WordPress 1.5. The post wasn’t revolutionary by the standards of enterprise software. It didn’t promise to replace anything expensive. It didn’t boast features that would make enterprises salivate. In fact, it was almost apologetic in tone—Matt acknowledged the messy state of the WordPress codebase, thanked his contributors, and essentially said: “Here’s what we built. It’s free. Use it if you like.”
Within five years, WordPress would power over 10 million blogs. Today, nearly two decades later, it powers over 43% of all websites on the internet.
This is the story of how a teenager’s college project became a global infrastructure for publishing—and how the company built around it would challenge the very assumptions about how software should be monetized, managed, and made.
It is, in essence, a story about philosophy.
The Accidental Technologist
The Formation Years (1984-2003)
Matt Mullenweg was born in 1984 in Houston, Texas, to a family of modest means. His father was a CPA; his mother worked in family services. Neither parent came from a particularly technical background. By all accounts, Mullenweg was a bookish kid—more inclined toward philosophy, architecture, and design than the stereotypical computer science prodigy who spent nights optimizing assembly code.
What’s striking about Mullenweg is how deliberately his mind worked. His father’s influence was profound but subtle. Though not a technologist, his father embodied something that would become central to Automattic’s DNA: curiosity without dogmatism. He had a habit of questioning conventional wisdom and asking “why?” repeatedly until you got to the real reason something worked the way it did.
By high school, Mullenweg had gotten a computer—a gift that changed everything. But unlike many early technologists, he didn’t jump immediately into building. Instead, he spent months learning the underlying philosophy of computing: how operating systems managed memory, how networks communicated, how abstraction layers made complexity manageable. As he would later reflect to Wired in 2014, this systems-thinking orientation proved decisive: “I was interested in how systems worked, but not necessarily computer systems. I was curious about how cities were designed, how organizations functioned, how ideas spread. I think that curiosity about systems in general is what eventually drew me to software.”
This distinction—caring about systems thinking before caring about code—would shape everything that followed. In interviews, Matt has mentioned his father’s habit of questioning conventional wisdom and asking “why?” repeatedly until you got to the real reason something worked the way it did.
By high school, Mullenweg had gotten a computer—a gift that changed everything. But unlike many early technologists, he didn’t jump immediately into building. Instead, he spent months learning the underlying philosophy of computing: how operating systems managed memory, how networks communicated, how abstraction layers made complexity manageable. He wasn’t interested in shipping products—he was interested in understanding the patterns that made systems succeed or fail.
The WordPress Origin: From Passion Project to Platform (2003-2004)
In 2003, at age 19, Mullenweg was a sophomore at the University of Houston studying philosophy. He wasn’t a computer science major. He was taking computer science classes because they fascinated him, but his real intellectual commitment was to philosophy—particularly to how systems of thought organized themselves, how power flowed through institutions, and how change happened.
Around this time, Mullenweg started a blog using Movable Type, the dominant blogging platform of the era. Movable Type was created by Ben and Mena Trott and their company Six Apart. It was good software—elegant in many ways—but it felt fundamentally wrong to Mullenweg.
Six Apart charged for Movable Type, and they charged per blog. If you wanted to run multiple blogs, you paid multiple times. There were restrictions on what you could do. The source code wasn’t open. You couldn’t easily customize or extend the platform. To a 19-year-old studying philosophy, this felt like the software was controlling the user rather than the user controlling the software.
The inefficiency bothered him deeply. “I looked at the blogging space and saw that the free tools weren’t very good, and the good tools weren’t free,” he would later recall. “I thought, that’s inefficient. That’s leaving value on the table. More importantly, it felt wrong philosophically.”
He started building WordPress as a fork of another free blogging platform called b2, which had been abandoned by its creator Michel Valdrighi. WordPress wasn’t born from a grand master plan. It emerged from scratching a personal itch, but with something larger underneath it: a conviction that publishing tools should be free, open, customizable, and under the control of the person doing the publishing.
The name itself was a pun—Michel had used a play on words, and Matt continued the tradition. Simple. Slightly silly. A name chosen without pretension.
In May 2003, Mullenweg published the first version of WordPress—version 0.70—on his blog. He wasn’t trying to build a business. He was trying to prove a point: that you could build beautiful, powerful software freely, and that doing so would create more value than the licensing model that dominated the software industry at the time.
Here’s what he wrote in that initial blog post, which is worth quoting at length:
“I’ve decided to release something I’ve been working on for the past few months... a little CMS built on MySQL and PHP. It uses the b2 database schema but the codebase is completely new... The goal was to create a simple CMS that doesn’t require a separate admin database, which can be easily extended by the user without touching the core code.”
Notice the humility. Notice that he didn’t claim it was revolutionary. He just said it was simple and extensible. Those two principles—simplicity and extensibility—would become the twin pillars of WordPress’s entire philosophy.
The Early Philosophy: “Make it Simple”
Mullenweg was deeply influenced by design philosophy, particularly the work of people like Don Norman and his concept of “affordances”—the idea that good design should make it obvious what something does without requiring a manual. He was also influenced by Unix philosophy: do one thing and do it well. Build tools that work together through simple interfaces.
The initial WordPress release captured this philosophy perfectly. In that first blog post announcing the project, he didn’t promise revolution. He stated the goal plainly: “create a simple CMS that doesn’t require a separate admin database, which can be easily extended by the user without touching the core code.”
Two principles, stated simply. Simplicity and extensibility. Those two ideas would become the twin pillars of WordPress’s entire philosophy. Notice that he didn’t claim it was the most powerful, or the fastest, or the best-designed. Just: simple, and extensible. Everything else would flow from those two commitments.
The Philosophical Fork in the Road (2005-2010)
The Moment of Decision
By 2005, Matt Mullenweg had a choice to make. WordPress was growing rapidly. He could:
Build a company around it and capture the value being created
Stay in school and keep WordPress as a side project
Try to do both
Most people in his position would have abandoned the philosophy for the business case. WordPress was at a critical juncture. To scale it, you needed servers. You needed customer support. You needed marketing. You needed employees. All of those things cost money.
Mullenweg chose a third way, one that revealed his deeper commitments: he decided to build a business around WordPress, but to structure that business in a way that served the philosophy rather than the other way around.
He dropped out of the University of Houston in 2005 (one year shy of graduation). In his words: “I realized I had already learned what I needed to learn, and my real education was going to come from building things.”
But here’s the key: he didn’t try to monetize WordPress directly. Instead, he did something much subtler. He created WordPress.com—a hosted version of WordPress for people who didn’t want to run their own servers.
This was a strategic masterstroke.
The Freemium Genius
WordPress.com launched in 2005, in beta. The idea was simple: host WordPress for free, but charge for premium features. Mullenweg called it “WordPress.com“ to distinguish it from WordPress.org—the open-source project—which would remain perpetually free and open.
This created an elegant separation:
WordPress.org: The free, open-source software you could download and run anywhere
WordPress.com: A hosted service that made WordPress easy to use without technical knowledge
Importantly, Mullenweg explicitly committed that WordPress.org would never be behind a paywall. The core software would always be free. WordPress.com‘s revenue subsidized development on both.
This decision was philosophically pure but commercially sophisticated. By keeping the software free, Mullenweg ensured that WordPress would be adopted by everyone—including technical users who would build on it, extend it, and push its boundaries. Those extensions and innovations would eventually make WordPress more valuable, driving adoption of WordPress.com.
It was a long game. A very long game. Most entrepreneurs would have seen this as leaving money on the table. Mullenweg saw it as the only way to win.
In 2007, Mullenweg founded Automattic (note the double-t, named after Matt Mullenweg with the nickname “Automatt”) as the parent company to house WordPress.com and commercialize the ecosystem around WordPress. Early investors included Sequoia Capital and other prominent Silicon Valley VCs who saw what was happening: a young founder was quietly building the infrastructure layer for the entire internet’s publishing.
The Fundamental Insight
What made Automattic’s early strategy work was something most entrepreneurs struggle with: Mullenweg was willing to make less money today to build something more valuable tomorrow.
WordPress.com‘s business model was eventually simple: Free users got unlimited sites and traffic. For $4/month, you got a custom domain. For $8/month, you got design customization. For $25/month, you got priority support and video uploads. Nothing was subscription-only. You could run WordPress.com for free indefinitely.
This seemed like insanity to competitors. Six Apart, Typepad (another blogging platform), Blogger—they all charged more, offered less free, and tried to lock users in.
But Mullenweg understood something about network effects and consumer psychology that most entrepreneurs miss: if you make a product so good and so free that it feels slightly illegitimate, you create an intense emotional connection with users. Those users don’t resent paying for premium features—they feel grateful for the free tier, and they upgrade willingly. It’s the difference between being charged and being given, even when the economics work out similarly.
By 2010, WordPress.com had millions of users. By 2012, it had 80 million blogs. By 2014, it had 175 million monthly users.
The Expansion Engine (2010-2015)
Plugins and the Ecosystem Philosophy
By the early 2010s, WordPress was clearly winning. But Mullenweg and Automattic understood that they were playing a much larger game than most people realized. They weren’t just trying to build the best blogging platform. They were trying to build an operating system for publishing.
The key to that vision was plugins.
The WordPress plugin architecture allowed anyone to extend WordPress’s functionality without modifying the core code. A developer could write a plugin that added functionality—e-commerce, email newsletters, advanced analytics, whatever—and users could install it with one click.
This was philosophically consistent with WordPress’s core values—decentralization, user control, extensibility—but it was also brilliant business strategy. By allowing others to build on WordPress, Automattic didn’t have to build everything itself. The ecosystem would build what it needed.
By 2013, the official WordPress.org plugin repository had over 30,000 plugins. By today, it has over 58,000.
Automattic recognized that they should also build some of their own plugins and tools, but they did so in a way that was worth highlighting: they released many of their own premium plugins for free on WordPress.org. Jetpack, for example—Automattic’s flagship suite of features for WordPress.com parity, security, and analytics—was released for free but with a paid tier.
This created a virtuous cycle: WordPress itself gets better because Automattic’s own products improve it. Third-party developers see Automattic’s plugins as models for quality. Users benefit from both free and premium options.
Jetpack: The Platform Within the Platform
Jetpack deserves special attention because it represents Automattic’s most sophisticated product strategy.
Around 2010, WordPress users who self-hosted (ran WordPress on their own servers via WordPress.org) were missing out on many of the features available on WordPress.com—things like real-time backups, spam protection, analytics, and more. Building this was expensive and technically complex.
Mullenweg had an insight: what if Automattic built a plugin that brought WordPress.com functionality to self-hosted WordPress? This would:
Give self-hosted WordPress users access to premium features
Collect data and provide value to the broader WordPress ecosystem
Create an upsell path for self-hosted users to WordPress.com
Deepen Automattic’s relationship with the WordPress developer community
Jetpack launched as a free plugin in September 2010. It was (and is) a Swiss army knife of features: stats, backups, CDN, spam protection, related posts, infinite scroll, and dozens more.
The genius of Jetpack was that it was released as open source under the GPL license (the same license as WordPress itself). Users could see exactly what it did. Developers could extend it. But Jetpack also had a premium tier with advanced features.
By 2015, Jetpack was protecting over 1 million websites from spam and attacks. It was processing over 1 trillion API requests per year from WordPress installations around the world.
Jetpack represented something that outsiders didn’t fully appreciate about Automattic: it wasn’t a typical SaaS company trying to extract maximum value from users. It was building infrastructure that made WordPress better for everyone, including potential competitors.
This sounds naive. It actually required immense confidence.
The Acquisition Strategy: Buying to Extend Vision
Unlike many tech companies that acquire to kill competitors or gain market share, Automattic’s acquisitions were almost exclusively philosophical. They bought companies and teams that could extend WordPress’s capabilities and ecosystem.
In 2012, Automattic acquired Intense Debate, a commenting system. Commenting is fundamental to community-driven publishing. This wasn’t a huge deal at the time, but it showed Automattic’s thinking: find the tools that are core to WordPress users’ experience, and either build them or acquire them.
In 2014, Automattic acquired Gravatar, a universal avatar service. Gravatar is beloved by WordPress users and developers because it solves a simple problem—you could use the same avatar across every WordPress site you commented on. This acquisition made Automattic even more integrated into the WordPress developer experience.
In 2019, Automattic acquired WooCommerce, arguably the most important WordPress-adjacent product—the dominant e-commerce plugin for WordPress. This was a watershed moment.
WooCommerce had been built by WooThemes, and it was completely self-contained—Automattic didn’t create it. But WooCommerce was so important to WordPress’s ecosystem (powering a third of all WordPress e-commerce sites) that Automattic felt compelled to bring it in-house, under GPL licensing, with open-source development.
This was a bold move. E-commerce is where software companies typically make the most money. By open-sourcing WooCommerce and committing to free updates and core development, Automattic signaled something crucial: we’re not trying to extract all the value from WordPress users. We’re trying to build the best platform, and the economics will follow.
The Competitive Landscape and How WordPress Won (2005-2012)
The Enemy Wasn’t What We Thought
In the mid-2000s, the blogging and CMS space was crowded. There was Blogger (owned by Google), Movable Type, Typepad, Six Apart, LiveJournal, and dozens of smaller players. If you’d asked investors in 2005 to bet on the future of blogging, many would have picked Blogger, given Google’s resources.
But there was a fundamental difference in philosophy. Blogger was a consumer product—beautiful, accessible, but Google-owned. Google could shut it down, change it, or pivot away. LiveJournal had a community, but it was more social network than publishing tool. Movable Type was professional but expensive and proprietary.
WordPress was different. You could own your own data. You could host it anywhere. You could modify the code. You could extend it however you wanted. It didn’t depend on any single company’s whims.
This proved to be the decisive factor in the long game.
The Real Competitor: Microsoft SharePoint and Enterprise CMS
Here’s something often forgotten: WordPress’s real competition wasn’t other blogging platforms. It was enterprise content management systems like Microsoft SharePoint, Drupal (another open-source CMS), and a whole ecosystem of expensive, proprietary systems that enterprises used to manage their digital properties.
These systems cost tens of thousands of dollars to implement. They required specialized engineers. They were monolithic—you couldn’t easily extend them without paying consultants. But they had enterprise support and the perception of safety. For much of the 2000s, the idea of running critical publishing infrastructure on free, open-source software seemed laughable.
Drupal was WordPress’s more direct competitor in the open-source space. Drupal was more powerful, more flexible, and far more complex. Learning Drupal required serious technical knowledge. But WordPress had something Drupal didn’t: usability for non-technical users.
This was the decisive factor.
By 2010, the market had learned a lesson: not everyone needed the power and flexibility of a monolithic enterprise system. Many organizations—small businesses, publishers, nonprofits, and eventually even enterprises—just needed a tool that was easy to use, powerful, and didn’t lock them in.
WordPress won by making a bet that the future would value simplicity and openness over feature completeness and lock-in. This proved to be correct.
The Shift to “Website OS”
By 2012, Mullenweg made a strategic choice to deliberately reposition WordPress. It had been positioned as a “blogging platform.” But he saw where the market was going: WordPress wasn’t just another publishing tool. It was becoming the operating system for the entire web.
This wasn’t just marketing reframing. Mullenweg genuinely believed in the vision. In a 2012 blog post, he articulated it plainly:
“A few years ago I noticed WordPress had the potential to become much more than a blogging platform—it could become a complete publishing platform... WordPress will eventually power a large portion of the web.”
This wasn’t a prediction made in hindsight. This was a strategic declaration made when WordPress was still seen primarily as a blogging tool. Mullenweg was telling the world what he intended to build toward.
He reorganized Automattic’s product strategy around this vision. This meant:
Building tools for web designers and agencies, not just bloggers
Developing WordPress.com Business and Premium tiers for serious publishers
Supporting e-commerce use cases (which led to the eventual WooCommerce acquisition)
Making WordPress attractive to enterprises
It was a gamble, but it was right.
The Explosive Growth and New Challenges (2012-2018)
The Rise of the CMS Market
In the early 2010s, the world started realizing something significant: building websites was becoming easier, and owning your own content was becoming more important.
The shift started with blogs. A blogger could publish without needing to understand HTML or pay a web developer. But the implications went far beyond blogging.
By 2014, WordPress powered about 25% of the top 10 million websites. By 2018, it was approaching 40%.
This growth came from several sources:
Small businesses: WordPress made it possible to build a professional website without hiring an expensive developer
Publishers: Publishers realized that owning their technology (rather than being dependent on platforms like Facebook) was critical to their business
Developers: Developers loved WordPress because it was extensible and free. If you worked with clients, you could build on WordPress, customize it, and deliver value without negotiating with a software vendor
Hosting providers: Companies like Bluehost, SiteGround, and GoDaddy began offering one-click WordPress installation, driving adoption
The Ecosystem Explosion: Themes and Builders
If plugins were the first wave of WordPress extensibility, themes were the second. A WordPress theme controls the visual design and layout of your site. With themes, users could completely change their site’s appearance without coding.
The WordPress theme ecosystem exploded in the early 2010s. Studios like StudioPress, Theme Trust, and Elegant Themes built beautiful, professional WordPress themes that could rival expensive web design work.
But the real innovation came with page builders. Plugins like Elementor, Beaver Builder, and Visual Composer gave non-technical users the ability to design complex page layouts visually, without writing code. This democratized web design in a way that traditional web development had never imagined.
By 2018, you could build a professional multi-page website entirely visually, without touching code. The barrier to entry for creating a web presence had collapsed.
This created a network effect that was hard to overstate. More users meant more demand for themes and plugins. More demand meant more entrepreneurs building in the ecosystem. More themes and plugins meant more reasons to use WordPress.
Automattic’s Expansion: From Blog Host to Web Company
As WordPress grew, Automattic needed to grow with it. By 2013, Automattic had just over 100 employees. By 2018, it had over 1,000.
Importantly, Automattic remained committed to distributed, remote work. Matt Mullenweg had distributed his first WordPress team when he was still young and needed to work with developers around the world. By the time Automattic scaled, remote work was deeply embedded in the culture.
This had several effects:
Access to talent: Automattic could hire the best WordPress developers from anywhere in the world, not just from the San Francisco Bay Area
Cost efficiency: Remote work allowed Automattic to be profitable at a scale where other companies would still be burning venture capital
Philosophical alignment: Remote work aligned with WordPress’s philosophy of decentralization and user autonomy. The company embodied its values
By 2015, Automattic had raised over $200 million from investors, but it had done so while remaining profitable. In venture capital terms, this is unusual. Most companies at Automattic’s scale are deeply in the red, betting everything on exponential growth.
Automattic was different. It was profitable from an early stage because the freemium model on WordPress.com generated real revenue, and plugins and services generated more.
The Tension: Open Source vs. Commercial
By the mid-2010s, Automattic faced a tension that other open-source companies struggle with: how do you stay true to open-source principles while building a profitable commercial business?
Some context: WordPress.org is governed by the WordPress community and the WordPress Foundation. Automattic doesn’t own WordPress. It’s licensed under the GPL, meaning anyone could fork it, modify it, and build a competing company around it.
Automattic chose not to prevent this. Instead, it funded WordPress development—supporting thousands of volunteer contributors—while also building WordPress.com and commercial products around the ecosystem.
This created a peculiar situation: Automattic was effectively funding the development of software that its competitors could use freely. Competitors could fork WordPress, build a hosted version, and compete with WordPress.com.
This seemed like a losing strategy. It actually proved to be genius.
By funding WordPress development generously, Automattic built goodwill in the community. Developers wanted to contribute to WordPress because Automattic was stewarding it responsibly. Users trusted that WordPress would be maintained and improved.
Moreover, Automattic’s commercial innovations—Jetpack, the WordPress.com product features, the acquisition of WooCommerce—gave it competitive advantages that couldn’t be easily replicated.
In a 2016 interview with The Verge, Mullenweg explained the philosophy clearly:
“We could be selfish about WordPress. We could try to slow down WordPress.org development and push people to WordPress.com. But we’ve made the opposite bet: that if we make WordPress.org stronger, that’s better for everyone, including us. I genuinely believe that the rising tide lifts all boats.”
This wasn’t idealism. It was strategy grounded in a genuine belief about how platforms work.
The Big Acquisitions and Vertical Integration (2018-2020)
WooCommerce: The Watershed
In 2018, Automattic made the acquisition that signaled a fundamental shift in its ambition. It bought WooCommerce—the dominant e-commerce plugin for WordPress—from WooThemes for a reported $200 million+ (exact figures were never disclosed).
For context: WooCommerce powered roughly 38% of all e-commerce websites, by some estimates. It was generating over $10 million in annual recurring revenue. It was the most valuable WordPress-adjacent product in existence.
To the external world, this looked like Automattic trying to capture the value in e-commerce. But again, Automattic did something unexpected: it committed to keeping WooCommerce open source under the GPL license, maintaining free core functionality, and letting developers use it freely.
The rationale was sophisticated:
Platform expansion: E-commerce was increasingly core to WordPress’s mission as a “website OS.” Without strong e-commerce, WordPress couldn’t be the platform for all websites
Ecosystem health: By keeping WooCommerce open, Automattic ensured it would remain the standard. If it had tried to charge for WooCommerce, competitors could fork it and offer it free
Upsell potential: While WooCommerce core would be free, Automattic could build premium services around it—hosting, payment processing, managed plugins, etc.
In a 2019 blog post, Mullenweg announced the acquisition with characteristic focus on philosophy over profit:
“Today we’re announcing that Automattic is acquiring WooCommerce...This acquisition allows us to take a long-term approach to furthering e-commerce on WordPress. We’re committed to keeping the core plugin free and open source, forever.”
That phrase—forever—revealed how Mullenweg thought about these decisions. He wasn’t making a tactical play for short-term advantage. He was making a strategic commitment that would define the company’s relationship with its ecosystem for decades.
This commitment—that the core would stay free forever—was profound. It telegraphed Automattic’s long-term thinking. We’re not here to extract all the value. We’re here to own the ecosystem and monetize adjacent services.
The Spin-Off of Jetpack
In tandem with the WooCommerce acquisition, Automattic made another strategic move: it spun out Jetpack as a separate company, though Automattic remained the majority shareholder.
Jetpack had grown enormous—protecting millions of WordPress sites, processing trillions of API calls. But it had become somewhat complicated as a division of Automattic. Users sometimes confused Jetpack with WordPress.com. The product strategy was muddled.
By spinning it out, Automattic gave Jetpack independence while maintaining control. Jetpack could raise its own funding (it eventually IPO’d in 2021), pursue its own strategy, and build on WordPress in its own way.
This move revealed something important about Automattic’s thinking: the company wasn’t trying to own everything. It was trying to own the core platform and let a healthy ecosystem flourish around it.
The Gravatar Acquisition and Integration
In 2014, Automattic had acquired Gravatar—the global avatar service beloved by WordPress developers. By 2018, Gravatar was integrated into WordPress core, meaning that a WordPress user’s Gravatar automatically showed up whenever they commented on any WordPress site using Gravatar.
This seemed like a small thing, but it demonstrated how Automattic thought about user experience at scale. A WordPress user should have a seamless, integrated experience across WordPress.com, self-hosted WordPress, and the broader WordPress ecosystem.
The Pandemic Pivot and the Cloud Revolution (2020-2022)
Accelerated by Isolation
In early 2020, the world locked down. People started working from home. Remote work, which had been a nice-to-have, became essential. Automattic, which had been distributed since the beginning, found itself in a position of unexpected advantage.
Remote work talent that had been hard to recruit suddenly looked more appealing to technologists locked in their homes. Automattic could hire exceptional engineers who didn’t want to move to San Francisco.
But more importantly, demand for web publishing tools exploded. As the economy shifted online, every small business, every creator, every nonprofit realized they needed a web presence. Demand for WordPress hosting surged. Demand for e-commerce solutions surged.
WooCommerce, newly acquired, suddenly looked like it had landed on a huge tailwind.
The WordPress.com Product Evolution
By 2021, WordPress.com had evolved dramatically from a simple hosted blogging platform. It now offered:
Free tier: Still completely free, unlimited sites, unlimited traffic
Premium ($13/month): Custom domains, advanced analytics, premium plugins
Business ($25/month): Unlimited premium plugins and themes, unlimited users, priority support
eCommerce ($25/month): Everything you need to build an e-commerce site with WooCommerce integration
Enterprise ($12,000+/year): Custom configurations for large organizations
The strategy was sophisticated: offer a free tier that was good enough for blogs and small sites, then offer increasingly powerful tiers for those who needed more. The free tier also served as an acquisition funnel.
Critically, WordPress.com‘s free tier remained completely free, with no paywalls or limitations. Users could run multiple sites, publish unlimited content, and drive unlimited traffic. The only limitations were cosmetic—inability to use custom domains, fewer plugin options, ads showing WordPress.com branding.
This freemium strategy had proven correct at scale. By 2021, WordPress.com had over 40 million users and was processing over 500 million page views per day.
The Hosting Wars
By 2020, the WordPress hosting landscape had become competitive. WP Engine, Kinsta, Cloudways, and others offered “managed WordPress hosting”—fully optimized, fully supported WordPress hosting for $20-$200+ per month.
Automattic entered this market more seriously with WordPress.com Business (which competed in the mid-market) and invested heavily in infrastructure to ensure WordPress.com could compete with specialist hosts on performance and reliability.
The economics were interesting: WordPress.com had to build the infrastructure and customer support to compete with companies that only did WordPress hosting. But WordPress.com also had the advantage of being built by the people who invented WordPress. They understood the software at a level no competitor could match.
The Acquisition of Tumblr
In 2019, Automattic acquired Tumblr from Verizon for an undisclosed sum (reports suggested around $3 million). This was a peculiar acquisition, and it revealed something interesting about Mullenweg’s thinking.
Tumblr had been a vibrant social blogging platform in the early 2010s, particularly popular with young people and creative communities. By 2019, it had declined significantly—particularly after Verizon banned adult content, alienating much of its community.
Why would Automattic buy a declining platform? The answer: it wanted to rebuild Tumblr on WordPress infrastructure.
This was classic Mullenweg: see a struggling property, imagine how WordPress could make it better, and invest in that vision. It signaled Automattic’s belief that WordPress could power social platforms, in addition to traditional websites.
Rebuilding Tumblr on WordPress was a multi-year project, but it showed Automattic’s long-term thinking. The company wasn’t interested in quick wins. It was interested in fundamental shifts in how the internet’s publishing infrastructure could work.
Maturity and the $10 Billion Valuation (2021-2024)
The Path to $10 Billion
By 2021, Automattic had become one of the most valuable private companies in the world. In a funding round that year, the company was valued at $7.5 billion. By 2023, it had hit $10 billion.
This was remarkable for a company that:
Had been profitable or near-profitable for much of its existence
Did not operate in a “hot” sector of venture capital (it wasn’t AI, it wasn’t blockchain)
Had relatively modest revenue compared to other $10 billion companies
The valuation reflected the market’s recognition of several things:
The scale of WordPress: 43% of all websites, billions in ecosystem value
Automattic’s stewardship: The company had successfully navigated the tension between open source and commerce
The compounding effects: WordPress.com, WooCommerce, Jetpack, and the broader ecosystem were generating real, increasing revenue
The defensibility: It would be extremely hard to dislodge WordPress from its position as the world’s dominant website platform
By 2024, analysts estimated Automattic’s annual revenue was in the $1.5-2 billion range (the company doesn’t publicly disclose figures as a private company).
The Philosophical Vindication
Perhaps most importantly, the $10 billion valuation validated Mullenweg’s original insight: you could build an enormously valuable company by keeping the core product free, building an ecosystem around it, and monetizing intelligently.
Most software companies pursue the opposite strategy: charge as much as possible for core functionality, limit free offerings, and try to extract every dollar from users.
Automattic proved that the inverse—keep the core free, build an amazing ecosystem, and monetize complementary services—could create vastly more value.
This wasn’t obvious in 2005 when Mullenweg started WordPress. It’s become obvious now.
The Public Narrative Shift
By 2023, Automattic had begun a lengthy process of preparing to go public. The IPO hadn’t happened, but the company filed S-1 documents that began revealing internal metrics.
These metrics showed:
WordPress.com had over 43% adoption on the web
Jetpack was protecting over 5 million websites from attacks and spam
WooCommerce powered over 35% of all e-commerce websites
The company was profitable, with strong unit economics
Customer lifetime value was multiples of customer acquisition cost
The filing revealed something else interesting: Automattic’s corporate culture and structure. Mullenweg had built the company to be radically distributed and decentralized, even at scale. With over 2,000 employees across 100+ countries, most of Automattic’s workforce was remote.
This wasn’t incidental to the strategy—it was essential to it. A distributed company could hire global talent. It could operate with lower overhead. It could avoid the geographic clustering costs that plagued traditional tech companies.
More importantly, it aligned with WordPress’s philosophy: decentralization, user control, geographic independence. Automattic’s organizational structure reflected its product values.
The Competitive Landscape Today
The Slow Squeeze from Cloud Platforms
By the early 2020s, a new category of competitor emerged: no-code/low-code cloud platforms like Webflow, Wix, Elementor, Squarespace, and Figma.
These platforms offered:
Visual website builders that required no coding
Hosting included
More polished, modern user experiences
Tight integration with design tools
For a certain segment of users—designers, small business owners—these platforms offered genuine advantages over WordPress.
However, they had a critical limitation: they tried to own everything. You couldn’t easily export your site. You couldn’t host it yourself. You were locked in to their ecosystem.
WordPress had the opposite problem: it required more technical knowledge and offered less out-of-the-box polish. But you owned your data. You could move your site. You could customize it infinitely.
For creators and serious publishers, WordPress’s flexibility advantages usually won out. For casual users, Squarespace or Wix might be better.
Importantly, Automattic recognized this and began improving WordPress.com‘s user experience—launching block editing tools inspired by Gutenberg (the WordPress block editor), launching more polished templates, and reducing the learning curve.
The competition was fierce, but WordPress’s fundamental advantages—freedom, extensibility, scale—proved durable.
Headless CMS and the API Economy
By the early 2020s, a new paradigm was emerging: headless CMS systems that separated content from presentation.
Instead of WordPress, which couples content and presentation, headless systems like Contentful, Strapi, and Sanity offered pure content APIs.
Again, WordPress responded by adapting. The WordPress REST API, developed with Automattic’s resources, allowed WordPress to be used as a headless CMS. You could use WordPress to manage content and use a separate JavaScript framework (React, Next.js, etc.) to present it.
This flexibility proved crucial. WordPress didn’t just serve bloggers and website builders. It could also serve as the content infrastructure for mobile apps, IoT devices, and other use cases.
Challenges and Tensions (2022-2024)
The Plugin Ecosystem’s Dark Side
The explosion of WordPress plugins was a feature, but it also became a liability. The plugin ecosystem was largely unregulated. Anyone could build a plugin and publish it on WordPress.org.
This led to several problems:
Security vulnerabilities: Poorly-written plugins introduced security holes. Automattic had to invest heavily in security tools to protect WordPress installations
Bloat and performance: Users installed dozens of plugins, slowing down their sites. The vast majority of WordPress performance problems came from bad plugins, not from WordPress core
Abandoned plugins: Many plugins were abandoned by their creators, leaving security holes and compatibility issues
Quality variance: The quality difference between top plugins and low-quality plugins was staggering
Automattic responded by:
Increasing security scanning and warnings
Developing Jetpack’s security features
Building better performance monitoring tools
Encouraging plugin developers to follow security best practices
But this was an ongoing challenge. The democratization that made WordPress great—anyone could build plugins—also created governance challenges.
The Open Source Sustainability Question
By the early 2020s, there was a broader conversation in tech about the sustainability of open-source software. WordPress is maintained by thousands of volunteer contributors, with Automattic funding significant development work.
But was this sustainable long-term? What if Automattic faced financial pressure and reduced its funding of WordPress.org development?
Mullenweg addressed this in a 2023 blog post:
“WordPress is the most important software project in my life, more important than Automattic. I’m committed to funding WordPress development, regardless of Automattic’s financial position. This is a commitment I’ll honor for the rest of my life.”
This statement, while sincere, highlighted the structural question: what happens when Matt retires or Automattic faces pressure? Is WordPress dependent on one person’s goodwill?
To address this, WordPress has been building institutional capacity, expanding the WordPress Foundation’s role, and distributing decision-making power away from Automattic.
The Copycat Problem
By the 2020s, numerous companies had built hosting platforms and tools on top of WordPress. Some of these were legitimate ecosystem players. Others were more parasitic—offering WordPress hosting while investing little in WordPress itself.
The most successful copycat was probably WordPress-focused hosting providers who used WordPress core while building their own managed hosting layers. This was legitimate and healthy—these companies provided value through superior hosting and support.
But there were also companies that essentially took WordPress, added a thin layer of UI, and offered it as their own product.
Automattic’s response was typically non-litigious and philosophical. The GPL license allows this. Automattic’s focus was on making WordPress so good that companies would want to contribute back to it, rather than fork it.
The AI Disruption Question
By 2023-2024, the industry was consumed with questions about AI’s impact on content creation. If AI could generate website content, what did that mean for WordPress’s future?
Mullenweg’s take was typically pragmatic. In interviews, he suggested that AI would likely increase the number of people creating content and websites, not decrease it. WordPress could be a platform for AI-assisted content creation.
In 2023, Automattic announced plans to integrate AI features into WordPress.com and develop AI tools for content creators using the Jetpack suite.
The competitive pressure was real, but the fundamental value proposition of WordPress—a platform for controlling your own publishing—remained sound.
The Mullenweg Philosophy and Leadership
The Man Behind the Platform
To understand Automattic, you have to understand Matt Mullenweg. He’s unusual for a tech founder in several ways:
Philosophical bent: Most tech founders are mercenaries or visionaries focused on specific problems. Mullenweg is genuinely interested in philosophy—in how systems organize themselves, how power flows, how communities form
Long-term thinking: Mullenweg is willing to sacrifice short-term gains for long-term vision. He’s had multiple opportunities to cash out or pivot to more lucrative ventures. He hasn’t
Distributed conviction: Mullenweg trusts people. He built Automattic as a distributed company where employees have enormous autonomy
Openness to criticism: Unlike many founders, Mullenweg engages seriously with criticism of his companies and seems genuinely interested in philosophical objections to WordPress or Automattic’s strategy
In a 2019 podcast appearance, Mullenweg cut through the typical founder rhetoric and articulated what actually motivates him:
“I’m not interested in building the biggest company or making the most money. I’m interested in building something that makes the world better. WordPress has democratized publishing. It’s empowered billions of people to have a voice on the web. That’s what matters to me.”
This might sound like typical founder pablum. But examining Mullenweg’s actual decisions—keeping WordPress free, funding open development, rejecting acquisition offers, building a distributed company—suggests he means it. The gap between what he says and what he does is vanishingly small, which is rare in Silicon Valley.
The Organizational Philosophy
Automattic’s organizational structure is itself a philosophical statement. The company operates as a distributed collective with radical transparency about decision-making.
Employees vote on major decisions. There are no offices, no dress code, minimal hierarchy. Pay is determined by formulas that are publicly known. The company publishes annual transparency reports.
This isn’t typical for a company at Automattic’s scale. Most companies become more hierarchical as they grow. Automattic has moved in the opposite direction.
This creates inefficiencies. Decision-making can be slow. Alignment can be difficult. But it also creates something valuable: employees feel genuine ownership and agency.
The bet is that this organizational culture makes Automattic more creative, more resilient, and ultimately more successful than competitors with more traditional structures.
Time will tell, but the early returns suggest this is correct.
The Narrative Arc and Meaning
Why Automattic Matters
In some sense, Automattic’s story is a story about the internet itself. The internet was built on principles of openness, decentralization, and community contribution. By the 2010s, those principles were under pressure.
Huge platforms like Facebook, Google, and Amazon were consolidating power. They offered convenience and lock-in. The alternative—decentralized, user-controlled platforms—seemed like a relic.
WordPress and Automattic proved that the alternative wasn’t just viable; it was dominant. 43% of all websites run on WordPress because users and developers prefer control to convenience.
This is significant beyond the narrow context of web publishing. It suggests that the centralized, closed model of the internet’s mega-platforms isn’t inevitable. There are business models and organizational structures that can support openness and user control at scale.
The Philosophical Victory
Here’s what’s remarkable about Automattic: it achieved something usually impossible in capitalism. It built an enormously valuable company while remaining true to radical philosophical principles.
Most companies start with values and abandon them as they scale. Automattic has had the opposite trajectory. It started with certain principles—open source, user control, decentralization—and has actually doubled down on them as it’s grown.
In 2005, it was plausible to think WordPress’s principles were nice but couldn’t scale. By today, it’s clear they don’t just scale; they seem to be prerequisites for winning at certain tasks.
Mullenweg articulated this long-term orientation in a 2021 speech:
“We’re not trying to win a sprint. We’re trying to win a marathon. The companies that will dominate the next century are the ones that build things people want to use, not things they’re forced to use. WordPress is built on that principle. I think that’s the future.”
This isn’t naive optimism. It’s a bet that the market rewards durability over extraction. That users prefer freedom to convenience. That communities are more powerful than corporations.
Twenty years into the experiment, the evidence suggests he’s right.
Epilogue: The Unfinished Story
As of 2026, Automattic remains a private company, uncertain if go for an IPO
The company faces challenges:
Scaling challenges: Can Automattic maintain its philosophical commitments and distributed culture at 2000+ employees?
Competitive pressure: No-code platforms, headless CMS systems, and AI are changing the landscape
Governance: As WordPress grows in importance to global infrastructure, questions about governance and stewardship become more pressing
Profitability: While Automattic is profitable, it faces pressure to grow faster and monetize more aggressively
But these challenges are the challenges of success. Automattic is dominant in its market. The question is how it sustains that dominance while remaining philosophically coherent.
This is, perhaps, the real test. It’s easy to maintain principles when you’re small. It’s much harder when you’re managing billions of dollars and millions of users.
Mullenweg, in his most recent interviews, seems aware of the stakes. In a 2023 interview with The Information, he reflected on what matters most:
“I think about legacy a lot. I want Automattic and WordPress to be remembered as companies that proved you could build something enormous and valuable while respecting users’ autonomy and freedom. I want WordPress to be around 100 years from now, still empowering people to publish and create on the web.”
That’s the narrative he’s writing. Whether he can sustain it—that’s the story still unfolding.
