Price Model

This price model is replaced with a new one - it’s here for reference until all current customers are migrated. See Pricing for the current one.

APPUiO Managed billing is modeled like the Kubernetes distribution supplier model and is therefore different per flavor.

Units of billing

For each managed Kubernetes cluster, these units are counted:

  • Kubernetes Control Plane (API Server, Controller Manager, etcd)

  • Kubernetes Nodes running the Control Plane

  • Shared base services (Monitoring, Backup, Rancher Management Server, …​)

  • Cluster provisioning and configuration

  • Synfection (Project Syn Tools)

  • Cluster system services like load balancer, cert manager and others

  • Kubernetes Worker Nodes

  • Supplier fees (licenses/subscriptions - if applicable)

  • Unit per flavor:

    • Red Hat OpenShift: vCPU

    • Rancher: Node

Usually there are no one-time setup costs, except for On Premise installations. As a rule of thumb we calculate with setup costs on such infrastructures with two times the monthly costs (it heavily depends on the infrastructure).

How to find the price

To get the price for a managed Kubernetes cluster, choose:

  1. Flavor

  2. Infrastructure provider

    Including the amount of compute resources (number of vCPU or number and size of nodes)

  3. Service level

With these three choices the price can be offered. Get in contact with to get an offering.


The rating defines in which frequency units are counted and summed up. The rating of the units is per hour.

Each unit in use is summed up per hour (maximum of last hour). Each month will end up with a slightly different sum as it adjusts by the amount of days (specifically: hours) a month has and of course how the usage changes in a month. Usage reporting to the supplier is done by averaging the usage per month.


SKUs (Stock Keeping Unit) identify a particular item. They are composed like this:

<Managed|Unmanaged><Flavor><Provider><Service Level><Unit>
Example 1. Managed OpenShift on with Service Level Premium
Example 2. Managed Rancher on AWS with Service Level Standard
Example 3. Self-Managed Rancher Cluster

Some SKUs are independent of the "Provider" part. In this case the value is set to Any.

The SKU appears on the invoice to identify the line item.

The Invoice

appuio managed invoice example
Figure 1. APPUiO Managed Invoice - (Fake numbers!)

This is an example invoice for an APPUiO Managed OpenShift Cluster on with service level premium.


This column includes the name of the cluster, the ID, the SKU (see above) and a hint about the billed unit.


The consumed amount of the billing unit.


Price per unit as per the defined rating.


Summed up total.

The above invoice example reads like that: The cluster consists of two billed units: Cluster and Compute (each unit is on it’s own line).

First line

"per Cluster/hour" means that this unit - the cluster - has been used for 672 hour (equals 28 days).

Second line

"per VCPU/hour" means that this unit - the compute - has a total of 32'256 hours. To get a better understanding of this number it can be divided be the amount of the first line (cluster/hour). In this example we see that the cluster has 48 VCPUs.

Table 1. Hours to days
Hours Days