Skip to main content

Uniview Documentations

Uniview is a comprehensive enterprise readiness platform for infrastructure over OpenStack and Kubernetes, designed to enable monetization and business ready of open source technologies with modern user console, billing, enterprise integration. It delivers a unified, production-grade layer that transforms standard open-source compute infrastructures into structured, highly auditable, and automated cloud systems. It's the enabler that turns open source to business.


Current Version: 2026-august

Key Underlying: OpenStack Gazpacho 2026.1

Key Underlying: CNCF Graduated Projects

Key Underlying: Ceph Latest


Current documentation is a repo for subjects around install, daily operation and feature discovering etc

Modular Infrastructure Mapping

Uniview solutions are highly modularized. In the meanwhile all components can cozily work together so that for end user he perceives as one credential, one sign in, one console, one bill for everything of multiple Openstack clusters, multiple Kubernetes clusters, one or multiple Ceph backends. Main Level-1 services at Uniview include: Virtual Machine service, Network, Volume, Swift Container, CAPI Cluster, Namespace, Pods, Load Balancer and Database as a service. A service provider can choose partial or all without hard dependencies on others. The multi-tenant Kubernetes architecture has zero dependency on the OpenStack offering, and vice versa.

  • IDP, Uniview IDP: the foundational element for both OpenStack and Kubernetes Solution, and you could resuse your own Keycloak, Zitadel, Keystone or deploy optimized Uniview IDP distros
  • OpenStack-Console-Core: a full OpenStack API implementation for popular OpenStack services, such as Nova, Neutron, Cinder, Magnum etc.
  • Scheduler: a standalone scheduling service for automated backup, snapshot, shelving, billing monitoring etc.
  • Kubernetes-Console-Core: a full Kuberentes API implementation for major Kubernetes kinds CRUD. K8s console intakes baremetal-cluster, capi magnum cluster, namespace user and virtual cluster user
  • Billing Engine: Same engine for full OpenStack project based rating, and namespace based rating of Kubernetes
  • Collector-OpenStack: a rabbitmq based full OpenStack object lifecycle interceptor for composing billing foundation.
  • Collector-Prometheus: a Prometheus based Kubernetes namespace resource consumption query for composing billing foundation of GPU, CPU and Ram.

The current docs facilitate to have a hands-on testing by following quick start, or get idea of the ecosystem and features. Given every infrastrucure is different, talking with our support team is always a great idea too.