IBM watsonx Orchestrate Reviews

My main use case for IBM watsonx Orchestrate is to coordinate and automate multi-step business workflows across different enterprise applications. We mainly use it to handle processes like employee onboarding and procurement requests where it can connect systems, trigger actions, and route exceptions without relying on separate automations for every step.

For example, in employee onboarding, we use IBM watsonx Orchestrate to coordinate tasks such as creating IT access requests, updating HR records, and notifying the relevant teams based on the employee's role. It helps reduce the manual coordination between HR and IT, while exceptions can still be routed to a person for review.

Day-to-day, we mainly use IBM watsonx Orchestrate for coordinating repetitive workflows that involve multiple systems and teams rather than simple task automation. It gives us better visibility into the overall process and reduces the amount of manual follow-up, while we still keep human approval for decisions that need judgment.

IBM watsonx Orchestrate has impacted my organization positively by reducing manual coordination and follow-ups in several workflows, particularly where multiple teams and systems are involved. We have also seen faster turnaround times and more consistent execution because routine steps are handled automatically while employees can focus more on exceptions and higher-value work.

For one of our onboarding workflows, the overall turnaround time came down by roughly 30 to 40%, primarily by removing manual handoffs and follow-ups. We also saw fewer data entry errors and saved several hours of manual effort each week, although the exact savings vary by process volume.

The best features IBM watsonx Orchestrate offers are its ability to orchestrate workflows across different enterprise systems, integrate with existing tools, and handle multi-step tasks from a single workflow. I also value the way it can involve human approval when needed, so automation does not have to mean completely removing people from the process.

I can tell you more about how the integration with existing tools works for us. We have mainly integrated it with systems such as ServiceNow, SAP, Microsoft Teams, and internal business applications through APIs and connectors, where the standard integrations were fairly straightforward, while the custom integrations needed more development and testing, especially around authentication and handling exceptions.

One thing that stands out about the features is the combination of orchestration, integrations, and AI-driven decision support, which makes IBM watsonx Orchestrate more useful than a traditional task-based automation. I would like to see even more flexibility around custom integrations and more detailed monitoring and troubleshooting capabilities for complex workflows.

I think IBM watsonx Orchestrate can be improved by implementing simpler configuration for complex workflows and providing more flexibility when building custom integrations with internal applications. The monitoring and debugging experience could also be more detailed, especially for understanding exactly where a multi-step workflow failed and why.

Regarding needed improvements, the overall user experience is fairly intuitive, but some advanced configuration areas have a steep learning curve for new users. I would also like to see more detailed, real-world examples in the documentation, particularly for complex enterprise integrations, troubleshooting, and production deployment patterns.

Better production monitoring and more detailed troubleshooting would make a noticeable difference. More ready-to-use enterprise integration patterns and clearer guidance for scaling complex workflows would also help teams adopt faster.

I have been using IBM watsonx Orchestrate for a little over a year.

Overall, we have found IBM watsonx Orchestrate to be stable for our production workflows over the past year. We have occasional integration or configuration-related issues, but they were generally manageable and did not undermine our overall confidence in using it for enterprise automation.

We have found IBM watsonx Orchestrate reasonably scalable, as we have expanded from our individual workflows to multiple business processes. It handles increased workflow volume well, although scaling complex integration still requires careful capacity planning, monitoring, and testing.

Overall, our experience with IBM support has been positive, particularly for technical issues and integration-related questions. Response times can vary depending on the complexity and priority of the issue, but their support team has generally been helpful in getting production issues resolved.

I would rate the customer support for IBM watsonx Orchestrate 8 out of 10. The technical assistance has generally been helpful and responsive, although response times can vary depending on the complexity and priority of the issue.

Before using IBM watsonx Orchestrate, we primarily relied on traditional RPA tools and custom scripts for individual task automation. We moved to IBM watsonx Orchestrate because we needed more end-to-end workflow coordination across multiple systems rather than maintaining separate automations for each individual task.

The setup process required effort around configuration, security, and integration.

We have seen a return on investment with IBM watsonx Orchestrate, mainly through reduced manual effort rather than headcount reduction. For some workflows, we have saved several hours of manual work each week and reduced the turnaround times by roughly 30 to 40%, which has made the investment easier to justify.

