Return to page

H2O.ai Blog

Filter By:

4 results Category: Year:
How NIH Created a Secure AI Assistant That Reduces IT Service Ticket Volume and Preserves Federal Compliance with H2O.ai
by Bruna Smith | September 19, 2025 Agentic AI, Case Studies, Enterprise h2oGPTe

NIH implemented H2O.ai's h2oGPTe to create a secure, air-gapped generative AI solution that reduced IT service tickets by up to 10,000 annually The AI assistant serves 8,000 employees across 28 institutes without exposing data outside the NIH network The solution integrates directly with SharePoint, providing source-linked answers f...

Read more
H2O.ai + LangGraph
by Betty Candel, Shivam Bansal, Laura Fink, Issac Liu | September 18, 2025 Agentic AI, Agents, Generative AI, LangGraph

We’re hearing from customers who are already bringing H2O.ai and LangGraph together in their technology stacks. LangGraph provides the backbone for structured, reliable workflows, while h2oGPTe contributes deep research, synthesis, and reasoning capabilities. But this isn’t just about LangGraph. h2oGPTe is designed to strengthen any e...

Read more
The Evolution of AI in Banking: Key Insights from Industry Experts

In a rapidly evolving regulatory and technological landscape, AI is no longer just a buzzword in banking—it’s a business imperative. But what does real adoption look like in an industry known for risk sensitivity and regulatory oversight? That was the focus of H2O.ai’s recent webinar, "Turning AI Strategy into Results", where ...

Read more
Agentic AI at Scale: Unlocking Enterprise Value with Domain-Specific LLMs and Exabyte Data
by Betty Candel | March 13, 2025 Agentic AI, H2O LLM Studio, Large Language Models

We’d like to personally thank Savannah Peterson and Dave Vellante for an engaging and insightful discussion on theCUBE, where we discussed the importance of AI’s convergence with enterprise data at scale. NVIDIA GTC always spotlights where AI is headed, from new GPU architectures to state of the art large language models (LLMs). During th...

Read more

ERROR