What we build

Sovereign systems — software and physical infrastructure that the ecosystem owns, operates, and can never be evicted from. Our deployments run on Hanzo PaaS and the hanzoai/ingress + hanzoai/static + hanzoai/gateway stack. We do not run nginx; we do not run Caddy. One way to do everything.

Stack

• Compute & orchestration: Kubernetes (DOKS, GKE), Hanzo PaaS deployments.
• Identity: Hanzo IAM, surfaced as Osage ID.
• Secrets: KMS only — never plaintext, never in-repo.
• Settlement: Osage Network — sovereign chain.
• Ingress & edge: hanzoai/ingress + static plugin, white-labeled by hostname.
• Containers: GHCR for sister companies; isolated registries by org.
• Builds: native amd64 + arm64 in parallel on owned runners. No QEMU.

Operating Principles

• Forwards only — no backwards-compatibility shims.
• Composable, orthogonal, complete separation of concerns.
• Simplicity over cleverness; one canonical path per concern.
• White-labeling by domain — no brand bleed between ecosystems.

Sister Properties

• osage.cloud — sovereign cloud.
• osage.network — settlement layer.
• osage.id — identity.