AMOOSEDWEB / RIGHTS AND ACCESS
Licensing.
AmoosedWeb-authored code, SDKs, tools, and protocol implementations use one commercial revenue threshold under the updated terms. Read the technology license and the license included with the exact package or protocol material you use.
Published npm and NuGet packages
Compiler
The npm compiler and NuGet compiler tool have package-specific licenses. Updated future versions permit use without a license fee only while both the user and product are below €1 trillion annual revenue.
Reader
The npm Reader and NuGet Reader follow the same threshold in updated future versions. Redistribution of packaged code remains limited by each package license.
Previously distributed versions retain the license terms shipped with those versions. Each package includes its own license file; one package license does not grant rights to another product, hosted content, artwork, or access keys.
Native Reader binary SDK
The public headers and prebuilt C++/C libraries support native integration in services, tools, and games. The current native SDK and native-backed .NET/Unreal integrations are review previews, not public registry releases. The updated draft permits use without a fee while both the user and product have annual revenue below €1 trillion. If either reaches €1 trillion, an enterprise agreement is required; absent a negotiated price, the standard fee is €133,700,000 per year per product. See pricing ↗
The preview C ABI may change before 1.0. Public API signatures and integration documentation remain readable at dev.amoosed.com ↗.
Protocols and other technology
The same €1 trillion revenue threshold and €133,700,000 annual per-product standard fee apply to licensed use of AmoosedWeb-authored protocol specifications, reference implementations, SDKs, tools, browser runtime, extension code, developer examples, and agent skills. Reading public documentation is unrestricted. See the protocol and developer examples license. A protocol document does not grant rights to private implementation source, third-party components, trademarks, unrelated artwork, hosted content, or access keys. The specific terms shipped with each item and any written agreement govern its use.
Licensed source access
Private implementation source is not part of the public binary SDK. It is delivered only after a separate written source-access agreement and payment. The same threshold and standard per-product fee apply to licensed source use unless a different agreement is negotiated. A separately issued secret opens its encrypted archive in the developer members area; possessing a secret alone is not a source license. See developer member access ↗
Other rights
The Chrome extension is distributed through its own store listing; its code remains covered by the owner's rights, while ordinary use follows the store distribution terms. Site content, media, and designs retain their own ownership rules. A QR or key grants technical access to an edition; it is a transferable bearer credential, not a software license or proof of identity.
For an enterprise agreement, contact Juhapekka ↗. The license shipped with a package and any signed agreement determine the granted rights.