Feature parity across deployments

IBM watsonx Orchestrate can be deployed as a managed software as a service (SaaS) or installed on-premises. As new features are added on each deployment's release cycle, it’s important that you understand which features are available in a deployment, so you can make informed decisions based on your business requirements.

Stay up to date with the latest features through the What's new in IBM® watsonx Orchestrate®.

The feature parity covers the following deployments:

  • Amazon Web Services (AWS): for the IBM-managed instances that are provisioned as a service on AWS.

  • IBM Cloud: for the IBM-managed instances that are provisioned as a service on IBM Cloud.

  • AWS GovCloud (US): for the IBM-managed instances that are provisioned as a service on AWS GovCloud (US).

  • IBM Software Hub (SWH): for client-managed instances that are provisioned on IBM Software Hub. It is an on-premises deployment and uses a stationary version of the continuous-delivered and continuous-integrated SaaS deployment for each of its releases into IBM Software Hub.

  • Developer Edition (DE): Developer Edition provides a local development environment on your computer to increase the development and building efficiency of agents and tools. To install and manage the Developer Edition, use the watsonx Orchestrate Agent Development Kit (ADK).

Important:

The availability of features might differ based on your IBM watsonx Orchestrate license. For more information, see Licenses and entitlements.

Feature parity by deployment

The feature parity is based on the features that you can handle through the watsonx Orchestrate's user interface, except by the mentioned for API capabilities and watsonx Orchestrate Agent Development Kit (ADK) features.

API capabilities

API capabilities might have their own support coverage for specific operations. For more information, see watsonx Orchestrate API documentation.

watsonx Orchestrate Agent Development Kit (ADK) features

Some features can be configured only through ADK CLI, as they are not available through the user interface. For more information, see Features that are configured only through the ADK CLI.

If you plan to use features from ADK in your IBM Software Hub (SWH) deployment, you must consider the supported ADK versions for each SWH version. For more information, see the SWH - watsonx Orchestrate ADK compatibility chart section in the watsonx Orchestrate Agent Development Kit documentation.

Classification of support coverage

Each deployment receives a classification of support coverage based on how the deployment supports the features' capabilities that are detailed in this topic:

  • Full support: The deployment fully supports the feature and its capabilities.

  • Partial support: The deployment partially supports the feature and its capabilities compared to other deployments. Partial support can occur when one or more of the following cases apply to the deployment:

    • The deployment has the feature, but the feature implementation in the product differs from other deployments.

    • The deployment does not support all the features' capabilities that are listed in the table.

  • No support: The deployment does not support the feature and its capabilities compared to other deployments.

Refer to the following table for the feature classification on each deployment:

Table 1. Support coverage for features on each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH

Developer Edition

Discovering the catalog

Full support

Full support

Full support

Partial support¹

Partial support

Building and customizing agents

Partial support

Full support

Partial support

Partial support¹

Partial support

Building tools

Full support

Full support

Full support

Partial support¹

Full support

Building agentic workflows

Full support

Full support

Full support

Partial support¹

Full support

Orchestrating agents

Partial support

Full support

Partial support

Partial support¹

Partial support

Adding knowledge to agents

Full support

Full support

Full support

Full support

Full support

Configuring voice for an agent

Full support

Full support

Full support

Partial support¹

Full support

Connecting to channels

Full support

Full support

Full support

Partial support¹

No support

Managing app connections and credentials

Full support

Full support

Full support

Partial support

Partial support

Testing the agent

Full support

Full support

Full support

Partial support¹

Full support

Deploying the agent

Full support

Full support

Partial support

Partial support¹

Partial support

Orchestrate Chat

Full support

Full support

Partial support

Partial support¹

Partial support

Agentic Control Plane (Private preview)

Full support

Full support

No support

No support

No support

Working with controls

Full support

Full support

Full support

No support

No support

Agent analytics and monitoring

Full support

Full support

Full support

No support

No support

AgentOps (Public preview)

Full support

No support

No support

No support

No support

Monitoring agents (previous experience)

Full support

Full support

Full support

Partial support¹

Full support

Securing your instance

Full support

Full support

No support

Full support

No support

Deployment architecture

Full support

Full support

No support

Full support

No support

Platform language

Full support

Full support

Full support

Full support

Full support

¹ Partial support availability: Considering features and capabilities, IBM watsonx Orchestrate on IBM Software Hub is usually one release behind the current Software-as-a-Service (SaaS) deployment of IBM watsonx Orchestrate on AWS or on IBM Cloud. Back to reference.

