Remote OpenClaw

Remote OpenClaw Blog

Who Owns OpenClaw? Foundation, Governance, and Open Source Status [2026]

Published: ·Last Updated:
What changed

This post was reviewed and updated to reflect current deployment, security hardening, and operations guidance.

What should operators know about Who Owns OpenClaw? Foundation, Governance, and Open Source Status [2026]?

Answer: Peter Steinberger is the creator of OpenClaw and a well-known figure in the developer community. Before OpenClaw, he was best known for his work in the Apple and iOS ecosystem, where he built developer tools used by thousands of app developers worldwide. He founded PSPDFKit, a widely-used PDF framework, and was recognized as a leading voice in mobile.

Updated: · Author: Zac Frulloni

Who owns OpenClaw? Learn about the OpenClaw Foundation, Peter Steinberger's move to OpenAI, community governance, and what open source means for OpenClaw's future.

Marketplace

Free skills and AI personas for OpenClaw — deploy a pre-built agent in 15 minutes.

Browse the Marketplace →

Shape the Future

Join 500+ OpenClaw operators shaping the project's direction. Governance discussions, deployment guides, and real-world results.

Who Is Peter Steinberger?

Peter Steinberger is the creator of OpenClaw and a well-known figure in the developer community. Before OpenClaw, he was best known for his work in the Apple and iOS ecosystem, where he built developer tools used by thousands of app developers worldwide. He founded PSPDFKit, a widely-used PDF framework, and was recognized as a leading voice in mobile development.

Peter started what would become OpenClaw as a personal project — an AI assistant he could text from his phone that would handle tasks autonomously. The project was originally called MoltBot, then forked and renamed to ClawdBot, and eventually rebranded to OpenClaw in early 2026 as the community grew and the project's scope expanded far beyond one person's side project.

Peter's background in building developer tools shaped OpenClaw's architecture. The project prioritizes extensibility (anyone can build plugins and skills), clean APIs (integrations are standardized and well-documented), and developer experience (clear error messages, good documentation, a helpful CLI). These are not accidental features — they reflect decades of experience building tools that developers actually want to use.


Peter's Move to OpenAI

In February 2026, Peter Steinberger announced that he was joining OpenAI. This sent a wave of concern through the OpenClaw community. The biggest questions were immediate: Would OpenAI absorb OpenClaw? Would the project become proprietary? Would development slow down or stop?

Peter addressed these concerns directly. He had anticipated them and prepared for the transition months in advance. Before joining OpenAI, he completed two critical steps:

  1. He established the OpenClaw Foundation as an independent legal entity to hold the project's intellectual property, trademarks, and governance structure.
  2. He transferred all project ownership — the GitHub repository, the npm packages, the domain names, and the ClawHub marketplace — to the foundation.

Peter's move to OpenAI was a personal career decision, not a corporate acquisition. OpenAI did not buy OpenClaw. They hired Peter for his expertise in developer tools and AI agents, but OpenClaw remained an independent project.

OpenAI became a sponsor of the OpenClaw Foundation, providing financial support for infrastructure costs (servers, CI/CD, CDN). But sponsorship is not ownership. OpenAI has no seats on the foundation's governing board, no veto power over technical decisions, and no special access to the codebase beyond what any open source contributor has.


The OpenClaw Foundation

The OpenClaw Foundation is the legal entity that owns and governs the OpenClaw project. It was established as a non-profit foundation with a charter that explicitly prevents any single company — including OpenAI — from gaining controlling influence over the project.

The foundation's responsibilities include:

  • Holding intellectual property: The OpenClaw name, logo, and trademarks are owned by the foundation, not by any individual or company.
  • Managing infrastructure: The GitHub organization, npm packages, Docker Hub images, and ClawHub marketplace are all operated by the foundation.
  • Coordinating releases: Major version releases are planned and approved through the foundation's governance process.
  • Accepting sponsorships: Companies can sponsor the foundation financially, but sponsorship does not grant governance rights.
  • Protecting the open source license: The foundation ensures that OpenClaw remains open source and that the license terms are respected.

