Skip to main content
Hivenet Router is licensed under the Apache License, Version 2.0. The license allows broad use, modification, and redistribution of the project, including commercial use, provided that its conditions are followed.
This page is a practical summary, not legal advice.The repository’s root LICENSE file is the authoritative text. When this summary and the license differ, the license controls.

Read the canonical license

Review the complete Apache License 2.0 terms distributed with Hivenet Router.

Apache License 2.0

Read the standard license text and supporting information from the Apache Software Foundation.

​
At a glance

Subject to the license conditions, you may: The license does not require you to:
  • publish private modifications
  • distribute your source code merely because you use Hivenet Router
  • license your complete application under Apache 2.0
  • make source code available solely because users access a hosted service over a network
Redistribution creates additional obligations. The current repository license includes:
Keep applicable copyright and attribution notices when redistributing Hivenet Router or a derivative work. You may add your own copyright statement for original modifications you create. For example, a derivative project may retain the original notice and add a separate notice identifying the copyright owner of its modifications. Each contributor grants a broad copyright license covering their contribution. This includes permission to:
  • reproduce the work
  • modify it
  • prepare derivative works
  • display or perform it publicly
  • sublicense it
  • distribute source or object forms
The grant is:
  • worldwide
  • non-exclusive
  • royalty-free
  • perpetual
  • generally irrevocable, subject to the license terms
This is what permits individuals and organizations to build, operate, modify, and redistribute Hivenet Router without negotiating a separate copyright license with every contributor.

​
Patent license

Apache License 2.0 also includes an express patent grant. Each contributor grants a license to patent claims that:
  • the contributor is able to license
  • would necessarily be infringed by that contributor’s contribution alone
  • or would necessarily be infringed by combining the contribution with the project it was submitted to
This is not a license to every patent a contributor owns. It covers the patent claims necessary to use the relevant contribution as part of the work.

​
Patent-litigation termination

The patent grant contains a termination condition. When you initiate patent litigation alleging that Hivenet Router or a contribution incorporated into it infringes a patent, the patent licenses granted to you under Apache License 2.0 for that work terminate when the litigation is filed. This can also apply when the allegation is made through a cross-claim or counterclaim.
The patent grant is not a patent warranty, indemnity, or guarantee that no third-party patent claim can exist.

​
Redistribution requirements

You may distribute Hivenet Router or a derivative work:
  • with or without modifications
  • in source or compiled form
  • as a standalone project
  • as part of a larger product
When you distribute it, follow the conditions in Section 4 of the license.

​
Include the license

Give recipients a copy of the Apache License 2.0. For a source distribution, retain the repository’s:
file. For a binary, package, appliance, or container distribution, include the license in an appropriate location such as:
  • the distributed archive
  • a licenses directory
  • accompanying documentation
  • an application’s legal-notices view
  • another location recipients can reasonably access
A link alone may not satisfy every distribution context. Include an actual copy of the license with the distributed work.

​
Mark modified files

Files you modify must carry a prominent notice stating that they were changed. The license does not prescribe one exact notice format. A notice can identify:
  • that the file has been modified
  • the organization or person making the modification
  • the date or version of the change
For example:
A general changelog can provide useful context, but it should not replace file-level notices when the license requires modified files themselves to identify that they changed.

​
Retain existing notices

When distributing source-form derivative works, retain relevant:
  • copyright notices
  • patent notices
  • trademark notices
  • attribution notices
You may remove a notice that does not apply to any part of the derivative work you are distributing. Do not remove upstream notices solely to make the project appear to have a different origin.

​
NOTICE files

Apache License 2.0 contains additional requirements when the original work includes a:
file. The current Hivenet Router repository does not include one. That means the license’s NOTICE-file redistribution condition does not currently add another Hivenet Router-specific attribution file.
Check the exact release or commit you redistribute.If a future Hivenet Router version includes a NOTICE file, its relevant attribution notices must be carried into distributed derivative works as described by the license.
The absence of a Hivenet Router NOTICE file does not mean that third-party dependencies have no licensing or attribution requirements.

​
Apply different terms to your own work

You may add your own copyright statement to modifications you create. You may also offer:
  • additional terms for your modifications
  • different terms for a larger derivative work
  • commercial licensing for your own components
  • paid support, warranty, or indemnity
This is permitted only when your use and distribution of the original Apache-licensed work still complies with Apache License 2.0. You cannot remove the upstream license obligations by placing the complete derivative work under another license. For example, a proprietary application may include Hivenet Router, but its distribution must still include the Apache License 2.0 terms and applicable notices for the Hivenet Router portion.

​
Common use cases

​
Run Hivenet Router internally

You may deploy an original or modified version inside your organization. The Apache redistribution conditions are generally relevant when copies are distributed to other recipients. Internal use does not create a requirement to publish your modifications. Keep the canonical license and attribution in your internal source repository so they remain attached to the work.

​
Offer a hosted service

You may operate Hivenet Router as part of a hosted or managed service. Apache License 2.0 does not contain a network-use source-disclosure condition. Allowing customers to access a service powered by modified Hivenet Router does not, by itself, require you to publish those modifications. Other obligations may apply when you also distribute:
  • an on-premises package
  • a downloadable appliance
  • an agent binary
  • a container image
  • source code
  • another copy of the software

