Skip to content

Installation and Deployments

Composable is very easy to deploy in the cloud, within an on-premise datacenter or at the tactical edge.

The Composable platform has the following components:

  • Composable Activation Services: The component that manages the activation and lifetime of the worker processes, including all runtime, deployment, and management activities for all Composable resources.
  • Composable Execution Engine: The back-end component that executes Composable Runs, and orchestrates all compute and data flows.
  • Composable Web Application: The centralized web application of Composable.
  • Composable Back-End Databases: The Composable Application and Membership databases used for membership store, application metadata and persistence.

In an n-tiered deployment model, the above system components can be distributed across multiple nodes. For example, Composable can be deployed with a dedicated database server, a dedicated node for the activation services and execution engine, and a dedicated web application server. In this way, isolation of the data storage, computation, business logic and web layer leads to improved stability, perfomance and scalability.


Deployment on one of the public clouds (e.g., Azure, AWS) is simple and straightforward. Composable is available in the cloud marketplaces, see, for example, Azure or AWS. Simply follow the installation wizard on the portal to spin up a virtual machine with Composable already configured. For a detailed walkthrough of the process, please see Public Cloud Deployment.

A development cloud instance is available for evaluation purposes. Please visit, and begin by creating an account.

On-Premise or Tactical Edge Installation

For development instances or tactical edge solutions, a single-tier architecture can be used, with all components deployed on a single node (e.g., server). For more complex deployments, a multi-tier approach can be configured for multi-machine and scale-out deployments.

Composable, including both first-time installations as well as platform updates, are handled via an installation wizard that guides system administrators through the required installation steps.

Typical infrastructure

Composable is used to build operational data-intensive applications, and as such, multiple instances are commonly deployed to cover the full software development and application lifecycle, from development to production. For example, an enterprise deployment can nominally have one or more Composable instances:

  • Development Instance: A dedicated Composable instance where Composable resources are developed and tested.
  • Quality Assurance Instance: A dedicated Composable instance where all stakeholders can perform quality assurance.
  • Staging Instance: A dedicated Composable instance, in an identical environment to that which is in Production, to test and finalize any configurtions needed in production.
  • Production Instance: The live Composable instance, interacting with production data feeds and services and producing operational results.

Installation and Upgrades

For on-premise installations and upgrades, a system admin can perform an installation or upgrade by simply following the Composable installation wizard or utilizing a deployment script. When upgrading an instance, an upgrade path is provided for Modules (see Modules).