Deployment methods

You can use IBM SaaS Console to provision and manage a SaaS instance of Concert, manage instance level access for users and user groups, manage service IDs and more. For more information, see Provisioning a SaaS instance of Concert, Workflows, and Data Apps.

For a lighter-weight containerized solution, deploy Concert software by using OpenShift Container Platform (OCP) without IBM Cloud Pak® foundational services. When deployed, Concert uses OpenID Connect (OIDC) as the primary protocol for user authentication and management. OIDC is a widely adopted standard that enables secure, decentralized authentication between you and your identity provider. For more information, see Installing on OCP.

Amazon Elastic Kubernetes Service (EKS) provides a lightweight container deployment option on an AWS cloud. When deployed, Concert uses OpenID Connect (OIDC) as the primary protocol for user authentication and management. OIDC is a widely adopted standard that enables secure, decentralized authentication between you and your identity provider. For more information, see Installing on EKS.

Rancher Kubernetes Engine 2 (RKE2) provides a container deployment option. When deployed, Concert uses OpenID Connect (OIDC) as the primary protocol for user authentication and management. OIDC is a widely adopted standard that enables secure, decentralized authentication between you and your identity provider. For more information, see Installing on RKE2.

Deploy Concert, Concert Workflows, and Concert Data Apps software on a VM in an isolated environment. When deployed, Concert VM uses OpenID Connect (OIDC) as the primary protocol for user authentication and management. OIDC is a widely adopted standard that enables secure, decentralized authentication between you and your identity provider. For more information, see Deploying on a virtual machine (VM).