![WP Engine vs Automattic: The WordPress Trademark War Explained [2025]](https://tryrunable.com/blog/wp-engine-vs-automattic-the-wordpress-trademark-war-explaine/image-1-1770997300021.jpg)
The WordPress Trademark Battle That's Shaking the Hosting Industry
In what's become one of the tech industry's most contentious corporate disputes, WP Engine and Automattic are locked in a legal battle that goes far beyond typical business disagreements. This isn't just about hosting platform politics anymore. It's about control of the WordPress ecosystem, the legitimacy of trademark licensing, and whether a single company can extract royalties from competitors based on brand ownership. The stakes? Potentially billions in revenue and the future structure of the WordPress economy itself.
The conflict started with a deceptively simple demand. In July 2024, Automattic CEO Matt Mullenweg sent a cease-and-desist letter to WP Engine, claiming the hosting company wasn't contributing enough to the open-source WordPress project and therefore didn't deserve to use the WordPress trademark. He demanded WP Engine pay 8% of its gross monthly revenue as a royalty fee for the privilege of continuing to operate. For a company generating tens of millions in annual revenue, this figure would translate to millions of dollars annually.
WP Engine responded by filing a lawsuit, setting off a chain of legal events that's still unfolding today. What makes this dispute particularly fascinating—and troubling—is that it reveals a fundamental tension in the open-source software world. When a nonprofit foundation or a single company controls a widely-used trademark, what power do they actually have? Can they demand royalties? Can they threaten smaller competitors? And who decides what constitutes "fair contribution" to an open-source project?
The situation has escalated significantly. WP Engine has now filed a third amended complaint, introducing new allegations that paint a picture of aggressive trademark enforcement that allegedly extends far beyond their initial dispute. The hosting platform claims that Automattic planned to target at least 10 other companies with similar royalty demands. It alleges that Mullenweg even tried to pressure Stripe into canceling WP Engine's payment processing contract, effectively attempting to choke off the company's ability to operate.
Automattic, for its part, dismisses these allegations as desperate attempts to resurrect claims the courts have already dismissed. A company spokesperson stated that WP Engine's latest filing contains "nothing new," just the same narrative repackaged and reshaped. But the courts have actually allowed many of WP Engine's claims to proceed, including allegations of intentional interference, unfair competition, and defamation.
This dispute matters because it affects everyone in the WordPress ecosystem. There are roughly 43% of all websites using WordPress, according to various web technology surveys. That's over 800 million websites. When the company and people who control WordPress's trademark start making aggressive demands on the companies that host, develop for, and extend the platform, it raises serious questions about fairness, market power, and the principles of open-source software itself.
Understanding the Initial Trademark Demand
Matthew Mullenweg didn't invent the WordPress trademark dispute out of thin air. His argument was rooted in what he perceived as an imbalance in the WordPress ecosystem. WordPress is open-source software, meaning anyone can use the code for free. The brand, however, is protected by trademark law. Automattic has significant control over how that trademark is used, and Mullenweg believed larger companies profiting from WordPress weren't contributing proportionally to the project.
His specific complaint about WP Engine was that while the hosting company made substantial revenue from WordPress customers, it wasn't returning enough value to the open-source project. He pointed out that WP Engine wasn't making significant code contributions, wasn't funding major development efforts, and was essentially riding on the coattails of a community-driven project.
On the surface, this argument has some merit. Open-source projects do rely on contributions from the community. When companies build billion-dollar businesses on top of free software, there's a legitimate question about reciprocity. However, Mullenweg's approach—demanding 8% of gross revenue—was unprecedented and controversial. No other major open-source trademark owner has attempted something similar.
The 8% figure is particularly aggressive when you understand what it means in practice. For WP Engine, which reportedly generates over
WP Engine's defense was straightforward. They argued that WP Engine does contribute to the WordPress ecosystem. They maintain WordPress hosting infrastructure, they employ developers who contribute to the WordPress community, and they contribute financially to WordPress-related projects. They also pointed out that the WordPress Foundation, which technically owns the trademark, has never made such demands. If the foundation itself hasn't pursued royalty payments, why was Mullenweg, as CEO of Automattic, doing it unilaterally?
Furthermore, WP Engine raised a critical legal question: does using a trademark that's been made freely available to all competitors in the same market constitute trademark infringement? If anyone can use "WordPress" to describe their services—as the trademark guidelines theoretically allow—how can Mullenweg claim WP Engine is violating the mark by using it honestly to describe what they actually do?
Estimated data shows Mullenweg's demand of 8% gross revenue (
The Royalty Demand: Unprecedented and Aggressive
When Automattic's cease-and-desist letter arrived demanding 8% of WP Engine's gross monthly revenue, it shocked the hosting industry. Nothing like this had happened before in the open-source ecosystem. While many companies contribute financially to open-source projects they depend on, few do so under threat of trademark enforcement.
The demand was structured as follows: WP Engine would need to pay monthly royalties calculated as a percentage of gross revenue. This isn't like a traditional licensing agreement where you pay a flat fee or a percentage of profits. Gross revenue includes every dollar the company brings in, before expenses, taxes, or anything else. In business terms, this is extremely aggressive because it means WP Engine would be paying Automattic regardless of whether WP Engine was actually profitable.
Consider the financial impact. A hosting company might have gross revenue of
WP Engine's legal team argued that this demand constituted trademark misuse. The basic principle of trademark law is that trademark owners can't use their marks to control behavior unrelated to the legitimate purpose of the trademark. If someone uses "WordPress" to accurately describe their WordPress hosting service, they're using the trademark legitimately. A royalty demand unrelated to actual trademark infringement—just because the company is profitable—goes beyond what trademark law allows.
Automattic responded that this wasn't a simple royalty demand but rather an attempt to ensure fair contribution to the project. In their view, large companies profiting from WordPress had a moral obligation to contribute back. The 8% was their proposed mechanism for quantifying fair contribution. Mullenweg even suggested that if WP Engine could show significant contributions to the WordPress project, the royalty percentage might be negotiable or waived entirely.
But here's the problem with that argument: it gives Mullenweg and Automattic the power to unilaterally decide what counts as "significant contribution" and whether any particular company's contributions are sufficient. Different people would value contributions differently. Some might think $1 million in annual contributions is generous. Others might think it's insufficient. Without clear, objective standards, the decision-making power rests entirely with Automattic. That's a lot of power to concentrate in one person's hands.
WP Engine's Allegations: A Wider Pattern of Aggressive Enforcement
WP Engine's third amended complaint, filed with newly unredacted information, paints a picture of Automattic engaging in a systematic effort to extract royalties or compliance from multiple companies in the WordPress ecosystem. This is where the dispute escalates from "two companies fighting over fair contribution" to "potential antitrust violation."
According to the complaint, WP Engine discovered that Automattic had already secured royalty agreements from other companies. Specifically, Newfold Digital, a major web hosting conglomerate, is already paying Automattic for the right to use WordPress-related trademarks. The names of other companies were redacted in earlier versions of the complaint but are now being revealed.
If Automattic is systematically approaching hosting companies and design agencies with royalty demands, this suggests a coordinated strategy rather than isolated disputes. The legal concern is whether this constitutes unfair competition, trademark abuse, or even antitrust violations. Antitrust law generally prohibits companies from using dominance in one market (the WordPress trademark) to extract payments or control behavior in related markets (WordPress hosting).
The allegation that Automattic targeted at least 10 additional hosting companies beyond WP Engine and Newfold Digital is significant. If true, it suggests Mullenweg and Automattic were planning an ecosystem-wide royalty enforcement campaign. Imagine if every company using the WordPress name received a similar demand. Smaller hosting companies, theme creators, and WordPress agencies would face a choice: pay royalties or rebrand entirely.
WP Engine also alleges that these royalty demands weren't just about fairness or contribution. They were tied to specific behaviors and outcomes favorable to Automattic. Companies that agreed to pay would get continued use of the trademark and, implicitly, less harassment. Companies that refused—like WP Engine—faced escalating pressure, which brings us to perhaps the most damaging allegation.
Estimated data shows WP Engine could pay 10% of its revenue as royalties, with other companies potentially contributing 20%. Remaining revenue is 70%.
The Stripe Interference Allegation: Cutting Off Payment Processing
One of the most serious allegations in WP Engine's third amended complaint is that Automattic allegedly attempted to pressure Stripe into canceling WP Engine's payment processing account. If true, this goes far beyond trademark disputes into the territory of intentional interference with business relationships.
Here's how such interference would work: Stripe is the payment processor that handles WP Engine's customer transactions. Without Stripe, WP Engine can't process payments from customers. This isn't a minor disruption; it's an existential threat. A hosting company can't survive without being able to charge customers for services.
WP Engine alleges that after the lawsuit was filed, Automattic approached Stripe and made claims that WP Engine was violating WordPress trademark rights or misusing the brand. The alleged goal was to convince Stripe to terminate WP Engine's merchant account due to legal liability concerns. If Stripe believed that WP Engine's activities put them at legal risk, they might drop the account. Stripe is very risk-averse about payment processing, especially regarding legal disputes.
This allegation, if proven, would be extraordinarily serious from a legal standpoint. Intentionally interfering with someone's business relationships is illegal. It's different from competing fairly or even aggressively pursuing legal claims. It's taking steps specifically designed to harm a competitor by cutting off their ability to conduct business.
Automattic's response to these allegations has been notably restrained. They haven't directly addressed the specific claim about Stripe but have characterized WP Engine's latest filing as simply rehashing old allegations. However, the fact that these details are now in court documents with specific allegations means they'll likely be discovered and investigated as part of the litigation process.
The payment processing allegation raises a crucial question about the extent of power a trademark owner can wield. If Automattic can pressure other companies in the payment processing, hosting, or software ecosystem to cut off businesses they disagree with, that power extends far beyond trademark law. It becomes economic coercion backed by legal threat.
Antitrust Concerns: When Trademark Power Becomes Market Power
One of WP Engine's primary legal theories in this case involves antitrust law. The company has filed antitrust claims arguing that Automattic is using its control of the WordPress trademark to unfairly dominate the WordPress hosting and services market.
Understanding why this matters requires grasping how antitrust law works. Companies can't use dominance in one market to leverage control in another, unrelated market. Additionally, companies can't use predatory tactics to exclude competitors or force them to pay for market access.
In this case, WP Engine argues that Automattic's use of the WordPress trademark constitutes market dominance. If you're a WordPress hosting company, you almost need to use the word "WordPress" to describe your service. It's not a generic term; it's the specific technology you're selling. Customers search for "WordPress hosting" not "open-source blog platform hosting." So WordPress, as a trademark, is essential to business in that market.
Once you control an essential trademark, antitrust law says you can't use that control to extract payments unrelated to preventing consumer confusion. You can't say, "pay us 8% of your revenue or lose the right to use our trademark" just because the trademark happens to be valuable. That crosses the line from protecting intellectual property into leveraging market dominance.
WP Engine's antitrust arguments also address the alleged targeting of multiple companies. If Automattic is systematically approaching competitors and demanding royalties or favorable terms under threat of trademark enforcement, that's potentially a pattern of anticompetitive conduct. The goal would be to maintain market dominance by extracting value from competitors or forcing them to operate under disadvantageous terms.
Automattic would counter that they're not using trademark dominance but rather making legitimate arguments about fair contribution. They'd argue they're not trying to control the WordPress hosting market but simply ensuring that companies profiting from WordPress share the costs of developing and maintaining the platform. There's a legitimate debate here about whether trademark enforcement can ever be used to encourage fair contribution without crossing into antitrust violations.
Defamation and Unfair Competition Claims
Beyond trademark and antitrust issues, WP Engine has also pursued claims for defamation and unfair competition. These claims address public statements Mullenweg and Automattic made about WP Engine and its relationship to the WordPress community.
Defamation law requires that false statements were made to the public that damaged the plaintiff's reputation. WP Engine's defamation claims likely focus on specific statements Mullenweg made publicly about WP Engine not contributing to WordPress. If WP Engine can show these statements were false—that they do contribute to the WordPress ecosystem—and that these statements damaged their reputation with customers or partners, they could prevail on a defamation claim.
Unfair competition claims are broader. They address whether Automattic was using improper methods to compete unfairly against WP Engine and other hosting companies. This might include the aggressive use of trademark enforcement, the alleged attempts to pressure Stripe, public statements designed to undermine WP Engine's reputation, or the coordinated demands to multiple companies.
Automattic's position is that these claims are simply the same allegations WP Engine has been making throughout the dispute, repackaged in legal language. They maintain they've done nothing improper and that the courts will ultimately dismiss these claims as well.
However, the court's decision to allow these claims to proceed in the motion to dismiss phase is significant. Courts often dismiss weak claims early in the process. The fact that WP Engine's defamation and unfair competition claims survived initial dismissal attempts suggests the court found them sufficiently plausible to proceed to discovery and trial.
Estimated data shows that an 8% royalty on gross revenue significantly impacts profitability, with royalty payments exceeding net profit.
The Counterclaims: Automattic's Perspective
While WP Engine has pursued claims against Automattic, Automattic has also filed counterclaims against WP Engine, as well as against Matt Mullenweg and other parties. These counterclaims provide insight into Automattic's side of the dispute.
Automattic's counterclaims likely allege that WP Engine violated their terms of service, misused the WordPress trademark, or failed to comply with licensing requirements that apply to all companies using the WordPress brand. They may also argue that WP Engine made false or defamatory statements about Automattic in their public filings and communications.
In November 2025, WP Engine filed a motion to dismiss Automattic's counterclaims. The outcome of this motion isn't yet clear, but it represents another phase in the litigation. If the court dismisses Automattic's counterclaims entirely, it would be a significant victory for WP Engine. If the court allows them to proceed, it means WP Engine will need to defend against these claims in addition to pursuing their own case.
This back-and-forth of claims and counterclaims is typical in commercial litigation, but it also demonstrates how entangled and adversarial the relationship has become. What started as a business dispute has evolved into a full-scale legal war with both sides making aggressive allegations about the other's conduct.
The WordPress Foundation's Role: Caught in the Middle
An important but often overlooked element of this dispute is the WordPress Foundation's role. Technically, the WordPress Foundation—not Automattic—owns the WordPress trademark. The Foundation is a nonprofit organization created to serve the WordPress community.
This creates an interesting dynamic. Mullenweg is making trademark demands and enforcement decisions, but he's doing so nominally as CEO of Automattic, not as a representative of the WordPress Foundation. Some of WP Engine's legal arguments likely hinge on the distinction between the Foundation's authority and Automattic's authority.
The WordPress Foundation's leadership has remained relatively quiet throughout this dispute. They haven't publicly endorsed Mullenweg's trademark enforcement campaign, but they also haven't openly opposed it. This silence is noteworthy. If the Foundation believed that Automattic was misusing the trademark or exceeding its authority, one would expect them to weigh in publicly.
The Foundation did approve Automattic's general licensing guidelines, which give Automattic significant discretion in enforcing the WordPress trademark. However, those guidelines were likely developed in a different era, before Mullenweg began pursuing aggressive royalty demands.
Going forward, the Foundation may face pressure to clarify its position. Should they step back and prevent Automattic from making unilateral trademark enforcement decisions? Should they establish clear, objective standards for trademark licensing? Or should they continue allowing Automattic to exercise significant discretion?
Newfold Digital and Other Companies: The Broader Ecosystem
Newfold Digital, a conglomerate that owns multiple hosting brands and web services companies, is noteworthy for already having a trademark licensing agreement with Automattic. This shows that at least one major player in the hosting ecosystem has agreed to pay for WordPress trademark usage.
Newfold Digital's situation is interesting because it provides a real-world example of what Mullenweg might want to impose on others. The specific terms of Newfold's agreement aren't public, but if they're paying royalties to Automattic, WP Engine might face pressure to accept similar terms or risk losing the ability to use the WordPress brand.
The other companies that WP Engine alleges were targeted—whose names were originally redacted—presumably refused or resisted Automattic's demands, as WP Engine did. If WP Engine can show that Automattic was targeting multiple companies systematically, it strengthens their arguments about anticompetitive conduct and unfair competition.
These other companies may also face pressure to enter settlements with Automattic. The publicity of the WP Engine case might actually make smaller companies more inclined to accept royalty agreements rather than risk expensive litigation. This could inadvertently benefit Automattic by establishing a pattern of companies accepting licensing terms.
WP Engine's legal claims against Automattic are diverse, with trademark infringement and interference with business relationships being the most significant. Estimated data based on typical legal claim distribution.
The Court's Initial Rulings: Key Decisions So Far
In the motion to dismiss phase of the litigation, the court has already ruled on several aspects of the case. These rulings provide important signals about the strength of each side's arguments.
The court allowed WP Engine's claims for intentional interference with business relationships to proceed. This is a significant victory for WP Engine because it validates their theory that Automattic was taking improper steps beyond simple trademark enforcement. The intentional interference claim likely encompasses the allegations about pressuring Stripe and making damaging public statements.
The court also allowed unfair competition and defamation claims to proceed, again suggesting the court found these allegations sufficiently credible and specific to warrant further development through discovery and potentially trial.
At the same time, the court apparently dismissed some of WP Engine's claims in its initial ruling. The specific claims dismissed weren't enumerated in the public reporting, but Automattic's characterization suggests that certain theories of liability or certain facts didn't meet the legal threshold for proceeding.
However, the overall trajectory—that most of WP Engine's major claims survived the motion to dismiss—indicates the court views WP Engine's allegations as legally viable. This is different from saying WP Engine will ultimately win. It just means the claims are plausible enough to proceed to discovery and trial.
The discovery phase will be crucial. Both sides will be able to demand documents and testimony from the other, uncovering evidence that's currently hidden. WP Engine will likely seek evidence that Automattic targeted multiple companies systematically. Automattic will seek evidence that WP Engine was profiting substantially from WordPress without contributing fairly.
The Business Impact: What This Means for WordPress Companies
This litigation has immediate practical implications for anyone building a business around WordPress. If you're a hosting company, a WordPress agency, a theme developer, or a service provider built on WordPress, the outcome of this case affects your business model.
First, there's the obvious trademark risk. If Automattic wins the legal dispute, or if they can pressure companies into accepting licensing agreements, the cost of doing business in the WordPress space increases. What was previously free access to the WordPress trademark becomes a paid licensing arrangement. This increases operational costs for smaller companies that can't negotiate favorable terms.
Second, there's business relationship risk. If Automattic can effectively cut off payment processors, hosting providers, or other infrastructure providers for companies it disagrees with, that creates a new vulnerability. Companies in the WordPress ecosystem would need to maintain multiple payment processors, hosting providers, and critical infrastructure partners to avoid depending on any single provider that Automattic could potentially influence.
Third, there's the uncertainty factor. Right now, no one knows what the rules are. Can Automattic enforce trademark royalties? Can they pressure other companies to end business relationships? What counts as fair contribution? Until these questions are answered definitively, companies operating in the WordPress space face significant uncertainty. Some companies might slow investment in WordPress products or services until the legal situation clarifies.
Automattic might argue that this case provides an opportunity to clarify fair contribution standards for the entire ecosystem. They might be right. But the current approach—using trademark enforcement and legal threats as the mechanism—is creating fear and uncertainty rather than cooperation.
The Open-Source Philosophy Under Pressure
At a deeper level, this dispute represents a philosophical conflict within the open-source community. Open-source is built on the principle that software should be freely available and that commercial companies should be able to build profitable businesses on top of free software. WordPress has proven this model works. Thousands of companies and individual developers have built sustainable businesses around WordPress.
Mullenweg's trademark enforcement campaign seems to challenge this philosophy. It suggests that while the code is free, if you profit from it at a sufficient level, you should pay the community back through the trademark licensing mechanism. The problem is that there's no clear standard for "sufficient profit," no clear definition of what counts as "paying back," and no clear process for determining whether royalty demands are fair.
One could imagine a different approach. Instead of using trademark enforcement as a coercion mechanism, Automattic and the WordPress Foundation could establish clear, objective standards for fair contribution. They could say, for example, that companies with more than $10 million in annual revenue that generate a significant portion from WordPress should contribute 1% of profits to WordPress development. Or they could create a tiered contribution system where different company sizes have different expectations.
But the current approach—sending cease-and-desist letters with specific royalty demands, allegedly pressuring payment processors, and targeting multiple companies—breeds resentment and legal conflict rather than cooperation.
Estimated data shows Automattic holds a significant portion of the WordPress hosting market, potentially leading to antitrust concerns.
Potential Outcomes and Their Implications
The litigation could resolve in several different ways, each with different implications for WordPress ecosystem.
Scenario 1: WP Engine Wins Decisively
If WP Engine wins on the major claims—demonstrating that Automattic's trademark enforcement was abusive, that the interference with Stripe was illegal, and that the conduct was anticompetitive—the implications are significant. Trademark owners would face clearer limits on how they can enforce trademarks against companies legitimately using the mark. Companies in the WordPress ecosystem would gain certainty that they can continue operating without facing arbitrary trademark demands.
Automattic would likely be prohibited from enforcing trademark royalties based solely on a company's profitability. They might face damages for the interference with business relationships, though quantifying such damages is often difficult. The main result would be a clear precedent that trademark enforcement can't be used as a coercion mechanism to extract payments.
Scenario 2: Automattic Wins or the Case is Dismissed
If the court rules in favor of Automattic or dismisses WP Engine's claims, the implications are that trademark owners do have the authority to require licensing fees from companies profiting from the mark. This would presumably give Automattic the green light to pursue royalty agreements with other companies in the WordPress ecosystem.
WP Engine would face significant operational and financial consequences. The question would be whether they'd agree to royalty payments or rebrand away from WordPress. For a company built almost entirely around WordPress, rebranding would be extraordinarily expensive and difficult.
Scenario 3: Settlement
The most likely outcome is actually a settlement, where both sides agree to terms that neither fully gets what they want but both can live with. A settlement might involve WP Engine agreeing to make financial or other contributions to WordPress development in exchange for clearly defined trademark usage rights. This would preserve the business relationship while clarifying future obligations.
A settlement would likely involve a payment of some kind from WP Engine to Automattic or the WordPress Foundation, but probably something much less than the 8% royalty originally demanded. It might also include commitments about future code contributions or infrastructure support.
The Bigger Questions: What Happens Next?
Regardless of how the WP Engine case resolves, the broader WordPress ecosystem needs to address the fundamental questions that this dispute has raised.
First, what are the clear standards for trademark usage and licensing in the WordPress ecosystem? The WordPress Foundation should establish clear, objective criteria that define how companies can use the WordPress trademark and what, if anything, they should pay for that usage.
Second, what mechanisms ensure that trademark enforcement authority is exercised fairly and transparently? Right now, Automattic has significant discretion, with limited oversight. Establishing a formal governance process could improve fairness and reduce the perception of arbitrary enforcement.
Third, how should companies contributing to the WordPress ecosystem be recognized and valued? Is financial contribution the primary metric, or should code contributions, infrastructure support, and community engagement also count?
Fourth, how should the WordPress Foundation's relationship with Automattic be structured? Automattic is a major player in the WordPress ecosystem, but they also have commercial interests that might not always align with the broader community's interests. Clearer separation of roles might help.
These questions don't have easy answers. But avoiding them—and instead relying on legal threats and aggressive enforcement—seems to be generating more conflict than clarity.
Lessons for Open-Source Projects and Trademark Owners
This dispute offers important lessons for other open-source projects and trademark owners who want to ensure fair contribution without creating conflict.
Establish Clear Standards Early
The WordPress Foundation should have established clear, objective standards for trademark usage before disputes arose. When standards are clear from the beginning, companies can make informed decisions about their business models, and everyone knows what the expectations are.
Separate Governance from Commercial Interests
Automattic is simultaneously a major commercial player in the WordPress ecosystem and a company with significant influence over WordPress governance through Mullenweg's various roles. This overlap creates conflicts of interest. Clear separation—where governance decisions are made by people without commercial stakes—would reduce the appearance of impropriety.
Use Positive Incentives Rather Than Threats
Instead of threatening companies with trademark enforcement, successful open-source projects offer recognition and benefits to contributing companies. The Linux Foundation, for example, has membership tiers and recognition programs that incentivize contribution without relying on legal threats.
Make the Process Transparent
If trademark enforcement or licensing decisions are necessary, the process should be transparent, with clear criteria and opportunities for the affected parties to present their perspective. The current approach—unilateral demands from Automattic—lacks this transparency.
Distinguish Between Trademark Protection and Commercial Leverage
Trademark law exists to prevent consumer confusion. It's a legitimate tool for protecting brand integrity. But using trademark law as a mechanism to extract payments from competitors or force them into commercial arrangements goes beyond legitimate trademark protection. Clear lines need to separate these two purposes.
Estimated data suggests that a settlement is the most likely outcome (50%), followed by equal chances of either WP Engine or Automattic winning (25% each).
The State of the Dispute: Where Things Stand Now
As of the latest updates in 2025, the litigation is ongoing with no resolution in sight. WP Engine has filed its third amended complaint with newly unredacted details about Automattic's conduct. The court has allowed most of WP Engine's claims to proceed past the motion to dismiss phase. Discovery is likely underway or about to begin.
Automattic continues to characterize the dispute as WP Engine simply rehashing old complaints, but the court's willingness to allow claims to proceed suggests the allegations have legal merit. The fact that previously sealed information is now being unredacted indicates the case is moving forward substantially.
The timeline is uncertain. Complex commercial litigation like this typically takes multiple years from filing to resolution. We could see developments over the next 1-2 years, but a final resolution might not come until 2026 or beyond. Some estimates suggest this case could take 3-5 years to fully resolve if it goes to trial.
In the interim, the WordPress ecosystem operates under uncertainty. Companies don't know whether trademark enforcement will become more aggressive or whether some resolution will emerge. Some companies might choose to settle with Automattic to reduce their legal risk, while others might await the outcome of the WP Engine litigation before making decisions.
Stakeholder Perspectives: Who Cares and Why
Different stakeholders in the WordPress ecosystem have different interests in the outcome of this dispute.
WordPress Hosting Companies have an obvious interest. They benefit from clarity about trademark licensing terms and they benefit if courts limit Automattic's enforcement power. Companies like Kinsta, Bluehost, Site Ground, and others are watching closely to understand how this affects their business models.
WordPress Agencies and Developers are interested because if licensing fees increase significantly, they may need to adjust their business models or pass costs to clients. The dispute affects their operating costs and margins.
The WordPress Foundation and Larger Community have an interest in preserving the open-source principles that make WordPress successful. If trademark enforcement becomes a significant barrier to entry, it could harm the diverse ecosystem that makes WordPress strong.
Smaller Competitors to WP Engine are watching to see if settlement or victory for WP Engine might help them too. If Automattic is forced to abandon aggressive royalty demands, smaller hosting companies benefit.
Automattic and Matt Mullenweg clearly have a stake in the outcome. Automattic benefits financially from trademark licensing fees. Mullenweg also has reputational stakes. If he's portrayed by courts as having abused trademark power or engaged in anticompetitive conduct, his reputation within the WordPress community is damaged.
Website Owners and End Users might not follow this dispute closely, but they have an indirect stake. If licensing costs increase significantly, those costs might get passed along in higher hosting fees or service costs. Conversely, if the dispute damages WordPress's ecosystem and development, that could affect the quality and rate of WordPress improvements.
Looking Forward: Resolution Scenarios and Timeline
Next 6 Months (Early to Mid-2025) Discovery will likely be in full progress. Both sides will be deposing witnesses and exchanging documents. Key evidence about Automattic's contacts with other companies and pressure on Stripe should emerge during this phase.
6-12 Months Out (Mid to Late 2025) Both sides will likely file summary judgment motions asking the court to resolve certain issues without going to trial. The court's rulings on these motions could potentially resolve the entire case or narrow the issues that need to be tried.
12-18 Months Out (Late 2025-2026) If the case isn't resolved through summary judgment, trial preparation would begin. Both sides would be preparing witnesses, exhibits, and legal arguments for trial.
Beyond 18 Months (2026 and Beyond) Trial would likely occur, potentially lasting several weeks given the complexity of the case. After trial, appeals would almost certainly follow, extending the timeline further.
However, settlement could occur at any point. Many commercial disputes resolve before trial, often once both sides have a clearer picture of the evidence and the strength of their positions.
The Bigger Picture: What This Means for Tech Companies
This dispute between WP Engine and Automattic isn't isolated. It's part of a broader pattern of tech companies and platforms trying to maximize control and revenue from their ecosystem dominance. Think about Apple's App Store, Google's Play Store, Amazon Web Services marketplace, or Meta's developer policies. When a company controls a platform that others build on, they face temptation to extract more value from that position.
WP Engine's lawsuit is essentially arguing that there are legal limits to how far you can push this dynamic. You can't use control of a trademark or platform to extract arbitrary payments from competitors or pressure other companies to terminate business relationships.
The regulatory environment around big tech is changing. The FTC, Department of Justice, and regulators in Europe are increasingly skeptical of how tech platforms use their market position. The WP Engine case is happening in this context. A court ruling that Automattic overstepped could have implications beyond WordPress, suggesting limits on how aggressively all platforms can enforce their rules against ecosystem participants.
Conversely, a court ruling favoring Automattic could embolden other platform owners to pursue similar royalty or contribution schemes with their own ecosystem companies.
Conclusion: The Unresolved Conflict
The WP Engine and Automattic dispute remains one of the most significant conflicts in the open-source software world, with implications far beyond these two companies. At its core, it's about the legitimate limits of control when a single company or person maintains authority over a widely-used open-source trademark.
WP Engine's allegations—that Automattic demanded unprecedented royalty payments, allegedly targeted multiple companies, and allegedly pressured payment processors to cut off a competitor—represent a level of aggressive enforcement that's uncommon in open-source. If these allegations are true, they demonstrate an important principle: control of a trademark, even one attached to open-source software, can be weaponized in ways that harm the broader ecosystem.
Automattic's position—that large companies profiting from WordPress should contribute fairly to the platform—has some merit in principle. But the execution through trademark enforcement and legal threats has created conflict rather than cooperation.
The courts will ultimately decide whether Automattic overstepped legal boundaries. But regardless of the legal outcome, the WordPress community faces a fundamental question about whether this is how open-source projects should be governed in the future. The answer to that question will affect not just WordPress but how other open-source projects balance the need for fair contribution with the need for a healthy, cooperative ecosystem.
For anyone in the WordPress ecosystem, the prudent approach is to monitor this case closely, diversify your business model away from dependency on the WordPress trademark alone, and advocate for clearer standards and more transparent governance in the WordPress Foundation. The future of WordPress—and of open-source software more broadly—may depend on how this dispute resolves.
FAQ
What is the WP Engine and Automattic dispute about?
The dispute centers on trademark licensing and fair contribution to the WordPress open-source project. Automattic CEO Matt Mullenweg demanded that WP Engine pay 8% of its gross monthly revenue as a royalty for using the WordPress trademark, claiming WP Engine wasn't contributing enough to the open-source project. WP Engine refused and filed a lawsuit alleging trademark abuse, intentional interference with business relationships, and antitrust violations.
Why did Mullenweg demand royalty fees from WP Engine?
Multenweg's stated rationale was that WP Engine was profiting substantially from WordPress without contributing proportionally to the platform's development. He believed larger companies making significant revenue from WordPress had a moral and financial obligation to support the project through royalty payments. However, WP Engine argues this demand was unprecedented, aggressive, and constitutes trademark misuse under the law.
What are WP Engine's main legal claims against Automattic?
WP Engine's claims include trademark infringement and abuse, intentional interference with business relationships (particularly the alleged pressure on Stripe), unfair competition, defamation, and antitrust violations. The company alleges that Automattic used control of the WordPress trademark not to prevent consumer confusion but to extract payments and control competitor behavior. The court has allowed most of these claims to proceed past the initial motion to dismiss phase.
Did Automattic really try to pressure Stripe to drop WP Engine?
According to WP Engine's complaint, Automattic allegedly approached Stripe after the lawsuit was filed and made claims designed to convince the payment processor to terminate WP Engine's account. If true, this would constitute illegal interference with business relationships. Automattic has not directly addressed this allegation, though they characterize all of WP Engine's claims as unsubstantiated.
How many other companies did Automattic allegedly target with royalty demands?
WP Engine alleges that Automattic targeted at least 10 other hosting companies and service providers beyond WP Engine with similar royalty demands or licensing requirements. Newfold Digital, a major web hosting conglomerate, is confirmed to already have a trademark licensing agreement with Automattic. The names of other companies were initially redacted in court filings but are gradually being revealed.
What role does the WordPress Foundation play in this dispute?
The WordPress Foundation technically owns the WordPress trademark, though Automattic has significant influence over trademark enforcement through Mullenweg and other executives. The Foundation hasn't publicly opposed Automattic's enforcement campaign, but they also haven't explicitly endorsed it. There's an ongoing question about whether the Foundation should more directly oversee trademark licensing to prevent Automattic from acting unilaterally.
Could WP Engine lose the right to use the WordPress trademark if they lose the lawsuit?
If the court rules in favor of Automattic, it would likely uphold their authority to enforce trademark licensing terms. However, even losing the lawsuit wouldn't immediately revoke WP Engine's trademark usage. Instead, it would establish that Automattic could legally demand royalty payments or other compliance terms. WP Engine would then face a choice between accepting those terms or attempting to rebrand their services.
What's the timeline for resolving this dispute?
Complex commercial litigation typically takes multiple years to resolve. Discovery is currently ongoing or beginning. Summary judgment motions could resolve certain issues within 6-12 months. If the case goes to trial, that could occur in 2026 or beyond. Total resolution, including appeals, could take 3-5 years or longer. Settlement could occur at any point in this process.
What would be a favorable outcome for WP Engine?
A favorable outcome for WP Engine would involve the court ruling that Automattic's trademark enforcement was abusive or exceeded legal authority, that the pressure on Stripe was illegal interference with business relationships, and that the conduct was anticompetitive. This would establish that trademark owners can't use their marks to extract arbitrary payments from competitors. Financial damages against Automattic would also strengthen the outcome.
How could this dispute affect other companies in the WordPress ecosystem?
If Automattic prevails or the case is settled with WP Engine accepting licensing terms, other hosting companies and service providers might face similar royalty demands. If WP Engine wins or the case clarifies that such demands overreach trademark authority, other companies gain protection from aggressive enforcement. The dispute has already created uncertainty that may slow investment in WordPress businesses until the legal situation clarifies.
What does this dispute mean for the future of open-source software?
This case raises fundamental questions about how open-source projects should handle trademark ownership and enforcement. A ruling that trademark owners can't use marks to extract arbitrary payments would protect the open-source model of allowing profitable companies to build on free software. Conversely, a ruling favoring Automattic might embolden other open-source projects to pursue similar licensing schemes, potentially changing the economics of the open-source ecosystem.
Key Takeaways
- WP Engine's third amended complaint reveals allegations that Automattic targeted at least 10 other companies with similar royalty demands and allegedly pressured Stripe into ending WP Engine's payment processing
- The court has allowed most of WP Engine's major claims including trademark abuse, intentional interference with business relationships, unfair competition, and antitrust violations to proceed past initial dismissal
- Automattic's 8% gross revenue royalty demand is unprecedented in open-source enforcement and raises serious questions about whether trademark law can be used to extract arbitrary payments from competitors
- The dispute has broader implications for how open-source projects should balance fair contribution expectations with avoiding aggressive enforcement that stifles ecosystem innovation
- Newfold Digital has already agreed to trademark licensing terms with Automattic, suggesting there's a broader pattern of companies being pressured to accept royalty arrangements
Related Articles
- How Deep AI Integration Transforms Customer Service ROI [2025]
- Meta's Facial Recognition Smart Glasses: Privacy, Tech, and What's Coming [2025]
- Meta's Facial Recognition Smart Glasses: What You Need to Know [2025]
- Retro Digital Cameras Hidden in Film Rolls: The OPT100 Neo Trend [2025]
- RentAHuman Review: The Reality of AI Gig Work in 2025
- Apple AirTags Deal Guide: Everything You Need to Know [2025]
