<-- Back

What is the user license counting mechanism in Mendix Private Cloud Standalone

Introduction

This article describes how Mendix determines and enforces user license limits for applications deployed with the Private Cloud Standalone deployment type. It explains which Runtime mechanisms are authoritative for license enforcement and which data sources are not used.

Environment

Applications hosted in Mendix on Kubernetes

Details

In Mendix Private Cloud Standalone deployments, user license limits are defined exclusively by the license agreement. These limits can include named users, concurrent users, and concurrent anonymous users.

When an application uses an offline license, Mendix does not use call-home reporting or the Metering Sidecar. License enforcement is performed locally by the Mendix Runtime and depends on the Runtime version and deployment configuration.

The Runtime evaluates user limits using internal logic. Named user limits are derived from Core.getNamedUserCount(), which is based on data from the [System]$User table. This count excludes the administrator account and users that are marked as inactive. Concurrent user limits are evaluated using additional Runtime logic such as Core.getConcurrentUserCount(boolean).

Metrics exposed through Prometheus are intended for monitoring and observability only. These metrics are not used by Mendix to enforce or validate license usage in Private Cloud Standalone deployments.

Internal information related

  • 255485
  • C0161BEMQ4B/p1754481176500129

Additional information

Mendix documentation:

 

 

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.

To provide feedback, please open a ticket here. Don't forget to include the article's URL along with the feedback you would like to provide.