My experience with pricing, setup cost, and licensing for IBM watsonx Orchestrate reflects that the pricing felt reasonable for an enterprise platform, but the overall cost depends quite a bit on usage, integration, and the scale of deployment. Initial setup required some effort around configuration, security, and integration with the licensing, and it took time for us to understand and plan accurately.

Before choosing IBM watsonx Orchestrate, we evaluated a few alternatives, mainly Microsoft Power Automate and some initially developed orchestration approaches. We compared them around integration capabilities, AI agent functionality, governance, ease of adoption, and how they can fit into our existing enterprise environment.

Regarding IBM watsonx Orchestrate's AI capabilities, I think the governance and security are suitable for enterprise use, particularly around access controls, authentication, and keeping human approvals in sensitive workflows. We still treat governance as an ongoing responsibility, especially for our AI-driven decisions, so we apply appropriate permissions, monitoring, and review controls before putting workflows into production.

The accuracy and reliability of output are generally reasonable for structured, well-defined workflows, especially when the underlying data and instructions are clear. For more complex or ambiguous scenarios, we have occasionally needed human validation, so we do not treat AI output as fully autonomous without appropriate checks.

IBM watsonx Orchestrate is deployed in our organization in a public cloud environment, integrated with our existing enterprise applications and APIs. We chose this approach because it simplifies scalability and integration, while access controls and security policies are managed according to our organization's requirements.

We primarily use IBM Cloud for our IBM watsonx Orchestrate deployment, as it fits well with our existing IBM ecosystem and makes it easier for us to manage integrations, access controls, and enterprise security requirements.

Business users have leveraged the no-code tools within IBM watsonx Orchestrate to create custom AI agents for their specific workflows, mainly using the no-code capabilities to configure agents for well-defined workflows without depending on developers for every change. For example, they can set up an agent to collect information, trigger actions across connected systems, and route exceptions to the right team, while IT handles more complex integrations and governance.

The technical aspects most relevant when orchestrating workflows across hybrid cloud and on-premises systems using IBM watsonx Orchestrate, particularly in conjunction with services such as Amazon S3 or AWS Lambda, include secure connectivity, authentication, API management, and reliable data movement between cloud and on-premises systems. When integrating services such as Amazon S3 or AWS Lambda, we pay particular attention to permissions, network connectivity, error handling, and monitoring so failures can be identified and recovered cleanly.

The mechanisms within IBM watsonx Orchestrate that inform our approach to maintaining enterprise-grade security and governance for AI agent operations involve role-based access controls, authentication control to data access, and human approvals for sensitive agent actions. We also apply logging and monitoring so agent activity can be reviewed, with governance policies helping ensure agents only perform the actions they are authorized to perform.

Our developers have utilized the Agent Development Kit (ADK) to extend the capabilities of IBM watsonx Orchestrate mainly when the built-in capabilities or connectors were not sufficient for a specific enterprise requirement. One example was creating custom integrations for internal REST APIs and ServiceNow workflows, where the ADK gave developers more control over authentication, business logic, and error handling.

We employ various methods for real-time observability of AI agent performance and workflow execution within IBM watsonx Orchestrate environment, especially when integrated with monitoring tools such as IBM Cloud Monitoring or AWS CloudWatch. We monitor workflow execution through execution logs, agent activity failures, response times, and integration errors, with alerts for critical failures, and for cloud services, we correlate these events with platform monitoring to troubleshoot issues across the end-to-end workflow.

I would rate my overall experience with IBM watsonx Orchestrate an 8 out of 10.

My use case involves developing workflows for banks using IBM watsonx Orchestrate, integrating it with AI models and the LLM. The most relevant aspect when I orchestrate workflows across hybrid cloud or on-premises systems is that it supports both, and we work with banks, so it is usually on-premises. It is important to me for sure, but we do not work in the cloud mainly because we usually work in the banking field, so they typically ask for an on-premises solution.

From my partner experience with IBM, I think the biggest advantage of IBM watsonx Orchestrate is that it is part of the IBM family for AI, and it can enable you to build workflows from the IBM registry or using open source. It supports using open source as well.

I would say it helps to leverage no-code tools within IBM watsonx Orchestrate to create custom AI agents, and it is a low-code platform that helps me to drag and drop and create a workflow easily.

IBM watsonx Orchestrate can be orchestrated in conjunction with AWS services such as Amazon S3 and AWS Lambda, and I work with that as it supports multiple hosters including Amazon, IBM itself, and Microsoft.

Regarding the maintenance of enterprise-grade security and governance for AI agent operations, IBM watsonx Orchestrate is secure. For governance in AI, I use watsonx.governance, and for security, it is secured by IBM. I do not see any problems or flaws on this side.

I am working with the aspect called ADK, Agent Development Kit, as it is a tool internally used to develop agents using IBM watsonx Orchestrate. It is helpful to me because it is a drag-and-drop tool that allows me to create an agent, which is a workflow connecting multiple applications or connecting with AI and multiple applications, making it simple to use to drag and drop and connect all my applications to create the flow to be an agent.

In terms of real-time observability of AI agent performance, especially when integrating with AWS CloudWatch services, there is a dashboard internally to check and observe the performance.

I do see areas for improvement with IBM watsonx Orchestrate, particularly in price, as it is too high compared to competitors, which makes customers think twice.

I see potential technical improvements in the future, as they could add more features or perhaps more integrations, but I think it is working fine right now, and I do not see it will change because IBM counts on multiple applications integrated together. There is room for performance improvement in governance or security, but it will not be on IBM watsonx Orchestrate as it is not its job; it will be on another solution and integrated with it.

I started working with the tool a year and a half ago.

I think the stability of the product is good, as it is quite stable and does not usually have glitches, latency problems, or bugs.

IBM sells it as scalable, and I find it to be scalable.

Regarding technical support from IBM, my experience is that it is poor. IBM support usually does not take me straight to the solution; it tends to ask many questions before providing a final solution, which can take many days compared to any others.

For IBM watsonx Orchestrate, I find it quite easy and straightforward.

I basically work with IBM as a partner.

Even though I say it is pricey, I see a return on investment and value for money here. However, you should know that it is working with AI, and ninety-five percent of AI projects fail to get ROI because of the cost. It is an investment, and it is not something that can be easy to achieve because whether it is Watson or not Watson, it will cost.

It usually involves the cost of development, cost of infrastructure, and the return in this case can reduce revenue, reduce time, and reduce cost. However, it is not something you can count because it depends on the use case. Regarding time reduction, it is not something you can count because it depends on the use case.

I have been working with something similar to IBM watsonx Orchestrate, as I evaluated some other products such as Red Hat AI. The difference that I see is that Red Hat relies mainly on the open-source community, while IBM has its own open-source community internally and its own code to create the platform. Red Hat is less expensive.

As partners with specific cloud providers such as AWS, we are restricted to what IBM offers, with AWS being one of them, along with Google. Summarizing all that we have discussed about IBM watsonx Orchestrate, I would give it a rating of seven out of ten.

I work on AI agents that we build and deploy on IBM platform. I was mostly working on deploying agents on IBM watsonx Orchestrate by creating different agents and orchestrating them to one main agent, then deploying it on IBM watsonx Orchestrate. The primary work involved testing the agent on IBM platform. The solution functions as an AI chatbot with a chat interface where the deployed agents can answer questions. Users can ask questions to each individual agent or ask the main orchestrator agent to route the questions through different sub-agents and provide answers.

I would rate the improvements to the organization between 60 to 70. IBM watsonx Orchestrate saves a considerable amount of time by automating processes. For example, if I need to search through many products for a company, having an automated IBM watsonx Orchestrate solution would allow me to search whatever I want using the chat interface. This would save significant time for inventory checks and other product-related queries. As a business owner, I believe I could save a substantial amount of time by implementing this solution.

The best aspect of IBM watsonx Orchestrate is how accessible and easy it is for any consumer to use. I have worked with different tools including Microsoft and other IBM products. IBM watsonx Orchestrate is much easier for anyone, whether a developer or a consumer, to understand and use without prior knowledge compared to other platforms.

The no-code functionality works well for developing simple agents. However, for building a complete product with automation, orchestration, and AI agents, the no-code approach has limitations. To develop a full-fledged project and product, the code-based approach where you code, deploy, connect, and automate using IBM watsonx Orchestrate produces a much better product than the no-code option.

I have integrated with Jira and other products. While integration is possible, it is not particularly easy. The integration of solutions including Jira, ticketing systems, mail systems, and SMTP could be improved and made much easier.

Since IBM watsonx Orchestrate is an agentic AI platform for orchestrating and building AI agents and automating workflows for different products, real-world implementation would benefit from easier integration with different solutions. Integration is currently possible, but the process could be simplified so connections across different solutions are more straightforward.

