Beeper, the company that attempted to launch an app that let Android users use iMessage a few months ago, has been acquired by Automattic, the giant that owns WordPress. As part of the deal, Beeper is opening up its messaging app, which attempts to corral all messaging services into one inbox, to everyone across platforms, and shutting down its waitlist for good. Automattic's CEO says that messaging will be the next big pillar of the company. Its team intends to replace a lot of messaging methods with an open-source system.

Beeper, the company that attempted to launch an app that let Android users use iMessage a few months ago, has been acquired by Automattic, the giant that owns WordPress. As part of the deal, Beeper is opening up its messaging app, which attempts to corral all messaging services into one inbox, to everyone across platforms, and shutting down its waitlist for good. Automattic's CEO says that messaging will be the next big pillar of the company. Its team intends to replace a lot of messaging methods with an open-source system.

WordPress.org has taken a significant step by banning WP Engine, a popular hosting provider, from accessing its resources. This decision was announced by Matt Mullenweg, co-creator of WordPress and CEO of Automattic, who stated that WP Engine's access to essential components like themes and plugins would be revoked due to ongoing legal disputes. Mullenweg accused WP Engine of attempting to monopolize the WordPress experience by wanting to control various aspects of the platform, including user login systems and update servers. The ban has immediate repercussions for WP Engine customers, who are now unable to install plugins or update themes, which has raised concerns among users and developers about the potential security vulnerabilities this creates. WP Engine has acknowledged the issue and is reportedly working on a solution, assuring customers that their sites' performance and security remain unaffected for the time being. The conflict between WP Engine and Automattic escalated after Mullenweg publicly criticized WP Engine for its business practices, labeling it a "cancer to WordPress." This prompted WP Engine to issue a cease-and-desist letter, claiming that Mullenweg's actions were unwarranted and detrimental to the broader WordPress ecosystem. In response, Automattic sent its own cease-and-desist letter, alleging trademark infringements by WP Engine. The underlying tension revolves around the use of WordPress trademarks, with the WordPress Foundation asserting that WP Engine has repeatedly violated its trademark policy. Mullenweg indicated that Automattic has been seeking a licensing agreement with WP Engine, offering options for direct fees or contributions to the open-source project, although the specifics of these contributions were not detailed. This situation highlights the complexities within the WordPress ecosystem, which powers a significant portion of the internet. The ongoing dispute not only affects the two companies involved but also has broader implications for developers and users who rely on WordPress for their websites.

WordPress.org has taken a significant step by banning WP Engine, a popular hosting provider, from accessing its resources. This decision was announced by Matt Mullenweg, co-creator of WordPress and CEO of Automattic, who stated that WP Engine's access to essential components like themes and plugins would be revoked due to ongoing legal disputes. Mullenweg accused WP Engine of attempting to monopolize the WordPress experience by wanting to control various aspects of the platform, including user login systems and update servers. The ban has immediate repercussions for WP Engine customers, who are now unable to install plugins or update themes, which has raised concerns among users and developers about the security and functionality of their sites. Many in the WordPress community expressed frustration over the disruption, highlighting the potential risks for small organizations that rely on WP Engine for their website hosting. In response to the ban, WP Engine acknowledged the issue and assured customers that their sites' performance and security were not compromised, although they could not access updates through the WordPress admin interface. WP Engine criticized Mullenweg's actions as an abuse of power that disrupts the broader WordPress ecosystem, affecting not just their customers but also plugin developers and open-source users. The conflict between WP Engine and Automattic escalated after Mullenweg publicly criticized WP Engine for its business practices, labeling it a "cancer to WordPress." This led to a series of cease-and-desist letters exchanged between the two companies, with WP Engine alleging that Mullenweg threatened aggressive legal action if they did not comply with demands for revenue sharing. Automattic countered with claims of trademark infringement by WP Engine, asserting that the latter had repeatedly violated WordPress's trademark policies. The situation highlights the complexities within the WordPress ecosystem, which powers a significant portion of the internet. The ongoing dispute raises questions about the future of collaboration and competition among hosting providers and the implications for users who depend on these services. Mullenweg indicated that the core issue revolves around trademark rights and licensing agreements, suggesting that Automattic has been seeking a resolution with WP Engine for some time.

