H2O.ai
H2O.ai is an enterprise platform that converges generative and predictive AI on private data. It runs air-gapped, on-premises or in a cloud VPC, serving banks, telcos and government agencies that cannot let data leave their own infrastructure.
What is H2O.ai?
H2O.ai is an enterprise AI platform built on a single premise: an organisation should be able to run modern AI without its data or its models ever leaving its own infrastructure. Founded in 2012 by Sri Ambati and headquartered in Mountain View, California, the company grew out of H2O-3, an Apache-licensed machine learning library for Python and R that it says has drawn more than two million data science users.
The commercial platform joins two lineages usually sold separately. On the generative side sits Enterprise h2oGPTe, marketed as the H2O AI Super Agent: a multi-agent system with schema-driven Document AI that returns structured JSON, audio models that transcribe and translate, vision models that read images, flowcharts and handwriting, a coding assistant, autonomous agents that carry out multi-step web research and iterative code execution, multimodal retrieval-augmented generation with inline citations, configurable guardrails with PII controls, and intelligent routing that picks a model per query on cost, latency and accuracy. On the predictive side sit H2O Driverless AI for AutoML with automatic feature engineering and explainability, H2O Hydrogen Torch for no-code deep learning on image, text and time-series data, and H2O-3.
Around them the company publishes tooling for each role: H2O LLM Studio for no-code fine-tuning, the open-weight Danube3 small language models and H2OVL Mississippi vision-language models, Label Genie for annotation, a Feature Store, H2O MLOps, the low-code H2O Wave application framework, and a GenAI App Store.
Deployment is the real differentiator. Customers choose a Managed Cloud hosted by H2O.ai, or a self-hosted Hybrid Cloud in a private cloud, on-premises or fully air-gapped environment. The homepage puts it plainly: No data sharing. No model exfiltration.
Adoption is concentrated in regulated sectors. H2O.ai cites Commonwealth Bank of Australia cutting scam losses by 70%, AT&T returning twice its generative AI spend in free cash flow, and the NIH serving 8,000 federal employees from an air-gapped assistant. It claims more than 20,000 organisations, was named a Visionary in the 2026 Gartner Magic Quadrant for AI Platforms for Data Science and Machine Learning, and says it was first to reach 75% accuracy on the GAIA benchmark.
What it does
- Converge generative and predictive AI on private, protected data
- Deploy air-gapped, on-premises or inside your own cloud VPC
- Build domain-specific vertical agents that automate multi-step work
- Query internal documents with cited, verifiable retrieval-augmented generation
- Fine-tune small and large language models on private data without writing code
- Automate model building with AutoML feature engineering and explainability
- Run the full machine learning lifecycle from training to production monitoring
When to use H2O.ai / When not to
A quick filter to help you decide if H2O.ai is the right fit.
When to use H2O.ai
- Banks and financial institutions running fraud detection, KYC, loan automation and trade reconciliation on data that cannot leave their premises
- Telecom operators automating call-centre resolution, NOC alert triage and field dispatch optimisation
- Government and federal agencies that need generative AI inside an air-gapped environment, with FedRAMP in-process at High impact level
- In-house data science teams with existing ML skills who want AutoML and generative agents on one platform instead of two
- Regulated organisations that must keep model risk management, explainability and audit trails alongside every AI decision
When not to use H2O.ai
- Individuals and hobbyists: the privacy policy states the services are designed for and directed to enterprise users
- Teams that need a published price before speaking to anyone, since no figure appears anywhere on the site
- Anyone under 18, the minimum age set by the terms of use
- Android users, as only an iOS application exists for h2oGPTe
- Buyers who want instant self-service sign-up, because every route to the enterprise product runs through a sales demo
How to use H2O.ai
A typical end-to-end flow, from setup to results.
- Start at h2o.ai and open Request Live Demo, the only entry point to the enterprise platform
- Or contact the sales desk for your region directly: North America, EMEA, APAC or LATAM
- Decide the deployment model early, since it shapes everything else: Managed Cloud hosted by H2O.ai, or Hybrid Cloud self-hosted in a private cloud, on-premises or air-gapped
- Scope which products you actually need, from h2oGPTe for generative agents to Driverless AI for AutoML and MLOps for the lifecycle
- Try the conversational experience first through the H2O GenAI App Store or the h2oGPTe iOS application
- Install the open-source line from GitHub to evaluate without a sales cycle: H2O-3, h2oGPT and H2O LLM Studio
- Sign in to an existing tenant through id.cloud.h2o.ai
- Connect your document sources and workplace applications, with Google Drive, SharePoint, Slack and Teams named on the site
- Read the product documentation on docs.h2o.ai and use the Python and R API clients to embed agents in existing workflows
- Train your teams through H2O University certifications and open enterprise support at support.h2o.ai
Pros & Cons
Pros
- Genuine data sovereignty: air-gapped, on-premises or VPC deployment, with no data sharing and no model exfiltration
- A rare convergence of generative and predictive AI in one platform rather than two vendors stitched together
- A mature open-source foundation and published open-weight models, so much of the stack can be evaluated at zero cost
- Traceability designed in: cited RAG, model risk management, guardrails and AutoML explainability
- Solid certifications, including SOC 2 Type II, an unqualified HIPAA/HITECH report and FedRAMP in-process at High impact level
- Named, quantified customer outcomes at Commonwealth Bank of Australia, AT&T and the NIH rather than anonymous testimonials
- Customer content is not used to train H2O.ai models unless explicitly agreed in writing
Cons
- No public pricing whatsoever: not one figure appears anywhere on the site, in text or in the underlying HTML
- No self-service trial or sign-up for the enterprise platform, as every route runs through a sales demo
- No Android application, with only an iOS app available for h2oGPTe
- No Article 27 EU representative and no named Data Protection Officer, despite processing European personal data
- Personal data is processed primarily in the United States, with residency options offered only where available and no published list of regions
- The Trust Center holding the subprocessor list returns an error to direct visitors and requires an access request
- A catalogue of roughly fifteen products makes the platform difficult to navigate without vendor guidance
Pricing & Plans
H2O.ai publishes no pricing. A review of the fourteen pages collected found no tariff, no price figure and no pricing page, in either the rendered text or the underlying HTML, and no pricing link in the navigation or the footer. The enterprise platform is sold exclusively through a sales conversation, opened by the Request Live Demo form or by contacting a regional sales desk. A permanently free route does exist, but it is the open-source line rather than a free tier of the commercial product: H2O-3 is Apache-licensed, and h2oGPT and H2O LLM Studio are published on GitHub at no cost. The privacy policy refers in passing to free-tier, trial and API-based offerings, but no such offer is described on any product page. No lowest paid price point can therefore be stated.
- price on request
- price on request
- Apache-licensed
- free
- price on request
- price on request
Data, GDPR & hosting
A consolidated view of how H2O.ai handles your data.
GDPR overview
Implementation is concrete but incomplete. Section 11.3 of the privacy policy, updated 25 April 2026, addresses EU, EEA and Swiss residents directly: H2O.ai names itself controller, states its lawful bases (contract, legal obligation, legitimate interest and consent where required), and lists rights of access, rectification, erasure, portability, objection, restriction and withdrawal of consent, with the right to complain to a local supervisory authority. Transfers out of the EU rely on Standard Contractual Clauses, the EU-U.S. Data Privacy Framework and the UK and Swiss Addenda. Consent is obtained before non-essential cookies in the EEA and UK. Rights are exercised through privacy@h2o.ai, subject to identity verification. One gap is notable: no Article 27 EU representative is designated and no Data Protection Officer is named anywhere in the legal pages.
Who owns the data?
Where H2O.ai processes personal data on behalf of a customer it acts as a processor, and the relationship is governed by the customer agreement including a DPA; the customer keeps its data, which is deleted when the customer environment terminates unless otherwise agreed. For data H2O.ai collects directly, including from EU, EEA and Swiss users, it is the controller. The significant carve-out concerns derived data: H2O.ai may collect, use and share aggregated, de-identified, anonymised or derived data, including telemetry, usage patterns and performance metrics, for any lawful business purpose, provided it cannot reasonably be used to identify an individual or a customer.
Reuse rights
The terms of use grant only a limited, non-exclusive, non-transferable and revocable licence to access the site for internal, non-commercial purposes. All content, including text, images, software, graphics, video and logos, remains owned by or licensed to H2O.ai, and copying, modifying or distributing any of it requires prior written permission. Two restrictions bite hardest for technical users: no robot, spider or other automated device may be used to scrape or monitor the site, and its content may not be used to develop, train or improve any machine learning or artificial intelligence model without written consent. Any feedback or suggestion a user submits may be used by H2O.ai without restriction or compensation. Content processed through the products themselves is governed separately by the customer agreement, and is not used to train H2O.ai models unless explicitly agreed in writing.
Data retention & training
Hosting summary
Personal data is processed primarily in the United States. The privacy policy of 25 April 2026 says customers can select data residency options where available, but publishes no list of regions, so the choice cannot be assessed in advance. International transfers rely on Standard Contractual Clauses, the EU-U.S. Data Privacy Framework and the UK and Swiss Addenda. Telemetry, logs and metrics may be processed outside the region chosen for customer data, though they are handled separately from customer input. Hosting is ultimately the customer's decision: Managed Cloud is operated by H2O.ai, while Hybrid Cloud is self-hosted in a private cloud, on-premises or in a fully air-gapped environment, in which case the data never reaches H2O.ai at all. Stated safeguards include encryption at rest and in transit, role-based identity and access controls, monitoring, audits, penetration testing and continuous vulnerability scanning, under SOC 2 Type II certification with ISO 27001 in progress. One caution: the site's own IP address resolves to a Fastly anycast CDN node in the United States, which describes website delivery and not where customer data lives.
Things to keep in mind
Risks and trade-offs to weigh before adopting H2O.ai.
- No published price means no budget control before a sales process starts; ask early for total cost of ownership, infrastructure included
- Over-reliance on autonomous agents is a real risk: H2O.ai's own terms warn that outputs may be incomplete or inaccurate and that agentic features can act without human intervention, so teams that stop reviewing outputs lose the very audit trail the product is bought for
- Californian law and exclusive jurisdiction in Santa Clara County govern the terms, a meaningful constraint for a European buyer in a dispute
- Personal data is processed primarily in the United States, with residency offered only where available and no published list of regions
- The absence of an Article 27 EU representative and of a named DPO weakens the practical route for a European data subject to exercise their rights
- The subprocessor list cannot be inspected before contact, since the Trust Center returns an error and requires an access request
- Features may be designated beta, preview or experimental and modified or discontinued at any time, so avoid depending on one without contractual cover
Setup & Integrations
Technical difficulty
Moderate to high, and front-loaded. There is no self-service sign-up: the first step is a sales demo, and an architecture decision follows immediately, between Managed Cloud and self-hosted Hybrid Cloud. The self-hosted route assumes a team able to operate a scalable Kubernetes cluster, which H2O.ai effectively concedes by selling Managed Cloud as the way to avoid exactly that. Once running, several components are deliberately no-code or low-code, so business users face a gentler curve than the infrastructure team. The harder work is choosing among roughly fifteen products. Documentation, H2O University certifications and Python and R API clients support the process.
Deployment
Apps stores
Integrations
Behind H2O.ai
Fundraising
Social
Resources
All the official URLs gathered for verification and reference.
Frequently asked questions
How much does H2O.ai cost?
Can I use it without sending my data to the cloud?
Is my data used to train their models?
What security certifications does H2O.ai hold?
Is a Data Processing Agreement available?
Is there a list of subprocessors?
Is there a mobile application?
Where is my data hosted?
How long is data kept?
Is there a free version?
Should you pick H2O.ai?
H2O.ai is one of the few AI vendors whose central claim is not capability but custody. Everything on the site returns to the same point: the platform runs where your data already is, air-gapped, on-premises or in your own cloud VPC, and neither the data nor the models leave. For a bank, a telecom operator or a federal agency, that is often the only argument that matters, and the results cited behind it are unusually specific for enterprise marketing.
The substance holds up. A 2012 open-source origin, an Apache-licensed library with a claimed two million data science users, published open-weight models, SOC 2 Type II, an unqualified HIPAA/HITECH report and FedRAMP in-process at High impact level are not decoration. Neither is the decision to converge AutoML with generative agents, which spares an organisation from stitching two vendors together, nor the commitment that customer content is not used to train H2O.ai models unless agreed in writing.
The reservations concern transparency and access rather than technology. Not a single price appears anywhere on the site, so no reader can size a budget without entering a sales conversation, and there is no self-service trial of the enterprise product. The Trust Center holding the subprocessor list returns an error to direct visitors. And for a company that processes European personal data and invokes the GDPR at length, the absence of an Article 27 representative and of any named Data Protection Officer is a genuine gap a European buyer should raise early.
The honest summary: a credible, mature platform for regulated organisations that have a technical team and an enterprise budget, and a poor fit for anyone who wants to try before they talk. Evaluating the open-source line first costs nothing and answers most of the technical questions.
- Choosing a selection results in a full page refresh.
- Opens in a new window.