IBM Bob self-hosted GA puts model infrastructure in the platform team’s hands
The customer-managed release can keep code and inference inside approved environments, but buyers must supply the OpenShift capacity and a supported model.
IBM has made the self-hosted deployment option for IBM Bob generally available, giving enterprises a supported way to run the coding agent in customer-managed environments, including air-gapped configurations.
The release changes the control boundary, but it does not make the infrastructure disappear. For OpenShift platform teams, Bob is now a capacity, model and operating-model decision rather than only a developer-tool purchase.
What remains inside the environment
IBM’s GA announcement says a supported fully self-hosted configuration can keep code, development context and build artifacts inside the customer-managed environment. Customers can instead connect Bob to a supported external model service in a hybrid or private-SaaS pattern.
The choice determines where inference occurs and how development context is processed. At GA, customers must source and provide access to the model. IBM lists NVIDIA Nemotron and Poolside Laguna for self-hosted use, while supported external services include models from Anthropic, Google and OpenAI. Eligible existing model licenses can be used through a bring-your-own-license approach.
Bob’s core IDE experience, BobShell, agent harness, skills, modes and parallel tool calling are included across the supported deployment configurations. Optional premium packages add workflows for Java modernization, IBM i and IBM Z.
The OpenShift cost is part of the product decision
IBM’s system requirements make clear that this is not a lightweight IDE-side installation. The control plane runs on Red Hat OpenShift in the customer environment, and the sizing model has to account for Bob services, expected concurrent users and the chosen model-serving architecture.
A fully self-hosted model also shifts accelerator capacity, model serving, patching and availability into the customer’s operational boundary. A hybrid configuration can reduce that local inference footprint, but it reintroduces an external service dependency and changes the data-flow review.
The deployment choice should therefore be made by platform, security and development leaders together. Teams evaluating Bob should first classify which repositories and build artifacts must stay local, then map those workloads to a supported model and estimate the OpenShift and accelerator capacity needed for expected concurrency.
IBM says it plans to expand the supported model portfolio and add multi-model routing in future releases. Those capabilities are not part of the current GA boundary, so buyers should size and govern the product against today’s supported configurations rather than the roadmap.
sources
comments · 0