Summary

Automattic is cutting back its contributions to the WordPress core project. It aligns with the 45-hour weekly pledge of WP Engine. The shift could reshape the open-source ecosystem. It will force other companies to step up WordPress site development.

Content

WordPress is in trouble.

WordPress has been the backbone of the internet for almost two decades. It is the silent force behind blogs, businesses, and billion-dollar brands. It is the reason countless people launched companies and found their voices online.

Automattic—the company behind WordPress.com—was the invisible safety net for most of that time. Now that net is gone.

In 2025, Automattic will slash its contributions to WordPress core from 2,500+ development hours per week to just 45.

The open-source community is reeling. WordPress is not software. It is a mission, a movement, and a belief that the Internet should belong to everyone.

The company that led the charge is walking away now.

The Legal War That Sparked It All

This is not a mere restructuring. It is a battle — a messy, ego-driven fight between two of the biggest players of WordPress.

Automattic’s CEO, Matt Mullenweg, called WP Engine “a cancer to WordPress” in 2024.

He accused the WP Engine of making millions from WordPress without giving enough back.

WP Engine did not stay silent.

They hit back with a lawsuit. They accused Automattic of trademark abuse as well as anti-competitive behavior.

And now, as the lawsuit drags on, Automattic is doing something no one expected: pulling back from WordPress.org entirely.

Instead, they are focusing on profit-making products like WordPress.com and WooCommerce.

How This Affects WordPress (and Why You Should Care)?

Automattic’s Dotorg team worked behind the scenes for years. The team kept WordPress core alive.

Now that team is gone. It will affect WordPress site development.

What This Means for You

Fewer updates and more delays

WordPress 6.8, set for April 2025, might be the first release to stall. Progress will slow with fewer WordPress developers.

Security is still a priority—but at what cost?

Automattic says its limited hours will go toward security fixes.

Other companies must step up fast

The smaller contributors will have to carry the load without Automattic. But will they?

WordPress is the foundation of millions of websites.

What happens when the foundation starts to crack?

Who is Leading WordPress Now?

Someone must step up with Automattic stepping back.

The new top contributor is rtCamp with 454 weekly hours.

The other companies trying to fill the gap are as follows.

• Multidots – 291 hours
• GoDaddy – 256 hours
• Awesome Motive – 222 hours
• 10up – 189 hours
• Yoast – 157 hours

Most WordPress Development Companies felt invincible because Automattic handled so much of the workload for years. The ecosystem is scrambling to adjust.

Why Automattic Pulled Back: The Ugly Truth

This seems like a business rivalry has gone too far at first glance.

But if you dig deeper, it is clear:

Automattic did not want to step back. It had to.

Automattic is Running Out of Cash

BlackRock slashed Automattic’s valuation by 50% in 2024. That is not a small dip. That is freefall.

And when does money get tight? You cut what does not make money.

Internal Drama is Tearing Automattic Apart

Nearly 80% of Automattic’s WordPress.org team quit in 2024. Many left because they disagreed with Mullenweg’s war against WP Engine. Pulling back from WordPress core was not a choice, with so many key developers gone. It was inevitable.

Automattic is Playing Hardball

Automattic is making a statement by cutting back to just 45 hours per week.

“If WP Engine—and other companies—want to profit from WordPress, they better start giving back.”

The Future of WordPress: What Happens Now?

WordPress has always been community-driven.

But let’s be honest:

That “community” was mostly Automattic.

Now, these are the possible outcomes.

Other companies rise to the occasion

If rtCamp, GoDaddy, and others step up, WordPress can stay strong.

WordPress badly slows down

Fewer WordPress developers – slower updates, delayed features, and security nightmares for WordPress Development Companies.

A new, decentralized model emerges

Some, like Joost de Valk (Yoast’s founder), want to move away from centralized leadership.

A major leadership shift

More people are questioning whether Mullenweg should control WordPress’s future.

Final Thoughts: A New Chapter for WordPress

This isn’t just business as usual. It’s a wake-up call. For years, Automattic carried WordPress. It is stepping back now—and the rest of the community must decide what happens next. The era of Automattic leading WordPress is over. It is up to the community now. The real question is, is it ready?

Author Bio:

Tejas Shah is the CEO and Director of ipath Solutions, an IT services company that specializes in custom software, web, mobile, and eCommerce solutions. With over 15 years of experience, he has led over 200 successful projects, helping businesses around the world adopt new digital technologies. His innovative approach and focus on client success have made ipath Solutions a trusted partner for many. He is dedicated to setting industry standards and helping businesses grow in the digital world.