Matt Mullenweg, the CEO of Automattic, has recently intensified tensions with WP Engine, a prominent hosting company, by rescinding an earlier offer for an 8% licensing deal. This shift suggests a potential corporate acquisition of WP Engine by Automattic. In a recent interview, Mullenweg indicated that Automattic is now seeking a greater share of WP Engine’s annual revenue or equivalent contributions to the WordPress project, stating, “That deal’s not on the table anymore. We’re seeking more, not 8%.” He expressed frustration over what he perceives as WP Engine's lack of leverage in negotiations, hinting that a takeover could be on the horizon. The conflict escalated after Mullenweg publicly criticized WP Engine during his keynote address at WordCamp US 2024, labeling the company as a “cancer to WordPress.” He accused WP Engine of profiting from the WordPress ecosystem without adequately contributing to it, contrasting their contributions with those of Automattic. Mullenweg's remarks have been fueled by years of failed negotiations, leading him to adopt a more aggressive public stance against WP Engine and its main investor, Silver Lake. In response to Mullenweg's accusations, WP Engine has remained relatively quiet but did send a cease and desist letter to Automattic, claiming that Mullenweg's demands for significant financial contributions were baseless and threatening. WP Engine defended its contributions to the WordPress community, highlighting its financial support for events and educational resources. The situation further escalated when Automattic issued its own cease and desist letter, alleging that WP Engine was violating the “WordPress” and “WooCommerce” trademarks. Automattic claims that WP Engine has built a substantial business based on unauthorized use of these trademarks and is demanding compensation for lost licensing revenue. As tensions mounted, Mullenweg took drastic measures by banning WP Engine from accessing WordPress.org resources, which disrupted services for WP Engine customers. This action was met with accusations from WP Engine that Mullenweg was misusing his control over WordPress to harm their business. Mullenweg countered these claims by alleging that WP Engine had been siphoning revenue from WooCommerce partnerships. Despite the ongoing conflict, Mullenweg remains resolute, stating that he feels justified in his public criticisms and is prepared for a potential legal battle or corporate takeover. The situation continues to evolve, with both companies navigating a complex landscape of trademark disputes, public relations challenges, and the future of their relationship within the WordPress ecosystem.

Automattic, the parent company of WordPress.com, recently made headlines by demanding that WP Engine, a competing hosting service, pay 8 percent of its monthly revenue. This demand came before a public dispute regarding the use of the WordPress trademark and the open-source nature of the WordPress project. Automattic's proposal, which was shared on September 20, outlined a seven-year agreement that would allow WP Engine to use the WordPress trademark in exchange for this revenue share, which could be paid either as a royalty or as salaries for WP Engine employees contributing to the WordPress.org project. If WP Engine opted for the royalty payment, Automattic indicated it would publicly acknowledge WP Engine's contributions to the Five for the Future initiative, which encourages companies to allocate resources to the WordPress.org project. Conversely, if WP Engine chose to pay the 8 percent through employee contributions, Automattic would gain extensive audit rights over WP Engine's operations, including access to employee records and time-tracking. However, WP Engine rejected Automattic's proposal, asserting that its use of the WordPress trademark and related abbreviations fell under fair use. Following this rejection, Automattic abandoned the terms, citing WP Engine's alleged deceptive practices. The conflict escalated during the WordCamp conference, where Automattic's CEO, Matt Mullenweg, publicly criticized WP Engine for not contributing adequately to the WordPress community and threatened legal action over trademark usage. In response, WP Engine issued a cease and desist order against Automattic, claiming harassment from Mullenweg. Automattic dismissed these claims as false and reiterated its request for a revenue-sharing agreement. As tensions mounted, WordPress.org, under Mullenweg's leadership, banned WP Engine from its servers, effectively cutting off access to updates and plugins. In response, WP Engine developed its own solution to maintain service continuity for its customers. This ongoing dispute highlights the complexities of trademark rights and contributions within the open-source community, as both companies navigate their competitive landscape while addressing the expectations of the WordPress ecosystem.

On October 3, 2024, Automattic publicly responded to a lawsuit filed by WP Engine, which they described as baseless and flawed. The company firmly denied the allegations made against them, asserting that the claims were gross mischaracterizations of reality. Automattic expressed confidence in their legal position and indicated their intention to vigorously contest the lawsuit while also seeking remedies against WP Engine. To bolster their defense, Automattic has engaged Neal Katyal, a prominent attorney and former Acting Solicitor General of the United States, along with his firm Hogan Lovells, LLP. Katyal, who has a history of successfully opposing the law firm representing WP Engine, stated that he found no merit in the complaint after reviewing it thoroughly. He expressed eagerness for the federal court to consider the case. Automattic emphasized that their primary focus has always been on protecting the integrity of WordPress and their mission to democratize publishing. They contrasted their commitment to customer service with WP Engine's approach, suggesting that WP Engine does not prioritize its customers in the same way. This response highlights Automattic's determination to defend its reputation and the values it stands for in the face of legal challenges.