# IBM watsonx Orchestrate Enterprise platform for building and managing agents and business workflows. Canonical profile: https://ki-agentenkompass.de/en/agents/watsonx-orchestrate/ Editor: [Michael Meierhoff](https://ki-agentenkompass.de/en/about/) Sources reviewed: 2026-10-19 Basis: provider documentation. Examples are editorial suggestions, not hands-on product tests. ## Overview Available enterprise platform with agent building and orchestration. - Provider: IBM - Product family: IBM watsonx Orchestrate - Profile type: Agent platform - Environment: IBM Cloud, AWS or own infrastructure - Connections: Build agents, Documents, Tool catalog, Custom tools, Control access - Setup: Set up trial access or a contract and connected business systems. - Pricing model: 30-day trial; Essentials from USD 530/month, regional terms and taxes separate. ## Key features ### Build agents Configure custom agents and workflows. Source: https://www.ibm.com/products/watsonx-orchestrate/pricing ### Documents Incorporate document processing into workflows. Source: https://www.ibm.com/products/watsonx-orchestrate/pricing ### Tool catalog Use integrations and agents from the catalog. Source: https://www.ibm.com/products/watsonx-orchestrate/pricing ### Custom tools Add business functions as custom tools. Source: https://www.ibm.com/products/watsonx-orchestrate/pricing ### Control access Manage security and access rules. Source: https://www.ibm.com/products/watsonx-orchestrate/pricing ## Example workflows ### Example task 1 - Your input: Model an internal service process with approval. - Possible result: A draft for expert review. - What to check: Check inputs, output and performed actions. ### Example task 2 - Your input: Prepare incoming documents for the responsible team. - Possible result: A draft for expert review. - What to check: Check inputs, output and performed actions. ## Requirements and limits ### Setup Requirement: Set up trial access or a contract and connected business systems. Source: https://www.ibm.com/products/watsonx-orchestrate/pricing ### Product boundaries Limitation: Check quotas, integration effort and regional contract terms. Source: https://www.ibm.com/products/watsonx-orchestrate/pricing ### Output quality Not yet confirmed: Success rates and German-language operation have not been tested here. Source: https://www.ibm.com/products/watsonx-orchestrate/pricing ## A good fit if … - your company wants to run agents and workflows as a cloud service on IBM Cloud or AWS, or in its own environment - you can build workflows with approval steps and schedules - you need to distinguish shared team connections from personal connections to external systems ## Less suitable if … - you want a simple single-user tool; the pricing page lists indicative prices from USD 578 per month - you need OAuth sign-ins inside web chat embedded on your own website Editorial assessment based on provider documentation. Not a product test. ## Usable AI models Open choice Besides IBM models you can register external models, for example from OpenAI, Anthropic, Google, Mistral or xAI, also through OpenRouter, Ollama or your own OpenAI-compatible endpoint. According to IBM, custom endpoints and gateways might not be fully supported, and only a few models have optimized support. The pricing page names a "Premier LLM" add-on but does not say which models the plans include. - Model families named: IBM (Granite), OpenAI (GPT), Anthropic (Claude), Google (Gemini), Mistral, xAI (Grok), Meta (Llama, Muse) · Other models can be connected freely - Model choice: You choose - Your own API key: Yes - Router or custom endpoint: Yes - Local models: Yes - Depends on: Plan Documented · Sources accessed on: 2026-11-05 - [watsonx Orchestrate ADK: Managing LLMs](https://developer.watson-orchestrate.ibm.com/llm/managing_llm) - [IBM: watsonx Orchestrate pricing](https://www.ibm.com/products/watsonx-orchestrate/pricing) ## Europe & regional availability Official product and regional sources reviewed. The stated open points still require confirmation from the provider. Reviewed scope: Product access, feature limits and regional evidence Reviewed on: 2026-10-19 ### German purchasing offer and European regions With requirements IBM offers watsonx Orchestrate on its German product page with euro pricing, a purchase option and a 30-day trial. Frankfurt and London are documented service regions. Plan, deployment and connected models determine the specific scope. Region covered: Germany; other countries subject to the offer Documented reason: The German sales offering and regional service matrix establish the stated access. Official source: https://www.ibm.com/de-de/products/watsonx-orchestrate Official source: https://cloud.ibm.com/docs/overview?locale=de&topic=overview-services_region ## Accounts & permissions Based on provider documentation. Permissions depend on the account, integration and organization policies. Review the permissions actually requested before use. Configuration covered: IBM watsonx Orchestrate as an enterprise platform (cloud service or own environment) with connections to external systems Sources reviewed: 2026-11-05 ### Account used Documented: A connection holds the details agents and tools use to authenticate with an external system. It is scoped either per user (member) or shared across the team; key-value connections are team-only. With OAuth, the person signs in interactively and Orchestrate generates an access token on their behalf. Evidence: https://developer.watson-orchestrate.ibm.com/connections/overview ### Admin approval Documented with conditions: The pricing page lists security and access control from the Essentials plan; Premium adds data isolation for sensitive workflows and a dedicated data space. Which roles may manage what was not stated on the reviewed pages. Evidence: https://www.ibm.com/products/watsonx-orchestrate/pricing ### Data access & team sharing Documented with conditions: Connections are scoped per user (member) or shared for the team. The page does not say exactly who can access a team connection. OAuth connections currently work only when you interact through the Orchestrate UI, not in embedded web chat. Evidence: https://developer.watson-orchestrate.ibm.com/connections/overview ## Prices and included usage Pricing checked: 2026-10-19 30-day trial; Essentials from USD 530/month, regional terms and taxes separate. Billing depends on plan, usage and setup. Pricing details: https://www.ibm.com/products/watsonx-orchestrate/pricing ## Operation & oversight Based on public provider documentation. Assessments are editorial inferences from the stated properties. Actual time requirements and reliability have not been measured. Deployment covered: Agentic workflows and agents in watsonx Orchestrate (ADK developer documentation) Sources reviewed: 2026-11-05 ### Files and working state Documented with conditions: Workflows run asynchronously and can take minutes, hours or days; an invocation returns an instance ID that you use to check progress in a new chat session. Nothing is stated about files and working state outside workflows. Evidence: https://developer.watson-orchestrate.ibm.com/tools/flows/overview ### Sign-ins Open in reviewed sources: The connections documentation contains nothing on token refresh or expiry. Evidence: https://developer.watson-orchestrate.ibm.com/connections/overview ### Starting further runs Documented: Workflows and agents run automatically at specific times or intervals when configured as schedulable. Schedules can be created in chat using natural language. Evidence: https://developer.watson-orchestrate.ibm.com/tools/flows/overview ### Human intervention Documented with conditions: Workflows can include human interaction for approvals or decisions; a sample displays a form to the user in the chat. This applies only where the workflow includes such steps. Evidence: https://developer.watson-orchestrate.ibm.com/tools/flows/overview ### Detecting errors Documented with conditions: Registered agents get a trace view, dashboards and a trace API; technical and business failures are recorded separately. The article describes this for externally running agents. Evidence: https://developer.ibm.com/articles/watsonx-orchestrate-agentic-control-plane/ ### Resuming after failures Open in reviewed sources: The reviewed page does not cover error handling, retries and resumption of workflows. Evidence: https://developer.watson-orchestrate.ibm.com/tools/flows/overview ### Editorial assessment Schedules, approval nodes and traces exist but must be set up per workflow. Recovery after failures and the role model should be clarified with IBM. ## Memory and conversation continuity Scope: Orchestrate agent memory; documented preview feature Sources accessed: 2026-11-04 User- and tenant-scoped facts with controls and a 30-day idle retention interval. ### Storage and scope Documented: Extracted facts are stored encrypted in Orchestrate, separately from chat history. - [Memory behavior and limits](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=memory-behavior-limits) - [Using agent memory in conversations](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=memory-using-agent-in-conversations) - [Orchestrate release notes](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=releases-release-notes-march-2026) ### Selection and timing Documented: With memory enabled, the agent automatically analyzes messages for durable facts and preferences; explicit remembering is also supported. - [Memory behavior and limits](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=memory-behavior-limits) - [Using agent memory in conversations](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=memory-using-agent-in-conversations) - [Orchestrate release notes](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=releases-release-notes-march-2026) ### Inspect, edit and delete Documented: Agent Memory provides inspection, editing and individual or complete deletion; updates and forgetting also work in conversation. - [Memory behavior and limits](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=memory-behavior-limits) - [Using agent memory in conversations](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=memory-using-agent-in-conversations) - [Orchestrate release notes](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=releases-release-notes-march-2026) ### Agent and channel boundaries Documented: Memory is isolated per user and tenant but shared across that user's memory-enabled agents. Draft and live use the same records. - [Memory behavior and limits](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=memory-behavior-limits) - [Using agent memory in conversations](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=memory-using-agent-in-conversations) - [Orchestrate release notes](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=releases-release-notes-march-2026) ### Retrieval Documented: Stored facts are used in later chats; queries can show memories. A complete view is available in the memory pop-up. - [Memory behavior and limits](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=memory-behavior-limits) - [Using agent memory in conversations](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=memory-using-agent-in-conversations) - [Orchestrate release notes](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=releases-release-notes-march-2026) ### Session reset and compaction Partly documented: Memory survives chat deletion and signing out and back in; entries expire after 30 idle days under LRU. Context compaction is not explained in these memory pages. - [Memory behavior and limits](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=memory-behavior-limits) - [Using agent memory in conversations](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=memory-using-agent-in-conversations) - [Orchestrate release notes](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=releases-release-notes-march-2026) ## Context Check quotas, integration effort and regional contract terms. Provider sources reviewed; examples are editorial suggestions. No hands-on test. ## Open points Requirements and limits, not yet confirmed: - Output quality ## Sources - https://www.ibm.com/products/watsonx-orchestrate/pricing ## Provider Product and provider are documented through the linked original sources. - Operator: IBM - Organization: Provider - Website: https://www.ibm.com/products/watsonx-orchestrate/pricing - Reviewed: 2026-10-19 - Provider source: https://www.ibm.com/products/watsonx-orchestrate/pricing [Sources and method](https://ki-agentenkompass.de/en/sources/)