live wire
▸AI · EAGLE-4 0.1.4 fixes multi-GPU vLLM collective ordering during startupEAGLE-4▸SECURITY: Apache Camel 4.23.0, 4.22.2 and 4.18.5 fix eight component vulnerabilitiesApache Camel▸AI · Red Hat shows DRA doubles llm-d KV-cache throughput by aligning GPUs and RDMA NICsRed Hat Developer▸Red Hat Developer Hub 1.9.10 ships as a Critical security updateRed Hat errata▸OpenShift Dev Spaces 3.31 adds live editor switching and DevWorkspace Operator 1.0Red Hat documentation▸OpenShift Pipelines 1.24.1 tightens Manual Approval Gate RBAC and approval integrityRed Hat release notes▸AI · Red Hat survey: 97% of UK CIOs trust agent security, but 43% can trace data flowsRed Hat▸JAVA · IBM and Kaggle launch a living benchmark for agentic Java framework migrationsIBM Research▸AI · Red Hat tests policy-derived data controls for AI agentsRed Hat▸Apache Camel pattern turns routes into bounded LLM tools and MCP servicesRed Hat Developer▸Atos tunes small models on OpenShift AI for structured German-language analysisRed Hat Developer▸Red Hat publishes checklist for evaluating third-party OpenShift applicationsRed Hat Developer▸SECURITY · OpenShift 4.21.40 patches OpenSSL, OpenSSH and PCRE2 flawsRed Hat Product Security▸SECURITY · Apache Camel fixes A2A webhook SSRF gap in 4.22.2 and 4.23.0 (Oct. 23)Apache Camel▸AI · EAGLE-4 0.1.4 fixes multi-GPU vLLM collective ordering during startupEAGLE-4▸SECURITY: Apache Camel 4.23.0, 4.22.2 and 4.18.5 fix eight component vulnerabilitiesApache Camel▸AI · Red Hat shows DRA doubles llm-d KV-cache throughput by aligning GPUs and RDMA NICsRed Hat Developer▸Red Hat Developer Hub 1.9.10 ships as a Critical security updateRed Hat errata▸OpenShift Dev Spaces 3.31 adds live editor switching and DevWorkspace Operator 1.0Red Hat documentation▸OpenShift Pipelines 1.24.1 tightens Manual Approval Gate RBAC and approval integrityRed Hat release notes▸AI · Red Hat survey: 97% of UK CIOs trust agent security, but 43% can trace data flowsRed Hat▸JAVA · IBM and Kaggle launch a living benchmark for agentic Java framework migrationsIBM Research▸AI · Red Hat tests policy-derived data controls for AI agentsRed Hat▸Apache Camel pattern turns routes into bounded LLM tools and MCP servicesRed Hat Developer▸Atos tunes small models on OpenShift AI for structured German-language analysisRed Hat Developer▸Red Hat publishes checklist for evaluating third-party OpenShift applicationsRed Hat Developer▸SECURITY · OpenShift 4.21.40 patches OpenSSL, OpenSSH and PCRE2 flawsRed Hat Product Security▸SECURITY · Apache Camel fixes A2A webhook SSRF gap in 4.22.2 and 4.23.0 (Oct. 23)Apache Camel
upstreambeat.ai
newsAI

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.

Self-hosted vs hybrid IBM Bob on OpenShift.
AI-generated illustration
By The News Desk· Oct 5, 2026the quick take — two AI hosts go live when you do

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

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk