The Kubeark licensing model is based on two main pillars: templates and clusters. These pillars determine the cost of the license, as well as the level of functionality and scalability that the platform provides.
The license for the Kubeark Platform is generated by Kubeark and is currently available only as an offline license.
Templates refer to pre-built environments that are designed to run specific types of workloads or applications. These templates can include the necessary infrastructure, platform, and software components to run the workload or application, and are designed to make it easy for users to get started. The number of templates that a license includes is one of the key factors that determine the cost of the license.
Clusters refer to the number of separate and independent environments that the license allows to be created. Each cluster is a complete, isolated environment that can include its own set of resources, such as virtual machines, storage, and network. The number of clusters that a license includes is another key factor that determines the cost of the license. The more clusters allowed by the license, the more workloads and applications that can be run simultaneously, which makes it more powerful and scalable.
The Kubeark license model is designed to provide a flexible and cost-effective way to access the platform. It enables customers to pay only for the resources and functionality that they need, while also providing the ability to scale up as their requirements change.
The license is based on the customer's needs and can be generated to include a specific number of templates and/or a specific number of clusters.
Templates are pre-configured sets of settings and data that can be used to quickly create new clusters and get started with the platform. Clusters are the primary unit of organization in the Kubeark platform and allow users to manage and access their data, workflows, and reports.
The license can be generated to include the specific number of templates and clusters that the customer needs, depending on their usage and requirements. For example, a customer who needs to manage a large amount of data and workflows may require a license that includes a larger number of templates and clusters, while a customer with more limited needs may require a license that includes a smaller number of templates and clusters.