Hummingbot Foundation primary sources — 2026-08-12

Project status in this pass

• This upkeep pass was about taxonomy, not new-project intake.
• The question was whether Hummingbot needed a separate entity note under companies/ rather than only a project note under projects/.
• The answer in this pass was yes: the named Foundation now concentrates enough release, governance, connector-admission, sponsorship, docs, and community workflow authority to deserve its own note.

Primary-source snapshots

1) Foundation page

• URL: https://hummingbot.org/about/
• Key excerpt:
  • The page says Hummingbot Foundation is a not-for-profit organization established in the Cayman Islands.
  • It says the Foundation’s mission is to democratize high-frequency trading by maintaining the open-source Hummingbot code repository and the HBOT governance system.
  • It also says Foundation staff review and merge pull requests, administer proposals and elections, maintain Snapshot, manage Discord, assign developer bounties, package Docker releases, and maintain the website and docs.
• Why it mattered:
  • This is the clearest first-party statement that one named organization still owns the practical release and governance shell around Hummingbot.

2) Governance page

• URL: https://hummingbot.org/about/governance/
• Key excerpt:
  • The page says HBOT holders can vote on proposals that approve pull requests, add or remove connectors, allocate bounties, re-elect the Foundation board, and change the governance system.
  • It also says governance was simplified in January 2025 into one HGP proposal type with a single Snapshot space and unified parameters.
• Why it mattered:
  • Connector inclusion, codebase change approval, and governance-process changes still run through infrastructure the Foundation administers.

3) Governance whitepaper

• URL: https://hummingbot.org/about/whitepaper/
• Key excerpt:
  • The page says the Foundation’s role is to coordinate ongoing maintenance and improvement of the open-source Hummingbot codebase.
  • It says the Foundation plans to own the software license, maintain commit access, implement approved proposals, publish official releases, update documentation, support users, and manage treasury assets.
  • It also describes exchange agreements, bounty administration, and the board’s multisig oversight role.
• Why it mattered:
  • Even if some details are historical, this remains the strongest first-party articulation of the Foundation as the governing release and maintenance operator.

4) Docs overview

• URL: https://hummingbot.org/docs/
• Key excerpt:
  • The docs say Hummingbot is maintained by Hummingbot Foundation.
  • They say all official Foundation code is stored in the official GitHub and DockerHub organizations and that users should download software only from those official sources.
  • They also frame the stack as multiple modules: Gateway, Dashboard, Hummingbot API, Hummingbot MCP, and Quants Lab.
• Why it mattered:
  • Official release provenance and the trusted repo boundary are explicit operator powers, not just generic open-source facts.

5) Exchanges / connector page

• URL: https://hummingbot.org/exchanges/
• Key excerpt:
  • The page offers three routes for official connector inclusion: DIY governance, Foundation-managed bounty management starting at $10,000,anddirectFoundationsponsorshipstartingat$50,000.
  • It says the Foundation handles developer assignment, code review, testing, and community approval processes for bounty-managed integrations.
  • It lists current Foundation partners and directs exchanges to Foundation operations contacts and a bounty escrow agreement.
• Why it mattered:
  • Connector maintenance and exchange access are not just community accidents; they are partly routed through a named organization’s business and governance workflow.

6) Foundation-introduction blog post

• URL: https://hummingbot.org/blog/introducing-the-hummingbot-foundation/
• Key excerpt:
  • The post says CoinAlpha, the company behind Hummingbot, planned to establish a new open-source foundation to coordinate ongoing maintenance and improvement of Hummingbot through sponsors, contributors, maintainers, and users.
  • It says the Foundation would earn income from exchange fee-share agreements and administering bounties.
• Why it mattered:
  • This clarifies the origin of the operator split: Hummingbot the framework and Hummingbot Foundation the governance / maintenance entity are intentionally distinct.

7) Main repository README

• URL: https://raw.githubusercontent.com/hummingbot/hummingbot/master/README.md
• Key excerpt:
  • The README frames Hummingbot as open-source trading infrastructure with official docs, official releases, and a broad connector surface across centralized and decentralized venues.
  • It routes users to official docs, reporting, newsletter, and community channels operated under the Hummingbot umbrella.
• Why it mattered:
  • The repo confirms that the framework is broader than one bot and that the official distribution shell around it is part of the real operating surface.

Working conclusion

Hummingbot should remain a projects/ note because the framework itself is analytically useful: strategy execution, exchange connectors, Gateway middleware, API surfaces, and the broader trading stack still matter on their own. But the Hummingbot Foundation now clearly deserves its own companies/ note because the named organization controls enough of the practical release, governance, sponsorship, and distribution shell that who runs the easiest official path? is a separate and important question from how does the framework work?