Skip to content

What is the React Foundation and Why React Left Meta for Linux Foundation

The problem with single-company ownership

When I worked at an enterprise company in 2024, our architecture review board blocked React adoption. The reason? “What if Meta abandons it?”

I thought this was a weak argument. React had been open source for over a decade. Meta had invested heavily. But the concern kept coming up in technology decisions.

Then React moved to the React Foundation in October 2025, and I understood why the governance structure mattered more than I realized.

What the React Foundation actually is

The React Foundation is a non-profit organization hosted by the Linux Foundation. It now owns React, React Native, and JSX.

The foundation handles:

  • Infrastructure (GitHub repositories, CI systems)
  • React Conf organization
  • Financial support for ecosystem projects
  • Grants and community programs
  • Trademark management

But here’s the key distinction I learned: the foundation owns the assets, but it doesn’t control technical direction.

Why React needed to leave Meta

I watched the Reddit discussion after the announcement. One comment from ruibranco captured the core issue:

“This is a pretty significant governance shift. React living under Meta always had that subtle tension where teams had to trust that one company’s priorities wouldn’t suddenly diverge from the ecosystem’s needs. The Linux Foundation is about as neutral a home as you can get.”

The React blog stated it more formally: the project has “outgrown the confines of any one company.”

The problems with Meta ownership weren’t theoretical. tokagemushi described a common scenario:

“Companies that were hesitant about React’s Meta dependency now have less reason to worry. I’ve been in meetings where ‘what if Meta abandons it’ was a real blocker for adoption.”

These concerns affected real technology decisions. Enterprise architects evaluated React against alternatives like Vue and Angular partly because of governance uncertainty.

Who runs the React Foundation

The foundation structure includes:

Leadership:

  • Executive Director: Seth Webster
  • Board of Directors: Oversees funds, resources, and strategic direction

Founding Platinum Members (8 companies):

CompanyRole in React Ecosystem
AmazonAWS React deployments, frontend tooling
CallstackReact Native consulting, major OSS contributions
ExpoReact Native development platform
HuaweiDevice manufacturer, React Native apps
MetaOriginal creator, continues development
MicrosoftAzure, VS Code React tooling
Software MansionReact Native core contributions
VercelNext.js, React deployment platform

The diversity matters. No single company controls the foundation. Each platinum member has equal governance participation.

How technical governance stays independent

The React Foundation separates funding from technical decisions. This is the critical design choice that prevents corporate capture.

The official React blog stated:

“React’s technical direction should be set by the people who contribute to and maintain React. As React moves to a foundation, it is important that no single company or organization is overrepresented.”

Here’s how the separation works:

graph TB
subgraph "React Foundation Board"
A[Amazon] --- B[Callstack] --- C[Expo] --- D[Meta]
D --- E[Microsoft] --- F[Software Mansion] --- G[Vercel]
end
subgraph "Board Responsibilities"
H[Funding] --- I[Infrastructure]
I --- J[Events]
J --- K[Grants]
end
subgraph "Technical Governance - INDEPENDENT"
L[Contributors] --- M[Maintainers] --- N[Technical Decisions]
end
Board -->|"Provides resources"| H
Technical -.->|"No direct control"| Board

The board funds React. The contributors build React. These roles don’t overlap.

What this means for different stakeholders

For individual developers:

React works the same as before. This is a governance change, not a technical one. But I see stronger long-term sustainability and more transparent decision-making.

For enterprises:

The governance structure reduces vendor-lock-in concerns. Major tech companies have invested in React’s future through foundation membership. Internal approval processes for React adoption face fewer objections.

For the ecosystem:

The foundation provides financial support for important community projects. Infrastructure and events get more resources. Contributors have a clearer path to influence React’s direction.

Why the Linux Foundation specifically

I researched why React chose the Linux Foundation over creating an independent foundation or joining another organization.

The Linux Foundation provides:

  • Institutional credibility in open source governance
  • Existing infrastructure for legal, financial, and operational support
  • Neutral governance model that prevents single-company control
  • Experience managing large-scale open source projects (Linux, Kubernetes, Node.js)

The foundation model worked for Kubernetes, which moved from Google to the Cloud Native Computing Foundation (CNCF, a Linux Foundation subsidiary). Kubernetes adoption accelerated after the governance transition.

What I learned about open source governance

Before this announcement, I didn’t think about governance structures. I focused on technical features, performance, and API design.

But governance affects sustainability. Projects owned by single companies face different risks than foundation-governed projects:

Governance ModelRisks
Single CompanyCompany priorities may diverge from community needs; acquisition can change direction; business decisions can override technical decisions
FoundationSlower decision-making; more bureaucracy; funding dependent on member companies

React chose foundation governance to solve the enterprise adoption blocker. The tradeoff is more process overhead, but the benefit is broader ecosystem participation.

Summary

In this post, I explained why React moved from Meta ownership to the React Foundation. The key point is that single-company ownership created a real blocker for enterprise adoption—teams worried about “what if Meta abandons React”—and foundation governance under the Linux Foundation provides neutral stewardship.

The React Foundation owns React’s assets but doesn’t control its technical direction. Eight founding platinum members share governance responsibility. Technical decisions stay with contributors and maintainers.

For developers, React continues as before. For enterprises, the governance structure removes a common objection to adoption. For the ecosystem, foundation support means more resources for community projects.

Final Words + More Resources

My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me

Here are also the most important links from this article along with some further resources that will help you in this scope:

Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!

Comments