Building in the
open.
We publish what we build, fix the bugs we find upstream instead of patching them in private, and pay the projects we depend on. The commitments below are specific enough to hold us to.
What Hanzo is built on
The projects our platform actually runs on, each with its licence and the people who maintain it.
The database underlying all our stateful services
PostgreSQL LicenseOur Stewardship Commitments
We hold ourselves to explicit, public commitments — not vague marketing language.
We ship open source first
Every tool we build for ourselves gets published. If it's useful to us, it belongs to the community. No internal-only forks.
We contribute upstream
When we find bugs or missing features in projects we depend on, we fix them upstream — not in private patches.
We never lock in what we open
Anything published under MIT or Apache-2.0 stays that way. We will never relicense open repos to extract commercial value.
We credit our foundations
Our platform is built on hundreds of open-source projects. We acknowledge, link to, and financially support the communities and maintainers who make this possible.
We fund what we depend on
Through GitHub Sponsors, Open Collective, and direct partnerships, we invest back into the projects that power Hanzo.
We welcome all contributors
Good code can come from anywhere. We maintain a contributor-friendly CONTRIBUTING.md, respond to PRs within 48 hours on active repos, and recognize every contributor.
20% to the author of the code that runs
Verify that you own a repository, and every org that deploys a project built from it pays you 20% of its metered spend, accrued each period.
What we publish
Read from GitHub by every build: the year of commits, the languages and the repositories of each ecosystem, then every organization.
69 organizations checked · non-fork repositories
repositories with a commit in 30 days
as GitHub counts them
as GitHub counts them
- hanzoai/guishell: the wordmark's files in oxfmt's form
- hanzoai/appChrome: the name lights with the bar's highlight, never an outline (0.2.56)
- hanzoai/cisite: the release's record of itself goes after its pages
- hanzoai/uifooter: the legal line beside the copyright, the wordmark at the row's end, the panel's ground; 8.29
- hanzoai/aimodels: ?id= narrows the listing to the models a page names
- hanzo-docs/docssdks: @hanzo/app and @hanzo/mod, what each ships
- hanzoai/benchmarksrecord: add Kai-1.9 Cand29 joint coherence capability benchmark results
- hanzoai/botchore(license): finish Apache-2.0 documentation and desktop attribution
Public GitHub snapshot · read Oct 30, 06:13
Read the sourceThe primary language of each of 1,617 original repositories, as GitHub reads it
Our own Git forge, git.hanzo.ai. Its figures are its own, read from it signed out, and never added to the GitHub figures.
public repositories, open to read signed out
of them mirror our repositories on GitHub, Hanzo, Lux and Zoo together
community projects published there
Forge listing · read Oct 30, 2026
Explore the forgeEvery organization
Hanzo
35 organizations · 1,617 repositoriesHanzo Skills — AI skill modules
AI infrastructure for the agentic era — LLM gateway, MCP tools, multi-agent SDKs, and dev tools. Techstars '17.
[Legacy] Hanzo app templates — see github.com/hanzoai for current projects
Frontier language models from 600M to 480B parameters — edge to cloud. Open weights, Zen architecture.
Hanzo KMS — Enterprise Secret Management & Key Infrastructure
[Legacy] Hanzo app templates — see github.com/hanzoai for current projects
Hanzo business apps
JavaScript SDK + libraries for Hanzo Ecosystem
Accelerate growth 🚀
Core modules for Hanzo Platform.
Hanzo KV — distributed key-value store
Hanzo Studio — AI development environment
Hanzo Bot — AI agent and bot framework
Hanzo Zero Trust — programmable zero-trust networking for AI infrastructure
Hanzo Network — decentralized AI compute marketplace
Hanzo S3 — S3-compatible object storage
Hanzo UI — React component library (Radix + Tailwind)
Lux
4 organizations · 405 repositoriesZoo
1 organizations · 40 repositoriesContribute & Earn
We welcome contributions of all kinds — code, documentation, bug reports, and feature requests. Every contribution earns a share of compute revenue through our OSS Revenue Sharing program.