I have been working for a year with IBM watsonx Orchestrate and related tools.

I would rate the stability at seven.

IBM watsonx Orchestrate is a scalable solution with room for improvement. We have built products for different clients using IBM watsonx Orchestrate that they continue to use, and I believe it is scalable. However, the chat interface functionality, how it currently operates, and the response time for the AI chat could be improved. The response time in particular could be enhanced.

I would rate the technical support from IBM around seven. Some of the support I needed was not provided in time, though it was eventually provided. I had to follow up multiple times with customer support. The support was helpful, and since we were partners, we could schedule meetings with IBM to resolve issues. However, these resolutions took considerable time, so I would rate the customer service between six to seven.

I have worked with different tools while building AI agents, including Microsoft and other platforms. I felt IBM watsonx Orchestrate is at the forefront in providing easy access for developers to create agents. Since everything is moving towards agentic AI solutions, IBM has been working in this direction along with other companies. IBM watsonx Orchestrate makes it easier for people to build agents on their own when they have access to it and their company partners with IBM for development.

To my knowledge, approximately 20 people are familiarized with IBM watsonx Orchestrate, and many people have completed certifications on IBM watsonx Orchestrate and other IBM watsonx tools. The hands-on experience, as far as I am aware, extends to about 20 to 30 people. In India, where I worked, approximately 20 to 30 people in my office were familiarized with and know how to work with the product.

I would recommend IBM watsonx Orchestrate to other users. As a business owner, I believe it would save considerable time compared to manual processes. It is easy to use and user-friendly, allowing anyone without prior knowledge to understand and use it quickly. The reason I would hesitate to recommend it is that the integration with different solutions is complicated. On a scale from 1 to 10, I would rate the solution itself at eight, though it could be improved in different areas.

The main use case for IBM watsonx Orchestrate is to create AI agents, helping students build AI agentic workflows for various domain tasks, automating their tasks, and streamlining business workflows, while guiding them through the design, development, and integration of these AI agents into practical real-world solutions across multiple domains.

One project that stands out involved helping a group of students design an AI-powered customer support agent using IBM watsonx Orchestrate, which assists in understanding customer questions, retrieving relevant information from the knowledge base, providing appropriate responses, and escalating complex issues while seeing them transition from understanding basic concepts to building functional prototypes.

The biggest challenge my students faced when building the customer support agent was getting the agents to understand the user's requests and connecting the right tools to execute tasks accurately, especially since they were new to AI agents. IBM watsonx Orchestrate helped simplify agent development through a visual interface and built-in tools.

I use IBM watsonx Orchestrate for various purposes beyond just one use case, including helping students understand how to apply agentic AI to real-world business challenges, from idea generation to integration and testing of solutions, while also demonstrating how multiple AI agents and tools can work together, and noting areas for improvement in documentation and onboarding for beginners.

My experience with the Agent Development Kit (ADK) involves helping developers extend IBM watsonx Orchestrate's capabilities by creating custom tools and integrating external APIs, such as connecting a customer support agent to a knowledge base for information retrieval.

IBM watsonx Orchestrate positively impacts my organization by enhancing collaboration with my consulting company, and aiding in training learners to build practical AI solutions while reducing technical barriers for beginners and making coaching sessions more hands-on.

We have seen significant outcomes from our programs, particularly in how students from diverse backgrounds who once had no coding experience were able to complete projects within the ten-week program, leading to expansion beyond the United States due to increased excitement and participation.

The best features of IBM watsonx Orchestrate include its ability to build and manage AI agents with minimal coding, offering no-code agent builders and templates that simplify the process for beginners, along with a visual workflow builder that facilitates the design of agentic workflows and supports multi-agent collaborations.

My students primarily rely on the visual workflow builder and low-code agent development capabilities because they enable them to visually design workflows, configure tools, and test agent interactions without writing extensive code, which is crucial for understanding agentic AI logic and building working prototypes.

IBM watsonx Orchestrate provides strong governance and security capabilities for enterprise AI apps, featuring role-based access controls, data protection, and integration with enterprise security policies that help manage how AI agents access information and execute tasks.

The no-code capabilities in IBM watsonx Orchestrate allow users with limited programming experience to build AI agents tailored to their specific needs, such as designing customer support agents and creating workflows to handle repetitive tasks and respond to user requests.

IBM watsonx Orchestrate can be improved in three key areas: documentation with more practical examples, better debugging tools to identify issues, and a more beginner-friendly onboarding experience to enhance user interaction.

I have been using IBM watsonx Orchestrate for a year and a half as an AI coach and consultant with IBM's SkillsBuild in partnership with IBM, where we organize cohorts for students all over the country and help them utilize some of the IBM toolkits.

IBM watsonx Orchestrate is stable.

IBM watsonx Orchestrate offers good scalability, supporting multiple agent workflows and integrations without significant performance issues, which is beneficial for concurrent projects across various student teams.

I have seen a positive return on investment through time savings, faster development, and reduced technical complexities, particularly as I coach an increasing number of teams and observe students quickly transitioning from learning AI concepts to developing functional prototypes.

Because my use of IBM watsonx Orchestrate is part of a collaboration with IBM, I have not incurred any costs for pricing, setup, or licensing.

I would rate IBM watsonx Orchestrate a seven out of ten.

I choose a seven because it is a powerful platform for building and deploying AI agents, offering low-code capabilities and strong support for agentic workflows, but it still requires improvements in documentation, debugging, and onboarding.

Although IBM watsonx Orchestrate generally produces reliable results, I would rate its accuracy a seven, noting that the output quality can vary depending on the AI model and configurations, as agents may misinterpret requests or provide incomplete responses.

We primarily utilize IBM watsonx Orchestrate through IBM's public cloud environment, enabling students to access the platform via cloud-based accounts to build, test, and deploy AI agents without managing underlying infrastructures.

When orchestrating workflows across hybrid cloud and on-premises systems, the key technical aspects are secure connectivity, API integration, and authentication, as well as managing data flow between environments, such as using Amazon S3 for storage and AWS Lambda for executing serverless functions.

My approach to maintaining enterprise-grade security and governance for AI agent operations focuses on access control, data security, monitoring, and human oversight, utilizing mechanisms like role-based access control to govern how agents operate and restrict their access to authorized data and actions.

I ensure real-time observability of AI agent performance by tracking agent execution, monitoring tool calls, and evaluating response quality, particularly by reviewing logs and workflow behavior to understand challenges faced by the agents.

I would advise others looking into using IBM watsonx Orchestrate that it is a fantastic tool to start with, offering a great skill-building experience as it helps users understand agentic workflows, prototype ideas, and create both basic and complex AI solutions.

I have worked on IBM watsonx Orchestrate in multiple projects, and I specifically worked on an AI-driven injection molding assistant using IBM watsonx Orchestrate. I used Orchestrate to coordinate multiple AI agents and tools that analyzed plastic part designs for manufacturability issues such as wall thickness, draft angles, undercuts, and sink marks. The system then generated recommendations, a mold rating and a score, and a supplier-ready report. I also integrated APIs and RAG so the agents could ground their responses in injection molding guidelines.

My main use for IBM watsonx Orchestrate is building assistants and agents and also using speech-to-text and text-to-speech services, and also building Node apps.

There are many features that I consider the best features that IBM watsonx Orchestrate offers. One of them is multi-agent orchestration; I can have a supervisor or orchestrator coordinate specialized agents and decide which agent or tool should handle a request. Another feature is the agent builder, which allows me to build agents using no-code or low-code, natural language instructions, templates, reusable tools, or pro-code using Python and the ADK. I personally love using the ADK because I can automate building agents using cloud code or IBM. I also have tool and API integrations, so the agents can invoke REST APIs, OpenAPI defined tools, Python tools, MCP servers, databases, and enterprise applications. This allows agents to actually perform actions rather than just answer questions. I can also bring my own agents; I can import existing LangGraph agents and manage external A2A agents instead of rebuilding everything in IBM. I also have agentic workflows; I can combine LLM reasoning with deterministic workflow logic, such as branching, conditions, loops, parallel execution, and long-running processes. I can also integrate human-in-the-loop workflows that can stop for approval or validation, preserve the context, and then resume automatically, which is extremely useful for regulated enterprise workflows.

I can also work with memory and context; Orchestrate supports agents' memory, so agents can retain useful context across interactions rather than treating every request independently. IBM added expanding memory management capabilities in 2026. I also have evaluation and testing, so I can create test cases, evaluate agent behavior, perform regression testing, inspect conversations, and detect whether changes have degraded the agent. I also have observability and governance; IBM's newer agentic control plane lets organizations monitor agents, manage security access, see performance analytics, and govern agents centrally, which is a major differentiator for large companies. I can also use multiple models; I am not limited to one IBM model. AI Gateway supports different model providers and routing policies, so the model can be selected based on the use case.

IBM watsonx Orchestrate helped my team move from building every AI workflow from scratch to using reusable agents, tools, and integrations; this meant APIs, authentication logic, knowledge sources, and business actions could be packaged once and then reused across multiple use cases instead of being built for each assistant. It also improved time to market, allowing me to prototype agentic workflows much faster, connect them to enterprise systems, and validate the business flow before investing heavily in custom development. Another major benefit was better separation of responsibilities; instead of one large assistant trying to handle everything, I could create specialized agents for specific tasks and let Orchestrate coordinate them. This made the solution easier to maintain, test, and scale. For enterprise teams, it also helped with consistency and governance, providing a more standardized way to expose tools, manage agent behaviors, test workflows, and control how AI interacted with back-end systems.

The best things to improve about IBM watsonx Orchestrate are better debugging across multiple agent workflows. When several agents and tools collaborate, troubleshooting can get complicated. I would want an even clearer end-to-end trace showing exactly why agent A delegated to agent B, why a tool was selected, what context was passed, where latency occurred, and where the failure originated. IBM already has strong execution tracing, but this can always be more developer-friendly. I also want stronger automated evaluation and regression testing; every time I modify a prompt, model, tool description, or agent, I want to know whether I broke something else. IBM introduced AgentOps and simulated user evaluations, but I would expand that further with easier CI/CD style regression suites and business-specific KPIs such as task completion, routing accuracy, hallucination rate, and tool call success. I also want more predictable agent routing; in multi-agent systems, two agents may have overlapping capabilities, so the orchestrator sometimes must infer which one is appropriate based on descriptions. IBM itself provides guidance on writing agent descriptions to improve routing accuracy, but I would want stronger routing controls, confidence scores, deterministic fallback rules, and easier visualization of why a particular agent was selected.

I have been working in my current field for about five years now, and I have been working with IBM watsonx Orchestrate ever since it started.

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.

My main use case for IBM watsonx Orchestrate is web search integration for specific company and public websites. In scenarios where my developers have utilized the Agent Development Kit, ADK, to extend the capabilities of IBM watsonx Orchestrate, we have implemented this integration.

Regarding IBM watsonx Orchestrate's AI capabilities, governance and security are extremely valuable and top of the industry.

The accuracy and reliability of output are extremely good, combined with the compliance and guardrail framework.

Business users have leveraged the no-code tools within IBM watsonx Orchestrate to create custom AI agents for their specific workflows by building their agents autonomously without help after we provide them with introduction and education.

The technical aspects most relevant when orchestrating workflows across hybrid cloud and on-premises systems using IBM watsonx Orchestrate, particularly in conjunction with services like Amazon S3 or AWS Lambda, include the seamless integration of all these different tools.

The governance tools from IBM inform my approach to maintaining enterprise-grade security and governance for AI agent operations, and I have the monitoring and integration features with this.

For real-time observability of AI agent performance and workflow execution within IBM watsonx Orchestrate, I employ standard metrics such as accuracy, bias, and latency.

IBM watsonx Orchestrate is stable.

IBM watsonx Orchestrate's scalability scales fully automatically and can scale up also with different clouds.

The customer support for IBM watsonx Orchestrate is very quick and extremely good.

I would rate the customer support on a scale of 1 to 10 as a 10.

Previously, we used multiple open-source solutions and Microsoft Azure, but we have not switched fully and are maintaining all options for our customers.

I have seen a return on investment, though this information is under NDA and cannot be enclosed.

My experience with pricing, setup cost, and licensing has been fair pricing and quick deployment.

Before choosing IBM watsonx Orchestrate, I evaluated other options such as open-source systems and Microsoft.

I would rate IBM watsonx Orchestrate overall a 9. I chose that number because it is an extremely efficient system for our use case and especially for our clients. My advice to others looking into using IBM watsonx Orchestrate is to attend one of their meetups or events to see and experience the system. My overall review rating for IBM watsonx Orchestrate is 9.

