Skip to main content
Version: 12.x (Current)

Self-Hosted installation requirements

Mia-Platform Console Self Hosted installation implies that the customer has already installed in its systems all the required software and tools.

Self-Hosted installation architecture

The following picture shows the high-level architecture for a Self-Hosted Mia-Platform Console installation. The communication between the components must be allowed as shown in the architecture.

Self-Hosted installation architecture

The following software and hardware recommendations are for installing Mia-Platform Console On-Premises.

Software and Hardware prerequisites


Blanks cell in the following table are for tools that do not require a specific version or a minimum of RAM and CPU.

ToolVersionMinimum CPUMinimum RAM
Auth Provider OktaSaaS
GitLab> 14.x
GitHub> 3.x
Azure AD B2CSaaS
Bitbucket Server> 8.x2 cores3 GB
Git Provider GitLab> 14.x4 cores4 GB
GitHub> 3.x4 cores32 GB
Azure ReposSaaS
Bitbucket Server> 8.x2 cores3 GB
Secret Manager GitLabSaaS
CI/CD Tool GitLab CI Runners> 14.x1 core2 GB
GitHub ActionsSaaS
Azure PipelinesSaaS
NoSQL database MongoDB Enterprise> 5
<= 7
2 cores2 GB
Redis Cache Redis>= 6
<= 7
2 cores2 GB
Runtime Kubernetes> 1.20
<= 1.27
2 CPU requests4 GiB Memory requests
Container image registryAny container image registrySaaS
Object Storage Google Cloud StorageSaaS
S3-Compatible Object StoragesSaaS
Key Management Service Google Cloud PlatformSaaS
Local KeySaaS

Reference Architecture

The following is an example architecture for the installation of the Mia-Platform Console supporting ~500 users and ~200 projects:

GitLab1418 core32 GB200 GB
GitLab CI Runners1421 core2 GB25 GB
MongoDB Enterprise532 core8 GB20 GB
Redis71 GB1 GB
Google Kubernetes Engine1.212 worker nodes4 core8 GB
Google Container RegistrySaaS
Google Cloud StorageSaaS
Google Cloud Platform KMSSaaS

Designating the Console Super User

When installing an instance of Mia-Platform Console, a user with the Console Super User role will be added to the database automatically.

The Console Super User role has been designed exclusively for backoffice administration purposes. When assigned to a user, this role implies full visibility and management of all CMS resources.