Composer
Enterprise AI does not become useful because it can talk. It becomes useful when it can work — safely, selectively, and only through capabilities the business has approved.
Compositions are a new governed capability layer for enterprise AI. They turn business know-how into reusable capabilities that can be created, controlled, published, and safely used by agentic AI — across one system, many systems, or the full landscape of the business.
The family is deliberately simple. Composer creates Compositions. Director provides identity, access, user and group management, and central visibility of every registered node. Conductor controls which Compositions are available to which groups, and publishes them to approved consumers. An AI client — BrainStorm, or another you approve — then uses those published Compositions to move from conversation to practical business outcomes.
Composer creates. Director governs. Conductor publishes. Your AI acts.
- Capabilities the business defines — not prompts, not guesswork.
- One system, several, or the whole landscape.
- Every capability gated by group. Users see only what suits their role.
- Published deliberately. Nothing reaches an AI client by accident.
- Central identity, access and node visibility.
- BrainStorm is one consumer — and remains a separate product.
An AI that can do anything is an AI you cannot deploy.
Give an AI broad reach into the systems that run a business and you have created something nobody will sign off. Give it none, and you have a chatbot. The industry has spent two years stuck between those two answers.
Compositions resolve it by changing what the AI is given. Instead of access, it is given capabilities: specific, named, reviewed things the business has decided are safe and useful — and nothing else. The AI cannot exceed them, because it was never handed the means to.
That is what makes this deployable. The question in the room stops being “what might it do?” and becomes “which capabilities have we approved?” — a question a business can actually answer, in a meeting, with names on it.
- Broad access → approved capabilities
- “What might it do?” → “What did we approve?”
- One system at a time → one answer, from wherever the truth lives
- Conversation → outcome
Capture the know-how
Every business runs on knowledge that lives in people: which checks matter before a supplier is approved, what “ready to ship” actually means, where the real number comes from when two systems disagree. Composer turns that knowledge into a capability that can be used again, by anyone entitled to it, without the person who knew it being in the room.
Make it reusable
A Composition is built once and used indefinitely. It does not decay when the author moves on, and it does not have to be rediscovered by the next team who needs it.
Keep it under control
Nothing a Composition can do is a surprise, because the business decided what it does. Capabilities are reviewed before they are published, published to named groups rather than to everyone, and withdrawn the moment they should be.
Turn conversation into outcome
Users stop needing to know which system holds which answer, which team owns which process, or which path leads to the right result. They ask for the outcome. The approved capability delivers it.
Composer creates
A productive place to build reusable business capabilities — and to keep improving them as the business changes.
Director governs
Identity, sign-on, users, groups and access — plus a live view of every registered node. More →
Conductor publishes
Decides which Compositions reach which groups, and releases them to approved consumers. More →
BrainStorm acts
One consumer of the layer — and a separate product. It works on its own; with Compositions it works on your business. More →
BrainStorm remains independent, and is sold separately. Compositions make it more capable. Director makes it controlled. Conductor makes it selective. Composer makes it practical.
And the whole ensemble is scalable by design. Add a capability and everyone entitled to it has it. Add a system and it is governed like everything else. Add a thousand users and nobody decides anything twice.
One system, many, or the whole landscape
Compositions can be created for JD Edwards EnterpriseOne, JD Edwards World, Ariba, SAP, reporting platforms, internal applications, partner systems, and beyond.
One source or several. One answer, assembled from wherever the truth lives.
This is the part that changes the conversation with the business. The question a user has is almost never confined to one system — but the tools they were given always were. A capability is not obliged to respect that boundary, and the person asking should never have had to.
- JD Edwards EnterpriseOne
- JD Edwards World
- SAP
- Ariba
- Reporting and analytics platforms
- Internal and bespoke applications
- Partner and third-party systems
Nothing is implicit
A capability reaches a user because someone decided it should. Compositions are published to groups, and a user sees only the capabilities their groups allow. A user with no group sees nothing beyond what is explicitly public.
Withdrawing a capability is a single act, and it takes effect for everyone who held it.
Central identity
Director owns sign-on, users, groups and access for the whole family. There is no second place where a user might exist, and no component that can be reached around it.
Visible by design
Every node registers itself with Director and reports in continuously. What is deployed, where, on which version, and whether it is healthy — on one screen. An administrator can approve a node, or disable it, and that decision is enforced centrally rather than requested politely.
A question your security team can answer
“What can the AI do?” has a list for an answer. That list was reviewed, it is versioned, and it is enforced — which is a materially different conversation from the one most AI projects are currently having.
Licensing
Annual subscription, sized by the systems your Compositions reach and the population entitled to use them — not by the handful of people who author them. Authoring seats are included: the last thing we want to do is charge you for building more capability. A fixed-price Pilot / Proof-of-Value is available to remove buyer risk. Contact us for a demo or quote, or see the pricing page for editions and indicative figures.
Director and Conductor are not separately licensed. They are how Composer is governed and delivered, and they come with it.
Common questions about governed AI
These pages explain the specific problems the Compositions family solves: governing what AI may do, publishing capability selectively, and reaching across more than one business system.
The argument, in full
Independent guides on JDE Citizen Developer, our companion site. No sales pitch — just the problem, and what it takes to solve it.
Composer creates. Director governs. Conductor publishes. BrainStorm acts.
A governed capability layer for agentic AI — reaching across JD Edwards, Ariba, SAP, reporting platforms and the applications you built yourself, to deliver coherent answers and practical outcomes.
Order or Inquire