System Requirements Summary

ProMDM supports deployment in Docker only for all services. There are few options for deployment, Docker single host with docker-compose, Docker Swarm, Kubernetes or Openshift. For smaller installations, Docker single host with docker-compose is preferred. 

Server Operating System Support:

  •  Ubuntu Server 

Database support:

  •  POSTGRESQL 11 and 12 (Active/Passive Configurations) 

Data Storage (configuration, mobile application files)

ProMDM uses GlusterFS system for data storage replication between nodes in Docker Swarm.

PKI Support:

  •  ProMDM CertHat TinyPKI Server

  • Microsoft Active Directory Certificate Services with Certificate Web Services installed (Windows 2012 R2, 2016 and 2019 Servers supported). 

LDAP support:

  • Microsoft Active Directory (only Secure LDAP over TCP 636 supported) 
  • Any LDAP compliant Directory

Claims-Based Authentication (Modern Web Authentication) supported providers:

  • Windows Azure Active Directory
  • Microsoft ADFS (Oauth2 integration) 
  • Integration with any Identity solution that supports standards like Oauth2 or OpenID Connect
  •  SAML 2.0 and SWT tokens supported 

 Load Balancer requirements 

ProMDM requires an external load balancer/reverse proxy like F5. It is recommended that an external load balancer/reverse proxy terminates TLS connections and redirect traffic to ProMDM services over http. 

It is possible to use ProMDM NGINX as TLS endpoint, but not recommended. 

ProMDM Reporting services 

ProMDM Reporting is based on the Postgres database and Microsoft PowerBI Tool for generating reports. It is recommended to use a dedicated Postgres server for reporting. Microsoft PowerBI desktop app could be used for generating reports or PowerBI services (needs licenses from Microsoft). ProMDM Reporting for PowerBI requires an additional license. 

Log Collection 

ProMDM supports Elastic Search for log collection using standard Docker log driver “gelf”. 


Hardware requirements for single-server deployment (up to 2000 devices)

ProMDM can be deployed on physical servers or virtual servers. We recommend deployment in a virtual environment (Hyper-V, VMWare) with the following VM requirements.

Type Minimum Optimal
VM with remote database

(Postgres or managed Postgres) 

  • CPU: 2 core
  • RAM: 4 Gb
  • Disk size: 50 Gb
  • CPU: 4 core or more
  • RAM: 8 Gb
  • Disk size: 100 Gb
VM with Postgres Database
  • CPU: 2 core
  • RAM: 8 Gb
  • Disk size: 50 Gb (small installations)
  • CPU: 8 cores
  • RAM: 16 Gb
  • Disk size: 100 Gb

Please contact us for VM requirements for SaaS Cloud installations.

Hardware requirements for cluster deployment (for 50.000 managed devices) 

ProMDM can be deployed on different Docker environments, like Docker single host with docker-compose, Docker Swarm, Kubernetes or OpenShift. Hardware requirements are specified in the table. 

ProMDM Services: 

  • 4 Docker worker nodes minimum (dedicated for ProMDM) 
  • 3 Docker manager nodes for Docker Swarm configuration 

ProMDM Database 

  • 2 servers (Postgres Active/Passive Configuration) 

ProMDM Log Collection: 

  • 1 server with ELK 

ProMDM Reporting Services: 

  • 1 server with Postgres