When you install WordPress, you get two plugins by default. One is Hello Dolly, a whimsical artifact that displays random lyrics from the Louis Armstrong song. The other is Akismet, a commercial spam-filtering service that requires you to sign up, provide an API key, and (if you run a business) pay for the privilege.
This bundling arrangement has existed since 2005. For nearly two decades, WordPress has shipped with a commercial product from Automattic pre-installed. The question isn’t whether this happens. The question is what it means for a platform that positions itself as democratizing publishing.
Every fresh WordPress installation includes Akismet waiting in the plugins folder. It’s inactive by default, but it’s there. Featured prominently. Ready to be activated. And when users do activate it, they’re funneled directly into creating an Akismet account on a commercial platform owned by Automattic, the for-profit company founded by WordPress co-creator Matt Mullenweg.
The commercial reality behind the open-source facade
Akismet isn’t a community-maintained plugin living on WordPress.org like thousands of others. It’s a proprietary service operated by Automattic. Personal blogs can use it for free, but the moment your site serves commercial purposes (running ads, promoting a business, selling products) you need a paid subscription starting at around $10 per month.
The pricing model itself reveals the tension. You can slide a dial on the personal plan from zero to $120 annually, essentially making a donation. But commercial sites don’t get that flexibility. They pay, or they find something else.
According to WordPress.org, Akismet has 6+ million active installations. The exact revenue Automattic generates from these paid subscriptions isn’t public, but with commercial plans ranging from roughly $120 to $600 annually, the math points to a significant revenue stream built directly into the WordPress ecosystem.
This matters because WordPress doesn’t bundle just any spam solution. It bundles Automattic’s spam solution. The platform doesn’t pre-install Antispam Bee or other open-source alternatives. It installs the one that drives revenue to the company run by the person who also controls WordPress.org and the WordPress Foundation.
The architecture of influence
The bundling goes deeper than most users realize. When you navigate to the plugins section in your WordPress admin panel and click “Add Plugins,” you see a “Featured” section. Two of the prominently featured plugins are commercial offerings from Automattic: Akismet and Jetpack.
According to Plugin Vulnerabilities, no criteria or explanation exists for how Featured plugins are chosen. The selection appears opaque, yet Automattic’s commercial products consistently occupy prime real estate in the WordPress admin interface.
This isn’t merely about placement. It’s about the seamless integration of commercial interests into what users perceive as neutral platform infrastructure. Most WordPress users don’t distinguish between WordPress.org (the open-source project) and Automattic (the billion-dollar company). They see WordPress as a unified thing, and when that thing recommends Akismet, they trust it.
The integration runs through the entire experience. WordPress doesn’t just include Akismet, it actively promotes it at the moment when users most need spam protection. The setup flow, the prominent activation notices, the “Featured” designation all create a pathway that feels like platform guidance rather than commercial promotion.
When foundations and fortunes blur
The recent legal battle between Automattic and WP Engine has exposed how thoroughly commercial interests have penetrated what was supposed to be an open ecosystem. WP Engine’s lawsuit accuses Mullenweg of having a “long history of obfuscating the true facts” about his control of WordPress Foundation and WordPress.org, according to TechCrunch.
Matt Mullenweg sits at the center of all this. He’s the CEO of Automattic, a WordPress Foundation board member, and effectively controls WordPress.org. He personally decides which posts appear in the WordPress admin dashboard news feed. He serves as Release Lead for new WordPress versions. He owns wordpress.org outright, having never fully transferred it to the Foundation.
This concentration of control matters when evaluating Akismet’s bundling. It’s not a community decision to include a commercial product with every WordPress installation. It’s a decision made by someone who benefits directly from that inclusion.
The WP Engine dispute crystallized these conflicts. When Mullenweg demanded 8% of WP Engine’s revenue or equivalent employee contributions to WordPress core, he framed it as protecting the ecosystem. But the ecosystem’s governance structure gives him unilateral power to make such demands while simultaneously running a competing commercial hosting service.
The cost of convenience
Akismet works. By most accounts, it’s effective spam protection. According to Akismet’s website, the service has blocked over 500 billion spam comments. The algorithm learns from collective data across millions of sites, creating a distributed defense system against spam.
This effectiveness makes the commercial relationship harder to scrutinize. Users activate Akismet because spam is genuinely destructive. Comments filled with malicious links, bogus user registrations, contact form abuse, these aren’t theoretical problems. They’re daily realities for anyone running a WordPress site with open comments.
But effectiveness doesn’t resolve the ethical question about bundling. WordPress could have built open-source spam protection into core. The platform could feature multiple spam solutions equally. Instead, it packages one company’s commercial service as the default solution, creating a competitive advantage no other spam plugin enjoys.
Consider the alternative universe where WordPress bundled nothing. Users would install WordPress, encounter spam, search for solutions, and choose among competing options based on features, reputation, and price. That’s a market. What we have instead is a pre-installation that shapes user behavior before competition even enters the picture.
The pattern beyond Akismet
Akismet isn’t unique in the WordPress ecosystem, it’s emblematic. Jetpack, another Automattic product, comes with similar prominent placement and integration advantages. WooCommerce, acquired by Automattic in 2015, receives preferential treatment in WordPress core features. The patterns repeat.
According to recent reporting by The Repository, multiple WordPress core contributors have raised concerns about governance and conflicts of interest, though many did so anonymously out of fear of retaliation. The concerns aren’t abstract, they reflect lived experiences of developers watching commercial priorities override community input.
In January 2025, Automattic announced it would drastically reduce its contributions to WordPress open-source development, dropping from approximately 3,988 hours weekly to just 45 hours. As reported by Digital CxO, the company stated it would instead focus on for-profit projects including WordPress.com, Pressable, WP VIP, Jetpack, and WooCommerce.
This shift reveals what was always true but rarely stated plainly: Automattic’s relationship with WordPress isn’t purely altruistic. It’s strategic. The company contributes to WordPress development because doing so serves its commercial interests. When those priorities shift, so do the contributions.
What this means for the ecosystem
The Akismet question isn’t really about one plugin. It’s about power, governance, and the difference between an open platform and a captured one.
WordPress succeeded by promising freedom. Freedom to build, modify, redistribute, and profit from work built on open-source software. But freedom assumes fair competition and transparent governance. It assumes that platform decisions serve the community rather than enriching specific commercial players.
The bundling of Akismet, the Featured plugin placements, the trademark licensing arrangements, the concentrated decision-making authority, these paint a picture of an ecosystem where commercial interests have become inseparable from platform infrastructure.
This matters for every publisher, agency, developer, and business building on WordPress. When fundamental platform decisions favor one company’s products, it distorts competition. When that same company controls platform governance, it eliminates the checks that usually constrain such power.
The current arrangement could continue indefinitely if users remain unaware of the dynamics or consider them acceptable. But awareness is growing. The WP Engine lawsuit, the exodus of Automattic employees who disagreed with Mullenweg’s approach, the anonymous statements from core contributors, all signal that tensions are reaching critical points.
Rethinking what we accept as normal
Most WordPress users have never questioned why Akismet comes pre-installed. It’s always been there. It works. That’s enough for most people.
But “it’s always been this way” isn’t an argument, it’s the absence of one. The bundling choice isn’t inevitable. It’s a decision that serves specific interests while being presented as neutral infrastructure.
If WordPress truly wants to democratize publishing, it needs to democratize its own governance. That means separating platform decisions from commercial incentives. It means transparent criteria for Featured plugins. It means genuine community control over what ships with WordPress core.
The alternative is admitting what’s already functionally true: WordPress is an Automattic platform that happens to use open-source licensing. There’s nothing wrong with being a commercial platform, but there’s plenty wrong with claiming to be an open community while operating as a commercial product.
For now, Akismet will continue shipping with every WordPress installation. Users will activate it, create accounts, and either pay or contribute what they think it’s worth. The system works, from a functional perspective.
But working and working fairly are different things. The question isn’t whether Akismet filters spam effectively. The question is whether bundling it serves WordPress, or just the company that profits from that choice.
