Key takeaways
- Developers keep the terminal and IDE they use today and point an open coding agent, OpenCode, at an Enterprise h2oGPTe endpoint inside your network.
- The agent helps with the daily work: writing and refactoring code, reviewing pull requests, writing tests, drafting documentation, and explaining unfamiliar code.
- It answers from your own repositories, internal API docs, design records, and runbooks, and it cites what it used.
- H2O Cascade fine-tunes open code models on your repositories, so the model learns your conventions without the code going to an outside service.
Your developers want AI help, and your code cannot leave
Your engineering teams see what AI coding tools can do and want them in their daily work. Your security team will not let source code, internal API specifications, or design records go to an outside coding service. In some networks that service is not reachable at all.
So you end up with two groups. Some developers use a cloud assistant under a policy exception, with per-seat spend that keeps growing. Others, often on the most sensitive code, get no AI help at all.