Haiku, Inc. Incorporates as a Nonprofit to Fund Development
Founded in July 2003 by Michael Phipps in Rochester, New York, Haiku, Inc. gave the OpenBeOS/Haiku project a formal nonprofit structure for accepting donations and funding contractor work.
Haiku, Inc. was incorporated as a 501(c)(3) nonprofit organization in July 2003, in Rochester, New York, founded by Michael Phipps — the same person who had started the OpenBeOS project nearly two years earlier, in the days immediately after Palm’s acquisition of Be Inc. ended BeOS development.
Why a volunteer project needed a formal nonprofit
By 2003, OpenBeOS had been running for two years as an informal, volunteer-driven effort — functional for coordinating code contributions, but not structured to accept financial donations, hold funds, or enter into contracts on the project’s behalf. Establishing Haiku, Inc. as a registered nonprofit gave the project a legal entity capable of doing exactly that: accepting donations from the community, and later, funding specific, scoped development work through paid contracts.
What this enabled later
This nonprofit structure is the same institutional mechanism that later funded focused development work like packagefs, when contractors Ingo Weinhold and Oliver Tappe were engaged to build out Haiku’s modern package management system starting around 2011. Without a formal nonprofit already in place, funding that kind of sustained, scoped contractor work would have been considerably more difficult to organize.
A deliberately narrow, supportive role
Haiku, Inc.’s purpose is specifically to support the Haiku Project and the development of the Haiku operating system — it functions as financial and organizational infrastructure behind the project, rather than a company selling or controlling Haiku as a product. This mirrors how many other open-source projects have structured community-facing nonprofit foundations, though Haiku, Inc.’s founding predates several better-known examples in the wider open-source world.
Why founding this structure two years into the project, rather than immediately, made sense
OpenBeOS’s founders in 2001 were focused on the immediate, urgent problem of continuing BeOS’s functionality at all — establishing formal nonprofit infrastructure wasn’t the most pressing need in the project’s earliest, most improvisational days. By 2003, with the project’s direction and community established, the practical need for a way to accept donations and fund real development work had become clear enough to justify the additional organizational overhead.
Sources: Haiku, Inc. — Haiku Project, About Haiku, Inc. — haiku-inc.org