I had an idea and conducted research from scratch on the features of the application I wanted to create and how the workflow would look. I started with IBM watsonx Orchestrate and used the idea feature to brainstorm. IBM watsonx Orchestrate stores the workflow inside the developing tool, so my workflow was being saved and documented.

Once I was ready to start programming, I worked off the previously completed idea workflow or idea page, step-by-step. Step one involved implementing IBM watsonx Orchestrate, which meant going through the prompts. It reads the prompt and then collects certain information from the prompt and organizes the information into JSON, which I would then use on the next step of the application.

The favorite feature that stood out for me was the ideation page. The page does not only store your ideas or give it a written form, but it is also a part of the project. Whenever I had an issue, I wanted to document the issues and the solution that was used to solve those issues.

Every single problem was documented on that document entirely. It was a whole document, basically a whole bible, from the genesis of the idea, then the issues that we came across, the solutions we used to solve them, and all the way to the completion. I find that this is not something I have seen anywhere before when it comes to developing tools. That was really nice to have and that stood out for me.

I have been using it for a month overall because I only used it for a hackathon. The hackathon was a month.

What stood out regarding stability is that sometimes it took so long for a response. I am not sure, but it did respond at the end of the day. It just took maybe it was hanging or something, but I did not get any crashes.

It is definitely scalable.

Other than Visual Studio, Visual Studio does not have, I guess it does have some AI assistance, but not something entirely focused in the way that IBM watsonx Orchestrate is.

The initial setup for me was fairly easy because I am already in the field of IT and programming. However, I would say it could be easier for other individuals, but for me, it was easy.

Personally, I would say it would be nicer if it could be cheaper because I was working on a hackathon project and I kept running out of credits. Although the hackathon told us we could use different emails to finish the project, I did subscribe at some point, but I feel it would be nicer if it could be cheaper.

It did not require any maintenance from my end.

Considering my use case of collecting the key information, how that information is being used or where it is going would also be concerning. For my use case, it is not really much of a security issue because it is not personal information I am collecting.

Because of how much I really appreciated being able to keep track of my workflow and everything, I would rate it between an eight or a nine. I would say nine.

My main use case for IBM watsonx Orchestrate is to create an intelligent layer for AI agent orchestrations. When we need to route a user question to one of the AI agents the team created, we use IBM watsonx Orchestrate.

The best features IBM watsonx Orchestrate offers are visibility for those agents, being able to see how much each was used and logs for each. We use those insights for loop engineering, meaning we improve our AI capabilities based on those logs. IBM watsonx Orchestrate has positively impacted our organization by helping us with governance and security layers for AI agents.

Better integration with other services can improve IBM watsonx Orchestrate. For example, integrating directly with Azure infrastructure, including AI services in Azure such as Data Factory in Azure and other data services, would be beneficial.

I have been using IBM watsonx Orchestrate for six months.

IBM watsonx Orchestrate is stable.

The scalability of IBM watsonx Orchestrate is good.

The customer support is good. I rate the customer support an eight out of ten.

I cannot disclose if we previously used a different solution, including which solution and why we switched.

We evaluated other options before choosing IBM watsonx Orchestrate.

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.

My main use case for IBM watsonx Orchestrate is developing new virtual AI assistants.

A quick specific example of how I've used IBM watsonx Orchestrate in my recent AI work is creating an AI assistant for students.

Students are involved by consulting the AI assistant for their class assignments.

Students consult the assistant for their assignments, and the assistant supports them by guiding them step by step and helping them consult documents.

The best features IBM watsonx Orchestrate offers are ease of implementation and customization.

When I mention system customization, I appreciate the possibility to tailor our own workflows and integrations.

IBM watsonx Orchestrate has positively impacted my organization by providing ease of implementation, configuration, and integration, making it very easy and possibly beneficial for the team.

The ease of implementation and integration has helped my team by allowing people who don't know how to code to work with this platform, streamlining processes and automation across departments.

IBM watsonx Orchestrate can be improved by including the possibility of incorporating external AI models.

I have been using IBM watsonx Orchestrate for one year.

IBM watsonx Orchestrate is stable.

IBM watsonx Orchestrate's scalability is fine and acceptable.

The customer support takes longer than is reasonable.

I did not previously use a different solution before IBM watsonx Orchestrate.

My experience with pricing, setup cost, and licensing in Brazil has been relatively straightforward.

At my organization, business users leverage the no-code tools within IBM watsonx Orchestrate to create custom AI agents for their specific workflows very effectively, facilitating development and enabling more people to create our workflows.