Parity by feature capabilities

Features can have their own capabilities, which might have limitations on what deployments support them. In the following sections, you can view the capabilities of each feature and if the deployments support these capabilities.

In the tables, you can find the following indications:

  • The black tick ✓ indicates that the deployment supports the capability.

  • The black tick with a warning ✓⚠️ indicates that the deployment supports the capability, but the capability might have specific implementations that differ from other deployments.

  • The black cross ✕ indicates that the deployment does not support the capability.

Discovering the catalog

Table 2. Discovering the catalog support for each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Support for prebuilt domain agents

Support for prebuilt tools

Adding External partner agents as collaborator agents from the catalog

Adding Partner native agents as collaborator agents from the catalog

Visualize artifact hierarchy in prebuilt agents

Adding a tool from a catalog

Exploring remote MCP servers from catalog

Add OpenAPI tools from catalog

Note:

A few prebuilt agents are not supported in on-premises deployments. To know more about the availability of prebuilt agents for each deployment, see Prebuilt agent feature parity across deployments.

Learn more:Discovering the catalog

Building and customizing agents

Table 3. Building agents support for each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Creating agents

Organize agents with workspaces

Connecting to IBM foundation models

Choosing style for your agent

Configuring voice modality (preview)

Adding guidelines to agent

Customizing the welcome message and starter prompts

Agent Assist integration (Preview)

Adding a tool from a local instance

Creating an agent for document processing

Managing tools from an agent

Learn more: Building agents

Building tools

Table 4. Building tools support for each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Customizing the schema for tools

Import external tools from OpenAPI

Import tools from Model Context Protocol servers

Learn more: Building tools

Building agentic workflows

Table 5. Building agentic workflows for each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Creating agentic workflows

Logic block

Document classifiers

Document extractors

Text extractors

Adding user activities

Adding generative prompts

Inspecting agentic workflow

✓⚠️³

Add agent nodes to agentic workflows

Running agentic workflows with MCP (Public Preview)

✓⚠️

✓⚠️

✓⚠️

Multi-user activities

Configure system callbacks

✓⚠️ ✓⚠️ ✓⚠️

Configure parallel execution for For each controls

Consuming intermediate context updates in agentic workflows

Masking sensitive information in agentic workflows

View and edit pro-code workflows

Add decision tables to agentic workflows

Adding parallel controls to agentic workflows

Arranging a workflow layout automatically

Configuring multiple languages for user interactions

Configuring agent summarization in agentic workflows

Configuring external system notifications in agentic workflows

³ IBM Software Hub 5.3.1: For IBM watsonx Orchestrate on IBM Software Hub, the Inspecting agentic workflows feature is available in Preview only. Back to reference.

ᵃ Support through ADK: Support is available only through ADK.

Learn more: Building agentic workflows

Orchestrating agents

Table 6. Orchestrating agents support for each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Adding AI assistant builder assistants as collaborator agents

✓⚠️

✓⚠️

Adding assistants from IBM watsonx Assistant product as collaborator agents

Adding agents from third-party platforms

✓⚠️

✓⚠️

Adding Partner A2A agents as collaborator agents from the catalog

Purchasing partner agents from the catalog

Importing LangGraph agents

⁶ Unavailability: The Assistant builder experience is not available in the Paris (eu-fr2) region on IBM Cloud and London (eu-west-2) region on AWS. Back to reference.

⁷ A2A support: Adding external agents that use the Agent to Agent (A2A) protocol as collaborators is not supported in SWH 5.2.2 and SWH 5.3.0. Back to reference.

Note:

Business Partners can create External partner agents or Partner native agents by using the Developer Edition. However, users cannot import them from the catalog, as the Developer Edition does not include a catalog.

Learn more: Orchestrating agents

Adding knowledge to agents

Table 7. Adding knowledge to agents support for each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Direct file upload

Connecting a Milvus content repository

Connecting to an Elasticsearch content repository

Connecting to a custom service repository

Connecting to an Astra DB content repository

Learn more: Adding knowledge to agents

Configuring voice for an agent

Table 8. Configuring voice for an agent support for each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Configuring voice settings for agents

Connecting to Phone with Genesys Audio Connector (Preview)

Connecting to Phone with SIP trunk (Preview)

Enabling real-time voice agents (Private preview)

Learn more: Configuring voice

Connecting agents to channels

Table 9. Connecting agents to channels support for each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Connecting to Microsoft Teams

