IBM Brings Bob Coding Assistant On Premises, With Customer-Supplied Models

Enterprises can now run IBM’s Bob AI coding assistant on their own infrastructure, including in air-gapped environments. IBM announced general availability on September 30, 2026. The release brings its development tools to sensitive software, but keeping code inside the customer environment depends on the model configuration—not simply where Bob is installed.

That changes a restriction in earlier versions. IT Jungle reports that Bob previously sent each query to IBM’s cloud for processing. IBM is targeting organizations whose security, data-sovereignty or operational rules require source code, application context and build artifacts to stay within approved environments. It names financial services, government, healthcare and critical infrastructure among the intended users.

The distinction is between accessing code and processing it. Bob 2.0, released in June, added direct connections to code residing on IBM i through its Premium Package for i. That removed the need to download all source code to a local client or the cloud. But, as IT Jungle explains, model requests still went to IBM’s cloud.

Local models and external services are different paths

Customers must source and provide access to a supported model. For a fully self-hosted setup, they install and manage that model themselves. Eligible existing model licenses can be used through a bring-your-own-license arrangement. Bob’s general availability therefore supplies the development platform, not a bundled model that removes those deployment decisions.

IBM illustrates the distinction with a hypothetical bank: development involving core banking applications could use on-premises model processing, while a less restricted workload could connect to an approved external service. Developers retain a consistent core Bob experience; platform and security teams choose the architecture underneath based on each workload’s requirements.

That flexibility does not mean automatic model selection is already included. IBM plans to add multi-model routing in future releases, alongside a broader supported model portfolio. The company describes routing as a way to match models to development tasks while balancing capability, performance and cost. Those remain roadmap goals, not delivered features.

Development tools stay; modernization packages add context

IBM’s modernization pitch starts with understanding existing systems, rather than writing new code. Long-lived applications can contain years of business logic, dependencies and technical debt. The company says developers need to identify those connections and assess how proposed changes could affect surrounding applications before modernizing them. Its optional packages add context for that work on specific platforms.

The self-hosted release includes Bob’s code-editor experience, BobShell, parallel tool calling, and the agent harness—the layer supporting its agent workflow—plus skills and modes. IBM describes Bob as handling more than code generation: understanding applications, planning multistep work, executing changes and validating results. Optional Premium Packages add platform-specific capabilities, subject to licensing and deployment requirements:

• Java Modernization adds dedicated modernization workflows.
• IBM i adds platform-specific connectivity, workflows, tools and IBM i knowledge.
• IBM Z adds application understanding and modernization capabilities, including platform context and application analysis.

Pricing remains undisclosed, according to Marktechpost. IBM directs prospective customers to a demo and offers to help evaluate supported configurations, infrastructure requirements and optional packages. The purchasing decision therefore involves both Bob and the customer-provided model setup.