IBM Bob is moving into the environments where enterprises keep their most sensitive software and data. As of October 2, 2026, IBM has made a self-hosted deployment option for its agentic software development platform generally available, opening Bob to on-premises systems, private and sovereign clouds, and air-gapped networks.
The shift gives enterprise customers a new way to use Bob without moving their code into an externally hosted environment. Customers run Bob inside their own managed infrastructure, choose a supported model, and decide how inference fits into their development workflow. That brings agentic software development into settings where deployment requirements shape every technology decision.
Bob Brings Its Core Development Experience On Premises
The self-hosted deployment carries the core Bob experience into customer-managed enterprise environments. Developers receive the IDE experience, BobShell, parallel tool calling, the agent harness, skills and modes, giving them the same central platform capabilities across different deployment choices.
That consistency matters when an organization uses more than one model configuration. IBM makes self-hosted, air-gapped and hybrid model configurations available, so teams can match the deployment approach to the workload while keeping the core Bob experience in place.
A customer must source, license and host a supported model itself for the self-hosted option. Bring-your-own-license, or BYOL, is available for eligible models on IBM’s supported list, and IBM groups that list by deployment method.
At general availability for self-hosted deployment, the supported models include:
- NVIDIA Nemotron
- Poolside Laguna
- Claude Sonnet 5.0
- Claude Opus 4.8
- Gemini 3.7 Flash
- OpenAI GPT 5.6 Sol
That model list creates a clear path for customers that need full isolation, as well as organizations that want to combine isolated and external model deployments. Customers can bring their own model, with Nemotron or Poolside Laguna available for full isolation, while hybrid mode routes selected workloads to Claude, Gemini or GPT models.
Hybrid Routing Connects Isolation With Model Choice
The strongest enterprise use case may come from combining deployment methods instead of choosing only one. A customer can run inference for core banking applications on premises, keeping that workload inside its own environment, while routing a less restricted workload to an approved external model.
Developers see a consistent core Bob experience in both cases. The model destination changes, but the development platform remains familiar, allowing teams to work across on-premises and external model configurations without leaving the Bob workflow.
This approach gives enterprises a way to separate workloads according to their requirements. Full isolation can support selected applications, while hybrid routing can send other workloads to approved external models. IBM’s description of these configurations centers on where models run and how customers manage them, not on a single deployment pattern for every application.
The model portfolio will not stop with the options available at general availability. IBM plans to expand the model portfolio and add multi-model routing, which points toward a broader system for directing workloads across supported models.
Enterprise Deployment Comes With A Direct Buying Path
IBM has made IBM Bob self-hosted generally available to enterprise customers for on-premises, sovereign cloud and air-gapped use. The deployment option includes Bob running in customer-managed enterprise environments, but customers take responsibility for sourcing, licensing and hosting a supported model.
IBM has not published pricing for the self-hosted deployment. Buyers are directed to request a demo, making that request the next step for enterprises evaluating the option and its deployment requirements.
The offering also extends beyond a single programming environment. Premium Packages extend Bob to Java, IBM i and IBM Z modernization, bringing the platform into development and modernization work across those environments.
That combination of deployment flexibility and broader modernization coverage gives IBM Bob a clear enterprise focus. Customers can choose on-premises operation, sovereign cloud, air-gapped deployment or a hybrid model configuration, then use the same core Bob experience across those choices.
The next stage will depend on the model portfolio and routing capabilities IBM adds. With self-hosted Bob now generally available, enterprises can place agentic software development closer to the systems they manage while keeping options open for approved external models. For organizations balancing isolated workloads with broader model access, that is the opening move in a more flexible development architecture.
