Licensing
Hermes is open source under the MIT License.
What You Can Do
| Use Case | Allowed? |
|---|---|
| Personal, hobby and educational projects | Yes |
| Open source projects | Yes |
| Commercial products, at any company size | Yes |
| Internal tools | Yes |
| Modifying Hermes and redistributing your changes | Yes |
There is no license key, no fee, no revenue threshold, and no limit on applications, seats or end users.
The one condition is the MIT License's own: include its copyright notice and license text wherever you distribute Hermes. That covers an application that bundles Hermes, where a third-party notices file is the usual place for it.
Upgrading From a Licensed Release
Earlier releases were source-available under the Elastic License 2.0 and read an optional license key at startup. Current releases contain no license check. When you upgrade:
- Remove any call to
WithLicenseKey(...)onHermesBlazorAppBuilder. The method no longer exists. - Delete the
HERMES_LICENSEenvironment variable and theHermes:Licenseconfiguration value. Neither is read any more.
Frequently Asked Questions
Can I ship a commercial application built on Hermes?
Yes. The MIT License allows commercial use with no fee, whatever your organization's size or revenue.
Can I use Hermes in a SaaS product?
Yes. The MIT License places no restriction on how Hermes is used.
Contact
For licensing questions, including a license bought for an earlier release: support@mythetech.com
