AI Engineer at a transportation company with 10,001+ employees
Real User
Top 20
Sep 15, 2026
Business users leverage the no-code tools within IBM watsonx Orchestrate mostly for creating dashboards and looking at metrics and the token economics of agents we create. The most relevant technical aspects when orchestrating workflows across hybrid cloud and on-premises systems using IBM watsonx Orchestrate, particularly with Azure services, are more integration with our models, what we use in Azure Foundry, and integrating those with IBM watsonx Orchestrate. It is more about logging and integration with Azure API management systems, as well as networking, that inform our approach to maintaining enterprise-grade security and governance for AI agent operations. Our developers utilize the Agent Development Kit (ADK) through Visual Studio Code to extend the capabilities of IBM watsonx Orchestrate and create the AI workflows that are needed for our users. For real-time observability of AI agent performance and workflow execution within IBM watsonx Orchestrate environment, especially when integrated with Azure monitoring tools, we have our custom dashboards based on the Azure stack, specifically logs and Power BI dashboards. My advice to others looking into using IBM watsonx Orchestrate is to start with simple agentic workflows and try to use all features available for those workflows, then move to more advanced options. I provided an overall rating of four out of ten for this product.
Senior Software Development Engineer & Ai ) Engineer at a outsourcing company with 5,001-10,000 employees
Real User
Top 20
Aug 26, 2026
I advise others looking into using IBM watsonx Orchestrate to actually try to get a free tier, which is available for around thirty days. Build a POC for your own use case, see how good IBM watsonx Orchestrate is for building agents and assistants, and then deploy it, test it, and from there you could decide if it fits your needs. The feature that I rely on the most is the multi-agent orchestration and agent builder using the ADK because in my project, I had an orchestrator agent and I built multiple agents using the ADK, automating building that using cloud code. One feature that I would see more of is reporting; I want to be able to build pins in my agent, to see out of a thousand calls, how many times one tool was called specifically, or how many times a specific journey was triggered. When it comes to accuracy and reliability, IBM watsonx Orchestrate has several strong points. One advantage of Orchestrate is that I do not have to rely solely on generative responses; I can ground agents through enterprise knowledge and APIs, separate responsibilities across specialized agents, and explicitly control which tools should be used for particular tasks. I can then evaluate routing accuracy, tool call precision, parameter accuracy, semantic correctness, and end-to-end journey completion before releasing changes. For example, if a user asks about a claim, I do not want the model generating claim information from its own knowledge; I want it to identify the intent, authenticate the member if required, call the appropriate back-end tool, retrieve the authoritative data, and formulate the response from that result. What stands out to me the most is the ability to create multiple agents and agent orchestration very seamlessly and very fast, in a matter of minutes. I would rate my overall experience with IBM watsonx Orchestrate a ten out of ten.
IBM watsonx Orchestrate is an AI-powered solution designed to automate complex workflows across businesses, integrating seamlessly with existing systems to increase operational efficiency.
IBM watsonx Orchestrate leverages cutting-edge artificial intelligence technology, enabling businesses to streamline processes by automating repetitive tasks and freeing up human resources for more strategic work. It prioritizes ease of integration, allowing rapid deployment within existing IT...
Business users leverage the no-code tools within IBM watsonx Orchestrate mostly for creating dashboards and looking at metrics and the token economics of agents we create. The most relevant technical aspects when orchestrating workflows across hybrid cloud and on-premises systems using IBM watsonx Orchestrate, particularly with Azure services, are more integration with our models, what we use in Azure Foundry, and integrating those with IBM watsonx Orchestrate. It is more about logging and integration with Azure API management systems, as well as networking, that inform our approach to maintaining enterprise-grade security and governance for AI agent operations. Our developers utilize the Agent Development Kit (ADK) through Visual Studio Code to extend the capabilities of IBM watsonx Orchestrate and create the AI workflows that are needed for our users. For real-time observability of AI agent performance and workflow execution within IBM watsonx Orchestrate environment, especially when integrated with Azure monitoring tools, we have our custom dashboards based on the Azure stack, specifically logs and Power BI dashboards. My advice to others looking into using IBM watsonx Orchestrate is to start with simple agentic workflows and try to use all features available for those workflows, then move to more advanced options. I provided an overall rating of four out of ten for this product.
I advise others looking into using IBM watsonx Orchestrate to actually try to get a free tier, which is available for around thirty days. Build a POC for your own use case, see how good IBM watsonx Orchestrate is for building agents and assistants, and then deploy it, test it, and from there you could decide if it fits your needs. The feature that I rely on the most is the multi-agent orchestration and agent builder using the ADK because in my project, I had an orchestrator agent and I built multiple agents using the ADK, automating building that using cloud code. One feature that I would see more of is reporting; I want to be able to build pins in my agent, to see out of a thousand calls, how many times one tool was called specifically, or how many times a specific journey was triggered. When it comes to accuracy and reliability, IBM watsonx Orchestrate has several strong points. One advantage of Orchestrate is that I do not have to rely solely on generative responses; I can ground agents through enterprise knowledge and APIs, separate responsibilities across specialized agents, and explicitly control which tools should be used for particular tasks. I can then evaluate routing accuracy, tool call precision, parameter accuracy, semantic correctness, and end-to-end journey completion before releasing changes. For example, if a user asks about a claim, I do not want the model generating claim information from its own knowledge; I want it to identify the intent, authenticate the member if required, call the appropriate back-end tool, retrieve the authoritative data, and formulate the response from that result. What stands out to me the most is the ability to create multiple agents and agent orchestration very seamlessly and very fast, in a matter of minutes. I would rate my overall experience with IBM watsonx Orchestrate a ten out of ten.