Who Shapes OpenClaw? The Foundation, Maintainers, and Donors in the Public Record

July 31, 2026
OpenClawBlog Team

A local-first assistant can read messages, call tools, and hold credentials. That makes stewardship a practical question. Who maintains the code? Who signs releases? Who can change the project’s direction when a major donor, employer, or founder has a different interest?

The public record now supports an organizational profile of OpenClaw. The project began with Peter Steinberger, then moved toward a Foundation structure while he joined OpenAI. The Foundation names a full-time team, a wider maintainer group, and donors from several technology companies and institutions. Its repository also publishes contribution and security rules.

That record is useful, but it is not a complete governance file. The opened sources do not establish every board power, donor agreement, succession rule, or decision right. This article reports what the sources say and marks the gaps instead of turning an announcement into an org chart.

Start with the record, not an org-chart guess

There are four kinds of evidence here. The Foundation announcement describes the structure and names its initial staff. Peter Steinberger’s February 2026 statement records his move to OpenAI and his plan for OpenClaw. The Foundation’s people directory gives a current public roster. The repository’s contribution guide and security policy show how technical work and security reports are expected to move.

Those sources answer different questions. A staff page can establish a published role. A pull request can establish participation in a change. A donor page can establish who the Foundation says supports it. None of those records, on its own, proves who has the final legal authority over the project.

The Foundation is the stated steward

On July 8, 2026, OpenClaw published Introducing the OpenClaw Foundation. The announcement says OpenClaw is an American 501(c)(3) nonprofit, that the Foundation exists to keep the project open and independent, and that the whole product will remain MIT licensed. It also says the Foundation employs the core team and signs every release.

The announcement is by Dave Morin and Peter Steinberger. It describes the Foundation as the institution responsible for governance, funding, and the people working on OpenClaw. It also says that councils on agent identity, agent profiles, evaluations, and enterprise deployment are being convened around the project.

That is a meaningful change in the public description of OpenClaw. The project is presented as a nonprofit with staff and a wider community, rather than as a tool maintained by its creator alone. It is still a statement written by the project itself. The announcement does not publish bylaws, a board charter, donor terms, or a formal succession process. The safe wording is therefore that the Foundation is the stated steward and employer of the core team, not that every governance question has been settled in public.

The named people form several layers

Peter Steinberger remains the clearest name in the project’s origin story. The OpenClaw credits page names him as the creator. In his own February 14 statement, Steinberger wrote that he was joining OpenAI to work on agents and that OpenClaw would move to a foundation while staying open and independent.

The July Foundation announcement adds an important qualification. It says Steinberger continues to make especially important technical calls. That describes a strong technical role. It does not mean that he is the only maintainer, the only employee, or the legal owner of the Foundation.

Dave Morin occupies a different position in the public record. He is listed as Chairperson on the Foundation’s people page, and he co-authored the July announcement with Steinberger. That supports describing Morin as a named organizational leader. It does not provide a full account of his board powers or the relationship between the chairperson role and technical decisions.

Vincent Koc is listed as Chief Architect in the Foundation announcement and on the people page. The same announcement names Josh Avant, Patrick Erichsen, Dallin Romney, Jason Sy, and Gideon Adegbesan in engineering, alongside Koc. Its operations list includes Jen Vescio for partnerships, Matt Jasie for finance, Hannes Rudolph for community, and Kelly Pike for talent.

The people directory I accessed on September 13 gives a later public snapshot. It lists a Foundation team that includes Vincent Koc, Ayaan Zaidi, Dallin Romney, Gideon Adegbesan, Hannes Rudolph, Jason Sy, Josh Avant, Josh Lehman, Patrick Erichsen, and Vyctor Brzezowski. It lists Dave Morin as Chairperson, with Jen Vescio, Kelly Pike, Matt Jasie, and Mollie Anderson in operations roles.

That later directory should not be mistaken for a frozen July 31 roster. It has no publication date, and staff pages can change. Its value is narrower: it shows how the Foundation currently chooses to describe its full-time team and the roles attached to those names.