Connecting to WhatsApp with Twilio

Connecting to SMS with Twilio

Connecting to Facebook Messenger

Connecting to Genesys Bot connector

Connecting to Slack

Learn more: Connecting to channels

Managing app connections and credentials

Table 10. Managing app connections and credentials support for each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Creating and managing connections

Managing app credentials

Binding and deploying connections

Connecting apps for prebuilt agents

Authenticating users with single sign-on

Managing access using the Security Control Center

View connection status indicators

Adding an agent-to-agent connection through Security Control Center

Learn more: Managing app connections and credentials

Testing the agent

Table 11. Testing the agent support for each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Debugging your agent

Evaluate with simulated users

Recording and managing test cases

Running evaluations

Understanding evaluation metrics

Learn more: Testing the agent

Deploying the agent

Table 12. Deploying the agent support for each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Deploying agents to live environment

Publishing agents to catalog

Using an agent in embedded chat

Embedding the agent with web applications

Enabling voice capabilities in the embedded agent

Securing the embedded chat

Learn more: Deploying the agent

Orchestrate Chat

Table 13. Orchestrate Chat support for each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Uploading documents during conversation

Connecting to a live agent

✓⚠️ ²

✓⚠️ ²

Understanding agent memory (Preview)

Scheduling tasks and agentic workflows

²  Support through assistants: Support is available only when the live agent is enabled through watsonx Assistant assistants. Back to reference.

Learn more: Using Orchestrate Chat

Agentic Control Plane (Private preview)

Note: This feature is available on IBM Cloud and only with IBM watsonx Orchestrate Agentic Essentials and IBM watsonx Orchestrate Agentic Standard offerings on AWS.
Table 14. Agentic Control Plane in each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Managing operational alerts

Reviewing agent fleet health

Learn more:  Agentic Control Plane overview

Working with controls

Table 15. Working with controls in each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Managing controls

Limiting MCP tool call rates

Learn more:  Working with controls

Agent analytics and monitoring

Note: This feature is available in IBM Cloud and only with IBM watsonx Orchestrate Agentic Essentials and IBM watsonx Orchestrate Agentic Standard offerings on AWS.
Table 16. Agent analytics and monitoring support for each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Agent level metrics

Learn more: Agent analytics and monitoring

AgentOps (Public preview)

Table 17. AgentOps support in each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Evaluate and optimize agents with AgentOps

Learn more:AgentOps

Monitoring agents (previous experience)

Table 18. Monitoring agent support for each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Monitoring and improving agent performance

✓⚠️

✓⚠️

✓⚠️

✓⚠️

PII masking

✓⚠️

✓⚠️

✓⚠️

✓⚠️

⁴ AWS: Monitoring agent analytics feature is deprecated in AWS and scheduled for removal in future release.  Back to reference.

⁵ IBM Software Hub: Monitoring agent analytics is an optional feature in 5.4.0, 5.3.1 Patch 2 and 5.3.1 Patch 5. Back to reference.

Learn more: Managing agent analytics settings

Securing your instance

Table 19. Securing the instances in each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Auditing logs

Creating private paths using AWS PrivateLink

Learn more: Securing your instance

Deployment architecture

Table 20. Deployment architecture support for each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Multi-region active architecture

Learn more: Configuring instances for multi-region active deployment

Platform language

Table 21. Platform language support on each deployment

Feature

AWS

IBM Cloud

AWS GovCloud (US)

SWH 5.4.0

SWH 5.3.1 Patch 5

SWH 5.3.1 Patch 2

SWH 5.3.1

SWH 5.3.0

SWH 5.2.2

SWH 5.2.1

DE

Changing platform language

✓⚠️

⁸ Language support: Platform language support for Developer Edition depends on the deployment that your installation targets and the deployment supported capabilities. Back to reference.

Learn more: Platform language configuration

Features that are configured only through the ADK CLI

Some features are configurable only through the Agent Development Kit (ADK). These features are supported across all IBM watsonx Orchestrate deployment options, including:

  • AWS

  • IBM Cloud

  • AWS GovCloud (US)

  • On-premises

  • Developer Edition

Important:
  • The following features are available in all deployment environments but must be configured by using the ADK. No UI support is provided for these features.

  • A few features exist exclusively within the ADK and are not available in any deployment environment. ADK-exclusive features are intended for advanced development and configuration use cases.

  • Documentation for ADK-exclusive features is available only in the ADK Documentation.

The following features are supported across all deployment options but require ADK for configuration: