Boundless Server Enterprise (BSE) is intended for a distributed cloud environment. This means that it is not installed on a single computer, but is instead split up across multiple virtual machines which are in turn managed by autoscaling and load-balancing software. This is referred to as a BSE deployment.

Structure of a BSE deployment

A typical BSE deployment consists of the following layers:

Host Infrastructure

The network of virtual machines which the containers run on. This is typically provided by a third-party cloud hosting provider, but you can use your own local cloud infrastructure if you desire. Many of the larger cloud hosting providers also provide provisioning and container management solutions.


Provisioning and Container management

Provisioning an environment involves deploying all the containers and any other components that make up the environment to the host infrastructure. Typically, there is some configuration that describes the deployment environment, which is used by the provisioning software to construct the environment.

The container management software manages the containers when they are running. It is responsible for load-balancing, autoscaling, and reprovisioning failed containers. It often (but not always) overlaps with the provisioning software.



The virtual machines running the application software. This consists of BSE, Redis, and PostGIS in a minimal deployment, but can also include other databases such as MongoDB or Oracle, and other software including monitoring applications and single-sign-on providers. In a typical autoscaling setup, there are a variable number of containers running the same Docker image (this is managed by the container management layer)

The Boundless Server Enterprise software consists of a single Docker image—all the other constituents of a BSE deployment are available from third parties.

Deploying BSE

Given the the variety of options available, there are innumerable ways to go about deploying BSE.

We recommend deploying Boundless Server Enterprise in AWS, using the Helm package manager for Kubernetes. Helm charts helps you define deployments, install, and upgrade BSE in Kubernetes with ease.

Deploying BSE on AWS

For instructions on deploying BSE using AWS, Helm and Kubernetes, first install Kubernetes on AWS, then use Helm to deploy BSE on Kubernetes.

If you require assistance deploying BSE on AWS using other provisioning and container management software, please contact us.

Deploying BSE on Microsoft Azure

If you require assistance deploying BSE on Microsoft Azure, please contact us.

Deploying BSE on GCP

If you require assistance deploying BSE on the Google Cloud Platform, please contact us.

Standalone Deployment

For instructions on deploying BSE on a single machine without the use of any provisioning or container management, refer to Standalone BSE Deployment.


This sort of deployment should never be used for production systems, and is instead intended for evaluation, demonstration, or testing purposes only.