Core maintainers are not the same thing as donors

The Foundation directory separates its full-time team from its core maintainers. It says the maintainers review pull requests, guide architecture, and keep the codebase healthy while contributing on behalf of themselves and companies building on OpenClaw.

The roster includes maintainers associated with NVIDIA, Microsoft, OpenAI, Tencent, Atlassian, Red Hat, Hugging Face, Xiaomi, and Paradigm, as well as people listed as independent. Examples include Kevin Lin, Nik Pash, and Sarah Fortune under OpenAI; Agustin Rivera, Devin Robison, Jacob Tomlinson, Nir Paz, and Pavan Kumar Gondhi under NVIDIA; and Sally O’Malley under Red Hat.

This is evidence of a multi-company maintainer group. It is not evidence that those companies control the roadmap. The directory itself says the maintainers contribute on behalf of themselves and the companies building on OpenClaw, but it does not publish a voting formula, a veto list, or a rule for resolving disagreements between employer interests and project interests.

The distinction matters for readers deciding whom to trust. A person with a maintainer role may review code or guide an architectural discussion. A donor may provide money or infrastructure. A Foundation officer may handle operations. Those responsibilities can overlap, but the public pages do not say that they are interchangeable.

OpenAI’s role is documented, while its limits remain less visible

Steinberger’s February statement says he chose OpenAI as the place to continue his work on agents. It also says OpenAI already sponsored OpenClaw and had made strong commitments to let him dedicate time to the project.

The July Foundation announcement gives more detail. It says OpenAI supports inference for OpenClaw, shipped Codex Security to harden the platform, established Claw Labs inside OpenAI under Steinberger, and became a major donor to the Foundation. It also says OpenAI committed to supporting the Foundation’s stewardship of OpenClaw as open and independent.

The current repository README describes OpenAI as a donor rather than an owner. It says donors and infrastructure sponsors support the Foundation but do not own or direct the project. The Foundation’s donor page makes a similar distinction and describes OpenAI as supporting inference and the project’s independence.

Those sources support a careful description: OpenAI is an employer of the creator, a donor, and a technical supporter named by the project. They do not support calling OpenClaw an OpenAI product. They also do not reveal employment terms, funding amounts, conflict rules, or whether any Foundation document gives a donor special rights. That missing detail is not proof of hidden control. It is simply outside what these public pages establish.

Donor disclosures show support, not a control register

The Foundation’s donor page names Offline Holdings, the University of Michigan, OpenAI, Microsoft, and NVIDIA among its supporters. The July announcement also describes support from organizations such as Amazon, Red Hat, GitHub, Vercel, Cloudflare, Convex, Blacksmith, Tencent, Atlassian, and others in different partner or infrastructure roles.

The list tells readers which organizations the Foundation publicly associates with funding or support. It does not show how much each organization contributes, whether contributions are restricted, or what happens if a donor disagrees with a technical decision. The opened pages do not publish those terms.

That is the part of the profile where editorial inference is unavoidable. A Foundation with several donors may have more financial room than a project relying on one sponsor. It may also need clear conflict and disclosure rules as those relationships grow. The first point follows from the existence of multiple named supporters. The second is a governance requirement to check, not a claim that the Foundation has failed it.

The repository makes some stewardship visible

The repository turns a few parts of the operating model into something contributors can inspect. The README says OpenClaw is developed in the open by the Foundation, Peter Steinberger, and the community. It links to contribution guidance, identifies the Foundation as the steward, and says releases are signed under its identity.

The contribution guide directs readers to the Foundation’s people page for the current team and core maintainers. It also says the maintainer group is expanding selectively, that maintainers are expected to triage issues and review pull requests, and that people are added slowly and deliberately. This is a published route into technical stewardship, even if it is not a constitution.

