Skip to content
DocumentationTry Hanzo
console.hanzo.ai

Hanzo Console

One admin for everything you run

Every product on Hanzo Cloud has a module here — providers and models, keys, applications, stores, agents, clusters, domains, billing. Sign in once and the sidebar is whatever your organization actually uses.

/v1
One API behind it
OIDC
Sign in with Hanzo IAM
Per-org
Data scoped to your org
OSS
MIT or Apache-2.0

A module per product, one shell around them

Add what you use. Hide what you don't. The shell stays the same.

Providers and models

Every model your organization can call, and which provider serves it. Connect an account of your own and its models appear beside the ones we run.

Usage and balance

A usage record per call and one balance per organization, so spend is attributed where it happened instead of totalled at the end of the month.

Keys

Issue an API key, scope it, revoke it. The key you paste into a client is minted here, and revoking it here is what stops it working.

Applications and stores

Register an app, hand it an identity, give it a store. The console writes the same resources the CLI does, because both are clients of the same API.

Find it by typing it

A command palette reaches every module and every record without learning where anything lives. The sidebar is yours to reorder and prune.

Scoped to the org on your token

Sign-in is OIDC against Hanzo IAM. What you see is what your organization owns, and switching organization switches the whole page — there is no global view to fall into by accident.

The console is a client. So is your code.

Everything on these screens is a call to api.hanzo.ai/v1, and the typed clients are generated from the same document.

app.py
from hanzoai.cloud import ApiClient, Configuration, ChatApi

# The key you issued in the console
config = Configuration(
    host="https://api.hanzo.ai",
    access_token="sk-...",
)

with ApiClient(config) as client:
    print(ChatApi(client).post_v1_chat_completions())

# The call, and what it cost, are on your
# organization's usage before it returns.
Open Source Revenue Sharing

Up to 5% of compute goes back to open source

Every deployment is SBOM-verified. Contributors to Console earn a share of compute revenue — transparent, on-chain, and customizable by the community.

Open the console

Sign in with your Hanzo identity. The organization you land in is the one that gets billed, and everything on these screens belongs to it.

Open source

License: Apache-2.0hanzoai

Get Console

Operator console for the cloud