​
Distribute a modified source fork

When distributing a source fork:
  1. Include the Apache License 2.0.
  2. Retain relevant upstream notices.
  3. Mark modified files.
  4. Include any applicable NOTICE file from the version you forked.
  5. Identify your own changes and copyright where appropriate.
  6. Review the licenses of bundled third-party components.
You may give the fork a different project name, but do not imply that it is the official Hivenet Router project or is endorsed by Hivenet.

​
Distribute a binary or container

When distributing a compiled router, agent binary, appliance, or container:
  1. Include a readable copy of the license.
  2. Preserve applicable attribution and legal notices.
  3. Make the notices accessible to recipients.
  4. Include an applicable NOTICE file if the distributed version has one.
  5. Review third-party runtime components and dependencies separately.
A container image does not remove the redistribution obligations merely because its files are delivered through a registry rather than a downloadable archive.

​
Include Hivenet Router in a proprietary product

Apache License 2.0 is permissive and does not require the complete combined product to use the same license. You may combine Hivenet Router with proprietary software, provided that you continue to comply with the Apache conditions for the Hivenet Router code and modifications derived from it. The license does not grant rights to third-party code merely because it is packaged alongside Hivenet Router.

​
Third-party dependencies

Hivenet Router depends on third-party Go packages, container images, infrastructure services, and development tools. Those components remain subject to their own licenses. The root Hivenet Router LICENSE file does not automatically relicense:
  • Go module dependencies
  • inference engines
  • container base images
  • Prometheus, Grafana, Loki, or Tempo
  • models and model weights
  • SDKs and client applications
  • operating-system packages
Before redistributing a complete product or image, review the license obligations for every included component. This is particularly important for:
  • required attribution
  • copyright notices
  • copyleft conditions
  • source-offer requirements
  • model-use restrictions
  • patent terms
  • trademark restrictions
A model served through Hivenet Router can have a license that is substantially more restrictive than the Hivenet Router software license.Review the license of every model and dataset independently.

​
Trademarks and project names

Apache License 2.0 does not grant a general right to use a licensor’s:
  • trade names
  • trademarks
  • service marks
  • product names
You may use names such as Hivenet Router and Hivenet where reasonably necessary to describe the origin of the software. For example:
The license does not permit branding a derivative product in a way that suggests it is:
  • the official Hivenet Router distribution
  • produced by Hivenet
  • approved or endorsed by Hivenet
unless you have separate permission. Choose a distinct name and visual identity for a separately distributed fork.

​
Contributions

Unless a contributor explicitly states otherwise, a contribution intentionally submitted for inclusion in Hivenet Router is licensed under Apache License 2.0. This includes work submitted through project-controlled channels for inclusion in the project, such as:
  • pull requests
  • commits
  • patches
  • issue discussions containing proposed project material
  • other communications intentionally submitted as contributions
A communication conspicuously marked as:
is excluded from the license’s definition of a contribution. A separate contributor or license agreement can also establish different submission terms when one exists. The repository does not currently describe a separate contributor license agreement. Contributions accepted through the normal workflow use the project’s Apache License 2.0 terms. See Contributing before submitting work.

​
No warranty

Hivenet Router is provided on an:
basis. Unless required by law or separately agreed in writing, the license provides no warranty or condition of:
  • title
  • non-infringement
  • merchantability
  • fitness for a particular purpose
You are responsible for determining whether Hivenet Router is appropriate for your deployment and for assessing the risks associated with using, modifying, or redistributing it. The open-source license does not promise:
  • technical support
  • service availability
  • compatibility
  • security fixes
  • maintenance periods
  • response times
  • a service-level agreement
Any separate commercial service or written support agreement is governed by its own terms.

​
Limitation of liability

The license limits contributor liability for damages arising from use of, or inability to use, the software, to the extent permitted by applicable law. The limitation covers categories such as:
  • direct or indirect damages
  • incidental or consequential damages
  • lost goodwill
  • work stoppage
  • computer failure
  • commercial loss
Applicable law or a separate written agreement may affect how those limitations operate in a particular jurisdiction.

​
Offer your own warranty or support

A distributor may offer and charge for:
  • support
  • maintenance
  • warranty
  • indemnity
  • other liability obligations
When doing so, the distributor acts:
  • on its own behalf
  • at its own responsibility
  • not on behalf of the original contributors
The distributor must protect the original contributors from liabilities created by those additional commitments, as required by the license.

​
Redistribution checklist

Before distributing Hivenet Router or a derivative work:
  • identify the exact release or commit being distributed
  • include a copy of Apache License 2.0
  • retain applicable copyright and attribution notices
  • mark modified files
  • check whether that version contains a NOTICE file
  • include relevant NOTICE content when required
  • review every third-party dependency and bundled component
  • review model and model-weight licenses separately
  • avoid implying official Hivenet endorsement
  • document your own modifications and terms clearly
  • obtain legal advice when the distribution or product raises material licensing questions

​
Canonical text

This page deliberately does not reproduce the complete license. Read and retain the canonical file:
in the repository root.

Canonical license

Read and retain the complete Apache License 2.0 text distributed with Hivenet Router.

Contributing

Review how submitted contributions are licensed and accepted.

Code of conduct

Review the standards applying to participation in the project.

GitHub repository

Browse the source code and canonical project files.