Skip to content

License and Commercial Use

Jump to bottom
Antonios Voulvoulis edited this page Apr 3, 2026 · 1 revision

License and Commercial Use

Purpose: Explains the NFTBan license model, what MPL-2.0 requires, and how commercial and fork usage works. Last verified: v1.68.0

License Model

NFTBan uses a split-license model:

Component License Scope
Core MPL-2.0 CLI, daemon, nftables schema, detection modules, health checks, CI tooling
Pro NFTBan Pro Commercial License pro.nftban.com portal, fleet telemetry, centralized management
Brand All rights reserved Name, logos, wordmark, brand assets in /branding

The Core and Pro components are architecturally separated. They communicate via defined interfaces (CLI commands, IPC socket, HTTP API).

MPL-2.0 Explained

The Mozilla Public License 2.0 is a file-level copyleft license. This means:

You May

  • Use NFTBan for any purpose (personal, commercial, government, educational)
  • Modify NFTBan source files
  • Distribute NFTBan in original or modified form
  • Combine NFTBan with proprietary code in the same project
  • Build commercial products or services that use NFTBan internally

You Must

  • Keep the MPL-2.0 license header in all MPL-licensed files
  • Keep the copyright notice intact
  • If you modify an MPL-licensed file, make the modified source of that file available under MPL-2.0

You Do Not Need To

  • Open-source your own separate modules, scripts, or applications that call NFTBan
  • Open-source proprietary files in the same project that are not themselves MPL-licensed
  • Disclose your entire codebase because you use NFTBan

Key Distinction From Other Licenses

  • Unlike GPL, MPL copyleft applies per-file, not per-project. You can mix MPL and proprietary files.
  • Unlike MIT/BSD, MPL requires that modifications to the licensed files are shared. You cannot take an MPL file, modify it, and distribute it without source.
  • Unlike AGPL, MPL has no network-use clause. Running modified NFTBan on a server does not trigger source disclosure requirements.

Commercial Use

Allowed Without Permission

  • Deploying NFTBan on servers you operate
  • Using NFTBan as part of infrastructure you sell or manage
  • Integrating NFTBan into a commercial product (subject to MPL-2.0 obligations for modified files)
  • Offering IT services where NFTBan is one of many tools used

Requires Written Permission

  • Selling a product or service named "NFTBan" (trademark restriction)
  • Distributing a modified version under the NFTBan name
  • Using the NFTBan name or logo in advertising

Contact legal@nftban.com for commercial licensing or trademark inquiries.

Fork Policy

Forking is encouraged under MPL-2.0. Forks must:

  1. Rename the project — do not use "NFTBan", "nftban", or "NFTBAN" in the fork name, binaries, packages, or domains
  2. Remove NFTBan logos and brand assets
  3. Keep MPL-2.0 license headers and copyright notices in all MPL-licensed files
  4. Publish source for any modified MPL-licensed files

Forks may describe themselves as "based on NFTBan" or "a fork of NFTBan" for factual attribution.

See TRADEMARK.md for the complete trademark policy.

Architecture Boundary

+--------------------------------------------------+
|                   MPL-2.0 Core                   |
|                                                  |
|  CLI (Bash)    Daemon (Go)    nftables Schema    |
|  Detection     Health         Modules            |
|  IPC           Metrics Export Packaging           |
+--------------------------------------------------+
        |              |              |
     CLI cmd     IPC socket     HTTP API
        |              |              |
+--------------------------------------------------+
|            Separate (Not MPL-2.0)                |
|                                                  |
|  pro.nftban.com    Fleet Telemetry    AI/ML      |
|  Centralized Mgmt  Analytics          Future     |
+--------------------------------------------------+

The boundary between Core and Pro is enforced at the interface level. Core components do not import or depend on Pro components.

Source Files

Copyright 2024-2026 NFTBAN Project / Antonios Voulvoulis.

NFTBan Wiki

Getting Started

Architecture

Modules

Operator Reference

Verification & Trust

Reference

Legal

Clone this wiki locally