A node is a physical or virtual server/machine. We don’t charge you per-node. We only charge in slabs of 100 nodes (1-100, 101-200, …)

Chkk Enterprise Plan is tailored for organizations that need additional support and customization. It includes all features of the Business Plan plus single sign-on (SSO), multi-organization support, custom integrations, premium support with response SLAs, and contractual uptime guarantees, making it ideal for enterprises with strict compliance requirements.

A Kubernetes upgrade cycle upgrades all clusters across all environments from a current Kubernetes version to a target version. For example, in a fleet with three environments (dev, staging, prod), an upgrade cycle from k8s v1.30 to v1.31 typically begins with dev clusters upgraded to v1.31 for early validation, followed by staging for integration testing, and concludes with prod upgrades once confidence is established. Chkk deems an upgrade cycle complete only when every cluster in all three environments is running the target version.

Yes, we offer volume discounts as the number of nodes and Upgrade Templates increases. Contact us to discuss your use case.

You are not charged for infrequent bursts of autoscaled nodes as Chkk uses the average number of nodes in every monthly measurement cycle. We compute this average node count based on a monthly measurement cycle that spans from the first day to the last day of every month. To compute average node count across the fleet, at the end of each measurement cycle, we take the sum of all node count measurements taken across all the clusters and divide it by the total number of measurements.

Chkk has a true-up forward policy, meaning that we don’t carry out chargebacks for scenarios where the consumption in a monthly measurement cycle exceeds the licensed count. If the new, steady-state number of nodes is expected to be higher, our customer success team will discuss the situation with you, and take steps to adjust your subscription for the next measurement cycles.