zooqueenandHanzo Dev 0a0f7c8f51 id-dev.hanzo.ai is the devnet's identity host, and stays on the devnet ...

The catalog gains id-dev.hanzo.ai: org hanzo on network devnet, client
hanzo-console, its issuer and /v1 its own origin (the dev cloud's IAM),
its app https://app-dev.hanzo.ai, its pay surface
https://app-dev.hanzo.ai/pay and its telemetry api-dev.hanzo.ai.

Three things in the portal sent an org-hanzo host to mainnet, and each now
reads the host's own entry:
- the alias redirect read one front door per org, so id-dev was sent to
  hanzo.id with its OAuth request; front doors are now per org per
  network, and a network with none stays put;
- a signed-in visit went to the brand's first app (hanzo.ai), the
  launcher, billing and the organization page linked mainnet; a host
  whose entry names `appUrl` links only its network's app and payUrl;
- telemetry went to api.hanzo.ai; an entry's `apiUrl` names its gateway.

Every mainnet entry names none of the new fields, so every mainnet host
resolves, redirects and links exactly as before.

Co-authored-by: Hanzo Dev <[email protected]>

2026-10-16 07:27:09 -07:00

..

src

id-dev.hanzo.ai is the devnet's identity host, and stays on the devnet

2026-10-16 07:27:09 -07:00

package.json

State a version once

2026-09-03 12:10:41 -07:00

tsconfig.json

fix(tenant): catalog-only hosts resolve their OWN brand; drop orphan divider

2026-06-20 02:38:31 -07:00