The security policy gives another view of responsibility. It asks researchers to report vulnerabilities privately and requests an affected version or commit, reproduction steps, demonstrated impact, and an explanation of which trust boundary is crossed. The policy says security work is shared across OpenClaw maintainers, including engineers and security researchers from organizations such as NVIDIA and Tencent.

These documents matter because they describe work that has to happen after an announcement. They also show the limits of the project’s security model. The policy treats OpenClaw as local-first infrastructure for trusted operators, not as a shared multi-tenant boundary between adversarial users on one Gateway. That is a technical assumption for operators to evaluate, not a statement about the Foundation’s legal structure.

A compact reading of the evidence

Checks for someone deciding whether to depend on OpenClaw

The following are proposed checks, not tests run for this profile.

1. Match the decision to the published role. Use the people directory and contribution guide to identify whether you are dealing with a Foundation officer, a full-time engineer, a core maintainer, or a general contributor.
2. Check the exact release you plan to run. The README says releases are signed by the Foundation, but this article did not independently verify a release signature or inspect a particular artifact.
3. Read the donor and independence statements together. Then look for current governance documents that explain conflicts, donor restrictions, board appointments, and what happens if a major sponsor leaves.
4. Read the security policy before connecting other people to one agent. If users do not share a trusted operator boundary, treat separate Gateways, operating-system users, or hosts as a deployment question rather than assuming session labels provide isolation.
5. Recheck the public pages before a long-lived deployment. The Foundation’s people directory is a current web page, not a dated historical register, and the article’s access date is September 13, after the requested July 31 publication date.

Where the profile must stop

The strongest limitation is source independence. Most of the evidence comes from OpenClaw, its Foundation, or its repository. Those are the right sources for the project’s own roles, policies, and announcements. They are not the same as an audited governance review or an independent legal filing.

In the material opened for this article, there is no published Foundation charter, board roster with decision powers, donor agreement, trademark policy, or succession document. That sentence describes an evidence gap in the reviewed sources. It does not claim that no such documents exist elsewhere.

The current roster also needs careful handling. A page accessed on September 13 may include changes made after July 31. It is included because the question asks what public record exists, but the date of the snapshot is part of the record. Readers should not quote it as a complete historical picture of the Foundation on the publication date.

The answer in one sentence

The public record describes OpenClaw as a Foundation-stewarded project centered on creator and technical steward Peter Steinberger, chaired by Dave Morin, supported by a full-time staff and cross-company maintainer group, and funded by named donors including OpenAI. It does not yet make every decision right visible, so the responsible profile ends with the roster, the operating rules, and the unanswered governance questions.

Sources

1. Introducing the OpenClaw Foundation — published 2026-07-08; accessed 2026-09-13. Supports the Foundation’s stated nonprofit structure, initial staff, stewardship role, release signing, councils, and OpenAI relationship.
2. OpenClaw, OpenAI and the future — published 2026-02-14; accessed 2026-09-13. Supports Steinberger’s public statement about joining OpenAI, moving OpenClaw to a Foundation, and keeping it open and independent.
3. The people building OpenClaw — publication date not listed; accessed 2026-09-13. Supports the published Foundation team, Chairperson and Chief Architect roles, core maintainer roster, affiliations, and community structure.
4. Funded as a public good — publication date not listed; accessed 2026-09-13. Supports the Foundation’s stated donor list, registered 501(c)(3) description, and distinction between donors and project control.
5. OpenClaw credits — publication date not listed; accessed 2026-09-13. Supports the project’s identification of Peter Steinberger as creator and its named contributor credits.
6. OpenClaw repository README — publication date not listed; accessed 2026-09-13. Supports the repository’s public governance description, Foundation stewardship claim, release-signing claim, donor distinction, and community contribution links.
7. Contributing to OpenClaw — publication date not listed; accessed 2026-09-13. Supports the maintainer-selection, contribution-review, and issue-triage expectations.
8. OpenClaw Security Policy — publication date not listed; accessed 2026-09-13. Supports the private reporting route, required evidence for reports, shared maintainer responsibility, and trusted-operator security assumptions.