The Pulse
IBM Makes Bob Self-Hostable for Sensitive Software
IBM made its Bob coding agent generally available for self-hosted deployment on September 30, 2026. The option runs Bob in customer-managed environments, with choices for local models or approved external model services.
AI.info Team · Written with AI ·
IBM announced on September 30 that its Bob coding agent is generally available for self-hosted deployment, giving enterprises the option to run the service in infrastructure they manage. The move is aimed at teams whose source code, application context or build artifacts must stay in controlled environments because of security, sovereignty or operational requirements.
Bob’s backend runs on customer-managed Red Hat OpenShift, either on premises or in an organization’s cloud account, according to IBM’s release notes. Developers can continue using Bob IDE and Bob Shell. IBM said the general-availability release was effective September 24, six days before its announcement.
Where Bob runs—and where model requests go
Self-hosting does not require every model to run inside the customer’s own data center. IBM describes two broad paths: organizations can run supported models on their infrastructure, including on air-gapped networks, or connect Bob to approved external model services through a hybrid configuration. The selected setup determines where inference occurs and how code and development context are processed.
In its release notes, IBM says the self-hosted backend includes identity, an inference gateway, audit logging and usage metering. An organization can connect the identity service to its corporate directory, and IBM’s installation tool supports deployment to an isolated cluster. For hybrid use, model requests—including the code context they carry—go to the customer’s own cloud model account, the company says.
That distinction matters for security teams assessing what “self-hosted” means in practice. IBM’s announcement says code and development context can remain in a customer-managed environment with a supported self-hosted model configuration; a hybrid setup, by contrast, sends model requests to the approved external service.
IBM pitches Bob beyond code completion
IBM presents Bob as an agent for broader software work: understanding applications, planning tasks, making changes and validating results. The self-hosted version includes the IDE experience, BobShell, parallel tool calling, skills and modes. Customers can also add IBM Bob Premium Packages for Java Modernization, IBM i and IBM Z, subject to licensing and deployment requirements.
Neel Sundaresan, IBM’s general manager of Automation and AI, framed the release around enterprise control.
“Organizations need AI that operates inside environments they have control over, especially when working with sensitive code and regulated data.”
Neel Sundaresan, GM of AI and Automation, IBM
Deployment comes with an enterprise buying process
IBM’s Bob release notes say self-hosted deployment is sales-led: organizations contact IBM or a business partner to arrange access and any package entitlements. Installation requires an OpenShift cluster; the release notes describe a two-stage process that gives cluster-wide setup to administrators and lets the Bob-owning team manage the application within its namespace afterward.
IBM’s cloud service remains available for teams that do not need to operate the backend themselves. The self-hosted option adds a different operational choice for organizations with stricter infrastructure constraints, while leaving model selection—and, in hybrid deployments, the movement of code context to an external service—as decisions that depend on the configuration.