# Conflicts: # README.md
Hub
Model catalog with versions, lineage, artifact metadata.
A brand-neutral fork in the hanzo-ml
organization — the open-source ML lifecycle estate. Branding is
consumed at runtime from a brand package via the
@<org>/brand contract; the same code deploys under
any white-label brand with zero source changes.
Brand package
This fork imports brand configuration from a runtime brand package
following the contract used across the open-source ML estate. Set
BRAND_PACKAGE to the npm package name; the fork's frontend (where
applicable) calls loadBrand() at boot to hydrate the singleton from
that package's brand.json.
Available brand packages:
| Package | Brand |
|---|---|
@hanzo/brand |
default / Hanzo AI |
@luxfi/brand |
Lux Finance |
@zooai/brand |
Zoo Labs |
@osage/brand |
Osage |
@parsdao/brand |
Pars DAO |
@cyrusdao/brand |
Cyrus DAO |
@migaprotocol/brand |
Miga Protocol |
@vccross/brand |
VC Cross |
@mlc/brand |
MLC |
@zenlm/brand |
Zen LM |
Or any custom reseller package conforming to the same schema.
Multi-tenant via IAM
Every request carries a JWT. The brand package's iam block specifies:
issuer— JWT issuer URLjwksUrl— JWKS endpointtenantClaim— JWT claim with the org/tenant ID (defaultorg_id)tenantHeader— HTTP header that propagates the validated tenant ID (defaultX-Org-Id)
The tenant ID scopes all storage, queries, and resource ownership. Cross-tenant access is forbidden by default.
Quick start (reseller deployment)
export BRAND_PACKAGE="@<your-org>/brand" # e.g. @luxfi/brand
The frontend (this fork's case: pipelines ships the React DAG UI;
the other 7 are read-only reference forks) loads the brand at boot.
The backend reads the brand package's iam block for JWKS + tenant
configuration.
Role
Read-only reference for the Rust operator's Model + ModelVersion CRDs. Metadata in per-tenant SQLite via the lifecycle estate's base storage; blobs in the VFS-backed artifact store.
The canonical control plane for the ML lifecycle estate is the Rust
operator at hanzoai/operator.
See HIP-0109
for the lifecycle CRD set.
Upstream sync
This fork stays current with upstream via the GitHub merge-upstream API. No upstream code is modified in this fork; only the 5 markdown files at root are added.
gh api -X POST /repos/hanzo-ml/hub/merge-upstream \
-f branch=main
See UPSTREAM_README.md for the original project documentation.
License
Apache-2.0. See NOTICE for attribution.
See also
- DESIGN.md — design system reference (mirrors the brand package's design spec)
- BRAND.md — brand package contract and reseller guide
- MULTI_TENANT.md — tenant isolation contract
- HANZO_CHANGES.md — divergence from upstream
- HIP-0109 Hanzo ML Cloud Toolkit