Template Kickbacks (25% OSS Revshare)

The Hanzo Open Source Partner Program routes users to sovereign cloud infrastructure, equips builders with production tooling, and pays open-source developers on every deploy.

Revenue Share Structure

Modeled on the industry-standard Railway OSS partner program, Hanzo Cloud provides up to 25% revenue share on net metered platform spend:

How Spend Is Calculated

• Kickbacks are derived strictly from net metered cloud infrastructure spend (CPU, GPU, RAM, disk storage, egress bandwidth, and managed database services).
• Kickbacks are paid out of Hanzo's platform margin — deploying organizations pay standard compute rates with zero markup or hidden fees.
• Accruals are computed continuously and locked into append-only ledger entries (models/ossaccrual).

The 25% Managed OSS Escrow Pool

Hanzo Cloud commits 25% of all cloud spend generated by open-source workloads back to the ecosystem.

Even if an open-source maintainer has not yet joined the partner program or linked a payout destination:

1. Automated Attribution: Template and dependency attribution engines tag deployments with the upstream GitHub repository or package coordinates.
2. Escrow Safeguard: 25% of metered platform spend is set aside into an immutable escrow ledger with status held.
3. Claiming Funds: When the verified author connects their GitHub organization and registers a wallet or payout account via platform.hanzo.ai/authors, all accumulated escrowed funds transition from held to queued and settle during the next payment cycle.

Settlement & Multi-Rail Payouts

Hanzo supports sovereign, global payout options:

• HUSD Stablecoin (Hanzo EVM): Real-time, gasless on-chain settlement on the Hanzo sovereign network directly to your non-custodial wallet.
• Direct Crypto Rails: Automatic payouts in ETH, USDC, or native sovereign tokens.
• Stripe Connect: Direct fiat deposit in 130+ currencies to global bank accounts.
• Hanzo Cloud Credits: Immediate 1:1 platform credit bonus for hosting your own infrastructure and CI/CD pipelines.

Eligibility & Verification

To verify your template and qualify for the full 25% kickback:

1. Open Source License: Blueprint repositories must carry an OSI-approved open source or permissive license (MIT, Apache-2.0, BSD, MPL, etc.).
2. Repository Ownership: Authenticate repository ownership via GitHub OAuth or cryptographic commit signature.
3. Health & Security Standards:
   • Valid container images or Dockerfiles
   • Clean security vulnerability scanning
   • Clear environment variable documentation and sensible defaults
   • Functional healthcheck probes (/healthz)

Getting Started

1. Deploy as a Template: Package your repo with a hanzo.yml blueprint.
2. Submit for Verification: Navigate to Marketplace → Submit Template in Hanzo Console.
3. Connect Payouts: Enter your sovereign wallet address or Stripe Connect account under Settings → OSS Payouts.