This model is similar to other successful open source foundations like the Linux Foundation, the Apache Software Foundation, and the Cloud Native Computing Foundation. It provides stability and independence that a single-maintainer project cannot offer.


How Governance Works

OpenClaw uses a community governance model with elected maintainers. Here is how it works:

Maintainers: A team of elected maintainers makes day-to-day technical decisions. They review and merge pull requests, triage issues, and manage releases. As of March 2026, there are seven maintainers from five different countries and four different companies. No single employer has a majority of maintainers.

Governance proposals: Major changes — new features that change the project's direction, breaking changes to the API, changes to the governance structure itself — go through a formal proposal process. Anyone can write a proposal. Proposals are discussed publicly on GitHub Discussions, and maintainers vote on them after a comment period.

Elections: Maintainers are elected annually by active contributors. Anyone who has had a pull request merged in the past 12 months can vote. Anyone can nominate themselves or be nominated by another contributor.

Code of conduct: The foundation enforces a code of conduct that applies to all project spaces — GitHub, Discord, forums, and events. This ensures that the community remains welcoming and productive.

The governance model is designed to prevent capture. No company can stack the maintainer team with their employees. No individual can make unilateral decisions that affect the project's direction. The community has real power, and that power is protected by the foundation's charter.


Open Source License and What It Means

OpenClaw is released under a permissive open source license. This is not just a label — it has specific legal implications that matter for anyone using or building on OpenClaw.

What the license allows:

  • Use OpenClaw for any purpose, including commercial use
  • Modify the source code to suit your needs
  • Distribute your modified version
  • Build and sell commercial products and services on top of OpenClaw
  • Use OpenClaw internally without any reporting or licensing obligations

What the license requires:

  • Include the original copyright notice and license text in any distribution
  • Do not use the OpenClaw name or logo to imply endorsement without permission

What the license does NOT do:

  • It does not require you to open source your modifications (unlike copyleft licenses like GPL)
  • It does not restrict commercial use in any way
  • It does not give the foundation or any contributor the right to revoke your license

This means that even if the foundation were dissolved tomorrow, everyone who has a copy of OpenClaw's source code would retain the right to use, modify, and distribute it forever. The license is irrevocable. This is the strongest guarantee of independence that open source can provide.


Can You Build a Business on OpenClaw?

Absolutely. The permissive license explicitly allows commercial use. Several types of businesses already exist in the OpenClaw ecosystem:

  • Managed hosting providers: Companies like Remote OpenClaw deploy and manage OpenClaw instances for clients who do not want to handle their own infrastructure.
  • Skill developers: Independent developers and companies build and sell premium skills on ClawHub.
  • Consultants and integrators: Professionals who specialize in configuring OpenClaw for specific industries or use cases.
  • White-label solutions: Companies that build their own branded AI assistant products using OpenClaw as the underlying platform.

The foundation encourages commercial activity because it strengthens the ecosystem. More businesses building on OpenClaw means more contributors, more skills, more documentation, and more resources flowing back into the project. It is a virtuous cycle.

Join the ecosystem

4 AI personas and 7 free skills — browse the marketplace.

Browse Marketplace →

What This Means for OpenClaw's Future

The combination of a foundation structure, community governance, and a permissive open source license means that OpenClaw's future is not dependent on any single person, company, or decision. This is by design.

Peter Steinberger built something that outlives his personal involvement. Even from OpenAI, he occasionally contributes code and participates in governance discussions. But the project no longer depends on him. It depends on the community.

For operators, this means you can invest in OpenClaw with confidence. Your deployment will not be abandoned because a founder changes jobs. Your skills and integrations will not become obsolete because a company decides to pivot. Your data remains yours because the software that manages it is open source and cannot be taken away.

The community is the owner. And the community is growing. Over 500 operators are active in the Skool community alone, sharing deployment guides, security configurations, workflow automations, and real-world results. Thousands more contribute on GitHub, build skills for ClawHub, and participate in governance.

OpenClaw's ownership structure is one of its greatest strengths. In a world where AI companies are consolidating, raising prices, and changing terms of service, OpenClaw remains free, open, and community-controlled. That independence is worth protecting — and worth being part of.