Zone 1
IBM Cloud
- watsonx Orchestrate
- watsonx.ai and Granite
- watsonx.governance
Managed services for building, running and governing agents.
Build on IBM watsonx and Red Hat
watsonx Orchestrate, Granite, watsonx.data and Red Hat OpenShift, engineered into agents that work across cloud, data centre and mainframe, with governance built into delivery.
How we see it
Many IBM estates run across public cloud, private data centres and IBM Z or Power systems, often under sovereignty rules. Moving everything first is rarely the right answer.
We build agents that reach data where it lives, run where policy allows and produce the governance evidence your risk team asks for, using watsonx and Red Hat OpenShift as the common layer.
Hybrid by design
One agent system can span IBM Cloud, your own data centre and IBM Z. Red Hat OpenShift keeps it consistent, and governance records every decision along the way.
Zone 1
Managed services for building, running and governing agents.
Zone 2
Models and data stay where your rules require.
Zone 3
Agents reach the systems of record without moving them.
Every model, agent, prompt and dataset in use, with an owner.
The use case, its impact and the controls it needs.
Test sets, scores and the thresholds a release must meet.
Who signed off, when and on which evidence.
Drift, failures and policy breaches in production, with alerts.
An illustrative design
An underwriter asks for a summary of a renewal. The agent reads the policy file, checks the core system on the mainframe and drafts a recommendation. The underwriter decides, and the evidence is recorded.
| # | Step | Where it runs | What is recorded |
|---|---|---|---|
| 01 | Underwriter asks | watsonx Orchestrate | Request and user identity |
| 02 | Agent plans the steps | Orchestrate ADK agent | Plan and agent version |
| 03 | Reads the policy file | watsonx.data · Docling | Documents retrieved |
| 04 | Checks the core system | MCP tool → Db2 on IBM Z | Tool call and response |
| 05 | Drafts the summary | AI Gateway · Granite or Claude | Model, prompt and output |
| 06 | Underwriter decides | Decision stays with a person | Decision and reviewer |
| 07 | Evidence recorded | watsonx.governance | Linked to the use-case record |
The IBM AI stack
Open a layer to see the IBM services involved and the part we take on.
What we build. We bring the agent into the tools people already use and design how it explains its reasoning and asks for approval.
What we build. We build agents with the Orchestrate ADK, bring in agents from other frameworks and coordinate them in multi-agent workflows.
What we build. We expose core systems as MCP or OpenAPI tools, including those on IBM Z and IBM i, with narrow permissions and recovery paths.
What we build. We prepare documents with Docling, connect governed data through watsonx.data and keep lineage visible from source to answer.
What we build. We test Granite, Claude and open models on your tasks and run them where your data rules allow, in IBM Cloud or on your own hardware.
What we build. We record models, risks and evaluations in watsonx.governance, trace agents with AgentOps and watch the platform with Instana.
What changed on IBM
The releases that change how we design and build on IBM, with a link to each announcement.
IBM and Anthropic announced Claude in select IBM software, starting with IBM’s AI development tool, and a guide to building secure agents with MCP.
OpenShift AI 3 brought distributed inference with llm-d and vLLM, for serving models on your own infrastructure.
An AI development partner that routes work across Claude, Granite and other models. Mainframe, IBM i and Java modernization packages followed in July.
Sovereign operations built on OpenShift and Red Hat AI reached general availability at Think.
IBM’s open, Apache 2.0 models gained step-by-step reasoning while staying small enough to run on your own hardware.
Our services on this platform
How each stage of our work maps to IBM. Start at whichever stage fits where you are.
Decide what is worth doing.
An Orchestrate agent with Granite or Claude, on your examples, in three business days.
watsonx Orchestrate · watsonx.ai
Build the system.
ADK agents connected to your core systems through MCP and OpenAPI tools.
Orchestrate ADK · MCP · watsonx.data
Applications on OpenShift that run the same in IBM Cloud and your data centre.
Red Hat OpenShift · Db2 · Event Streams
Make it dependable.
Guardrails, AgentOps tracing and AI security before broader rollout.
Guardium AI Security · AgentOps
COBOL, PL/I and IBM i applications understood and modernized with their rules kept.
IBM Bob · Z and IBM i packages
Keep it healthy.
OpenShift and application telemetry triaged by agents, decided by engineers.
Instana · OpenShift
Cloud and Kubernetes spend made visible and right-sized.
Cloudability · Turbonomic · Kubecost
Model inventories, risk assessments and evaluation records in one place.
watsonx.governance
Add capacity.
Engineers who know watsonx, OpenShift and Ansible, inside your team.
OpenShift · Ansible · Terraform
Claude on IBM
Claude is built into IBM Bob and can be selected through the watsonx Orchestrate AI Gateway alongside Granite. We test both on your task and deployment constraints, and use Granite where a smaller open model running on your own infrastructure is the better fit.
How we build with ClaudeUnder the agents
Red Hat OpenShift · IBM Kubernetes Service · Virtual Servers
One container platform across IBM Cloud, other clouds and your data centre.
IBM Z · LinuxONE · Power · IBM i
Connect agents to the systems that hold your most important records, without moving them first.
Db2 · Cloudant · IBM Cloud Object Storage
Relational, document and object data, integrated or migrated with care.
IBM Confluent · IBM Event Streams
Event-driven connections with clear processing, retry and operational behaviour.
Ansible · Terraform · Schematics
Versioned infrastructure and repeatable environments across the hybrid estate.
IBM Cloud IAM · Key Protect · Instana · Sovereign Core
Access, encryption, observability and sovereignty controls in the architecture from day one.
Questions
Tell us about your application, your IBM environment, or the idea you want to explore.