HomeLicense

License

Last updated: March 27, 2026

Privacy PolicyTerms of ServiceLicense
Summary: hyperpush core is AGPL-3.0 — you can use, modify, and self-host it freely, but derivatives must also be open source. SDKs are MIT-licensed for maximum flexibility. Commercial licensing is available for proprietary use cases.

1Overview

hyperpush uses a dual-license model designed to keep the core platform open source while giving SDK users maximum freedom. This approach ensures the platform stays open and community-driven while allowing developers to integrate hyperpush into any project without license concerns.

Core Platform

AGPL-3.0

Server, dashboard, API, ingestion pipeline, bug board, and token economics engine.

Client SDKs

MIT

JavaScript/TypeScript, Rust, Python, Node.js, and Mesh SDKs.

2AGPL-3.0 — Core Platform

The hyperpush core platform is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0). This means:

You Can

  • Use hyperpush for any purpose, including commercial use
  • Self-host hyperpush on your own infrastructure
  • Modify the source code to suit your needs
  • Distribute copies of hyperpush
  • Offer hyperpush as a hosted service to others

You Must

  • Disclose the source code of any modifications you make to hyperpush core
  • License derivative works under AGPL-3.0
  • Provide source code access to users who interact with your modified version over a network
  • Preserve copyright and license notices in all copies
  • Document changes you make to the original code

Why AGPL-3.0?

The AGPL ensures that improvements to the core platform benefit the entire community. If someone builds a competing hosted service on hyperpush, they must contribute their improvements back. This creates a level playing field and keeps the ecosystem healthy.

3MIT — Client SDKs

All hyperpush client SDKs are licensed under the MIT License. This is intentionally permissive — we want zero friction for developers integrating hyperpush into their applications.

What This Means

  • Use the SDKs in any project — open source or proprietary
  • No obligation to disclose your application's source code
  • Modify the SDKs as needed with no copyleft requirements
  • Bundle the SDKs in commercial software without restrictions
  • The only requirement is preserving the MIT license notice in copies

Covered Packages

@hyperpush/sdkMIT
@hyperpush/nodeMIT
hyperpush-rsMIT
hyperpush-pythonMIT
hyperpush-meshMIT

4Commercial Licensing

If the AGPL-3.0 license doesn't work for your use case — for example, if you want to embed hyperpush core in a proprietary product without open-sourcing your changes — we offer commercial licenses.

Commercial License Includes

  • Right to modify and distribute hyperpush core without AGPL obligations
  • No requirement to disclose source code of derivative works
  • Priority support and SLA guarantees
  • Custom feature development (case by case)

Contact licensing@hyperpush.dev to discuss commercial licensing.

5Contributor License Agreement

Contributors to the hyperpush repository agree to the following:

  • You grant hyperpush a perpetual, worldwide, non-exclusive license to use your contributions
  • You certify that you have the right to submit the contribution
  • You agree that your contribution may be relicensed under the current project licenses
  • Your contribution remains attributed to you in the project history

We use a lightweight CLA — no legal paperwork required. By opening a pull request, you agree to these terms. This is standard practice for dual-licensed open-source projects and ensures we can maintain the SDK under MIT while keeping the core under AGPL.

6Third-Party Components

hyperpush includes third-party open-source components. Each component retains its original license. A complete list of dependencies and their licenses is available in the THIRD_PARTY_LICENSES file in the repository root.

7Trademark

The hyperpush name, logo, and brand identity are trademarks of hyperpush. The open-source licenses do not grant permission to use these trademarks. Specifically:

  • You may state that your product is "powered by hyperpush" or "compatible with hyperpush"
  • You may not use the hyperpush name or logo to imply official endorsement
  • Forks and derivatives must use a different name and brand
  • The hyperpush logo may be used in documentation and blog posts referencing the project

8Full License Texts

The complete license texts are available in the repository:

  • AGPL-3.0: /LICENSE in the main repository under github.com/hyperpush-org
  • MIT: /LICENSE in each SDK repository under github.com/hyperpush-org

For questions about licensing, contact licensing@hyperpush.dev.