Why a sovereign cloud
When the institutions you build are intended to outlast you, you cannot rent your foundations. Osage Cloud runs on infrastructure the ecosystem owns and operates โ Kubernetes clusters under our own management, owned container registries, owned ingress.
What we run
- Compute: Kubernetes via Hanzo PaaS (platform.hanzo.ai).
- Edge and ingress: hanzoai/ingress with the static plugin and gateway.
- Containers: GHCR
ghcr.io/osage/*โ single namespace. - Builds: native amd64 and arm64 in parallel on owned runners. No QEMU emulation.
- Secrets: Hanzo KMS only. Plaintext secrets do not exist in this ecosystem.
What we do not run
Nginx. Caddy. Vendor-locked managed services for anything we can reasonably operate ourselves. There is exactly one canonical path for each concern, and we maintain it.
For partners
Tribal nations and aligned institutions who require sovereign hosting can co-locate workloads on the Osage Cloud at cost. Inquiries go through osage.tech.