Skip to Main Content
Shape the future of IBM watsonx Orchestrate

Start by searching and reviewing ideas others have posted, and add a comment (private if needed), vote, or subscribe to updates on them if they matter to you.

If you can't find what you are looking for, create a new idea:

  1. stick to one feature enhancement per idea

  2. add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)

  3. Explain business impact and timeline of project being affected

[For IBMers] Add customer/project name, details & timeline in Hidden details field or a private comment (only visible to you and the IBM product team).

This all helps to scope and prioritize your idea among many other good ones. Thank you for your feedback!

Specific links you will want to bookmark for future use
Learn more about IBM watsonx Orchestrate - Use this site to find out additional information and details about the product.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Under review
Created by Guest
Created on Jul 21, 2026

Alternative Licensing Models for Anonymous Users and Automated Workloads

The current per-user (MAU) option (with the 50-message cap) is great and handles a lot of standard scenarios well.

However, we run into roadblocks with use cases where the end-user is anonymous, impossible to identify, or when the "client" calling the system is actually another application. For those scenarios, it would be awesome to have alternative licensing options—like billing based on LLM tokens consumption or per agent workflow execution.

The idea isn't to overcomplicate the licensing structure, but just to give clients a bit more flexibility when user-based pricing doesn't quite fit their architecture.

To make a consumption-based approach viable, it would also be helpful to include some built-in safety rails:

Cost tracking: A way to monitor LLM usage and keep an eye on billing costs.

A "Hard Stop": A feature that lets admins set a budget threshold and automatically blocks or pauses execution if it gets hit, avoiding any surprise costs.

Idea priority Low