You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today H2O.ai launched H2O-3 Secure, a commercially supported tier of H2O-3. We want to be direct with the community about what this means for H2O-3 OSS.
What stays the same
H2O-3 OSS remains free and Apache 2.0-licensed
All current and future algorithms remain open and free to use
Python and R clients still available in Pypi and CRAN
The H2O-3 OSS codebase remains on GitHub at github.com/h2oai/h2o-3
All our math is open source and remains free for the community as per the original founding vision to democratize AI and use AI for Good.
Community channels, documentation, and contribution paths continue to operate
What changes in upcoming H2O-3 releases
Beginning with H2O-3 Version 3.46.0.12, the following capabilities will transition to the H2O-3 Secure software release:
Production MOJO model scoring for Hadoop, Spark, Teradata, Oracle. (But non-commercial licenses are available for FREE)
Hadoop and Kubernetes enterprise packages. OSS users can still create their own.
Telemetry is being added to H2O-3. It is opt-in and off by default, details below.
Why we're making this change
The same data scientists who built on H2O-3 are now being asked to prove production controls: vulnerability management, incident response, and vendor risk documentation. What they need is not a different platform. It is the one they already run, holding up at scale, standing up to an audit (SOC 2, ISO 27001, ISO 42001), and backed by someone they can call at 2am.
That is H2O-3 Secure. API-compatible with the open-source version, so there is nothing to rewrite and nothing to port. The same code, the same pipelines, now with prioritized CVE patching, and 24x7 support coverage.
Telemetry
3.46.0.12 also adds telemetry to H2O-3. Calling that out here rather than letting you find it in a diff:
It is opt-in and off by default. H2O-3 sends nothing unless you turn it on.
We honor DO_NOT_TRACK=1 and follow the convention documented at donottrack.sh.
Turn it on or off yourself with h2o.telemetry_enable() / h2o.telemetry_disable(), or via config — see the telemetry docs.
We do not collect your code, your data, column names, hostnames, or file paths.
The complete list of what is and isn't collected is in the H2O-3 README, in the repo, versioned with the release.
What if you're running H2O-3 OSS in production today
There is no change, you can continue running your current OSS deployments. They won't stop working. But we recommend you try H2O-3 Secure, which is designed for production use cases. Schedule a Production Review at h2o.ai/h2o-3/oss-vs-secure, or request a trial license at enterprise@h2o.ai .
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Today H2O.ai launched H2O-3 Secure, a commercially supported tier of H2O-3. We want to be direct with the community about what this means for H2O-3 OSS.
What stays the same
What changes in upcoming H2O-3 releases
Beginning with H2O-3 Version 3.46.0.12, the following capabilities will transition to the H2O-3 Secure software release:
Why we're making this change
The same data scientists who built on H2O-3 are now being asked to prove production controls: vulnerability management, incident response, and vendor risk documentation. What they need is not a different platform. It is the one they already run, holding up at scale, standing up to an audit (SOC 2, ISO 27001, ISO 42001), and backed by someone they can call at 2am.
That is H2O-3 Secure. API-compatible with the open-source version, so there is nothing to rewrite and nothing to port. The same code, the same pipelines, now with prioritized CVE patching, and 24x7 support coverage.
Telemetry
3.46.0.12 also adds telemetry to H2O-3. Calling that out here rather than letting you find it in a diff:
DO_NOT_TRACK=1and follow the convention documented at donottrack.sh.h2o.telemetry_enable()/h2o.telemetry_disable(), or via config — see the telemetry docs.What if you're running H2O-3 OSS in production today
There is no change, you can continue running your current OSS deployments. They won't stop working. But we recommend you try H2O-3 Secure, which is designed for production use cases. Schedule a Production Review at h2o.ai/h2o-3/oss-vs-secure, or request a trial license at enterprise@h2o.ai .
Learn more: https://h2o.ai/blog/2026/changes-coming-to-h2o-3-open-source
All reactions