When orchestrating workflows across hybrid cloud and on-premises systems using IBM watsonx Orchestrate, I consider ease of implementation, integrations, and latency as the most relevant technical aspects.

The mechanisms within IBM watsonx Orchestrate that inform my approach to maintaining enterprise-grade security and governance for AI agent operations involve IBM Cloud infrastructure.

My developers have utilized the Agent Development Kit, ADK, only for the AI assistant.

For real-time observability of AI agent performance and workflow execution within IBM watsonx Orchestrate, I employ proprietary dashboards and a database.

I have seen a return on investment.

The return on investment I have seen includes a reduction in time, although there could be a plan for countries where the dollar exchange rate is very high.

My experience with pricing, setup cost, and licensing in Brazil has been relatively straightforward.

I did not evaluate other options before choosing IBM watsonx Orchestrate.

IBM watsonx Orchestrate's AI capabilities are excellent for governance and security.

Its accuracy and reliability of output are very good, with secure and accurate data especially for audits.

My advice to others looking into using IBM watsonx Orchestrate is to make the most of the platform and be creative.

I rate this review an eight out of ten.

My main use case for IBM watsonx Orchestrate is that my team has built an AI agent leverages the agentic capabilities of IBM watsonx Orchestrate.

A specific example of how my AI agent works in practice is that a typical workflow may include a financial institution adopting the agent to perform Know Your Customer checks on their customers signing up for a new bank account. The end user talking to the agent via the built-in IBM watsonx Orchestrate chatbot would be prompted to provide various documents that verify their identity.

We did not use the no-code tools within IBM watsonx Orchestrate; we went the Python development route instead.

My developers have utilized the Agent Development Kit, ADK, to extend the capabilities of IBM watsonx Orchestrate specifically for the KYC agent that we developed, and we used the full range of tooling and offering of the ADK.

IBM watsonx Orchestrate has positively impacted my organization by allowing us to strengthen our relationship with IBM and our partnership. IBM watsonx Orchestrate specifically has helped us reach new customers through this new product offering of the KYC agent on IBM Marketplace catalog.

The best features IBM watsonx Orchestrate offers for my use case are that it is very simple and easy to get started with in terms of developing new AI agents and testing them end-to-end.

What stands out to me about the simplicity and ease of getting started is that there is comprehensive documentation that is very clear and easy to read, which definitely plays a part in the getting started UI. When building a new agent, there are many options and it is simple to get started.

Regarding IBM watsonx Orchestrate's AI capabilities, I think its governance and security appear to be top-notch. It is still a little early for us to tell, but I appreciate the robust logs that I can review.

Regarding IBM watsonx Orchestrate's AI capabilities, I find that the accuracy and reliability of output is challenging because AI can hallucinate and is not 100 percent accurate. From what I have seen with this agent project, it is fairly accurate.

IBM watsonx Orchestrate could be improved by reducing the onboarding experience and getting the AI agent live. The onboarding took several months of working with an account team, and there were some bugs in the submission process. Having that be reduced to days or more automated would be very useful and appreciated.

I have been using IBM watsonx Orchestrate for about six months.

IBM watsonx Orchestrate is very stable.

As for IBM watsonx Orchestrate's scalability, we have not progressed far enough to worry about that yet, but I imagine with it being IBM and their well-known legacy, it should be fine.

The customer support for IBM watsonx Orchestrate is good. We have been able to resolve any questions we have had with the support team.

We were not using another solution before, and there was nothing that led us to switch to IBM watsonx Orchestrate.

n/a

Before choosing IBM watsonx Orchestrate, we did not evaluate other options. We had a relationship with IBM, so that made it a natural choice.

I rate IBM watsonx Orchestrate overall an eight out of ten. I say eight because of the challenges to the onboarding and submission process that I mentioned previously.

We are not deploying IBM watsonx Orchestrate within our organization, but we are using it to reach new audiences via the catalog and the new KYC agent project.

For real-time observability of AI agent performance and workflow execution within IBM watsonx Orchestrate environment, that is an area we still need to set up. Currently, we are reviewing the logs that are built into the ADK and IBM watsonx Orchestrate platform.

I would advise others looking into using IBM watsonx Orchestrate to consider it as a solid platform worth investigating. I would rate the customer support of IBM watsonx Orchestrate a ten out of ten.