• Introduction
• Software Requirements
• Requirements to Host Build.One Applications On-premise
• Preliminary Considerations
• Container Management
• Exemplary Hardware Requirements

Introduction

The Build.One Development Framework will be delivered in the cloud, using a code repository and cloud development environment.

Build.One Applications developed with the Development Framework can be deployed and used either

• on the Build.One Cloud,
• on a public cloud, or
• on-premise.

Software Requirements

While Build.One Applications are containerised in principle, the underlying container software still has requirements. We require:

• Linux, preferably Ubuntu Long-term Releases (LTS), minimum version: 22.04

Requirements to Host Build.One Applications On-premise

Preliminary Considerations

Before going to the requirements, let’s check the different parameters, which are necessary to decide the concrete requirements:

• How many environments should be deployed on the server? Such environments may be, for example: test, staging, security-hub and/or production.
• Is the database to be included on the platform inside a container or installed outside containers and connected?
• Number of users who will be using the application.

Container Management

Since Build.One is deployed via Docker Containers, a container management software is needed. We recommend Portainer. Portainer and other software involved in the deployment on-premise must be completely managed by the customer. For installing Portainer, we strongly recommend a Linux server be used.

Exemplary Hardware Requirements

For a customer environment, with around 10 simultaneous users, as well as an external database also installed on the server the minimum hardware requirements are:

• 16 GB RAM (should increase with number of users)
• 4-core CPU
• >500 GB disk space

Consult with one of our certified Implementation Partners or us directly for your specific requirements based on usage projections.

Back to Documentation

Back to Home Page