The Kato Difference

Positioning Differences

Kato uses cloud-native application-level packaging and abstraction. Users don’t need to learn about containers and k8s, or understand the underlying infrastructure such as servers, networks, and storage. Managers can manage containers, k8s and related infrastructure at the resource level. And realize the scenario-based application delivery process (software development delivery process, enterprise IT management process, enterprise application market ecology) on top of the application.

Other container platforms are mainly to simplify container management and expand the functions of containers, conceptually embody containers and k8s, users must learn containers and K8s, and implement scenario-based solutions at the granularity of containers.

Cloud Native

Kato’s idea of ​​cloud native practice is similar to Heroku, but it has expanded its extension in the field of To B delivery.

Scene Difference

Kato has different management interfaces according to different groups of people. It has application management consoles for development, testing and application operation and maintenance, command line tools and resource management backends for system operation and maintenance, and application markets for application delivery personnel and end users.

Other container platforms usually manage containers and infrastructure in a unified management interface, and are mainly oriented to the crowd for operation and maintenance.

Difference from K8s

Kubernetes is the underlying technical component of Kato. There is no need to learn containers and k8s to use Kato. Kato is compatible with containers and K8s standards. Kato runs on k8s, and k8s is responsible for the operation and scheduling of all applications.

Reference Technical Architecture