Guides
v1.0
Guides
  1. operations

Licensing

BlazeRules is source-available under FSL-1.1-ALv2, with commercial licensing for managed-service, SaaS, OEM, and enterprise use.

BlazeRules is source-available under the Functional Source License 1.1, Apache
2.0 Future License (FSL-1.1-ALv2).

The public repository is the local data plane: the engine, Python/C++ bindings,
IO helpers, local agent, local dashboard, examples, and deployment templates.
Hosted governance and enterprise control-plane features may be commercially
licensed or proprietary.

📘

Short version

You can use BlazeRules for permitted purposes under the FSL. Offering
BlazeRules or substantially similar functionality as a commercial hosted
service, managed service, SaaS, API, platform, or competing product requires a
commercial license.

License Files

FilePurpose
LICENSEFull FSL-1.1-ALv2 license text.
COMMERCIAL.mdPractical summary of commercial/OEM/BYOC licensing.
TRADEMARKS.mdBlazeRules name and mark usage policy.
THIRD_PARTY_NOTICES.mdBest-effort third-party dependency notice summary.
CONTRIBUTING.mdContribution policy, CLA/DCO expectations, and licensing of contributions.

Commercial License Triggers

Contact [email protected] before using BlazeRules to:

  • offer BlazeRules or substantially similar functionality as a commercial
    hosted service, managed service, SaaS, API, or platform;
  • embed BlazeRules into a commercial product that competes with BlazeRules or
    exposes substantially similar rule-engine functionality to third parties;
  • redistribute BlazeRules as part of an OEM product or commercial platform;
  • sell hosted rule authoring, rule execution, governance, or decisioning
    services built around BlazeRules;
  • receive enterprise support, certified builds, indemnity, custom licensing
    terms, or private/commercial features.

BYOC And BYOL

BYOC means the BlazeRules data plane runs in the customer's cloud, VPC,
Kubernetes cluster, or on-prem environment. Raw events do not need to leave the
customer's infrastructure.

BYOL means an enterprise customer brings a commercial license key or
commercial agreement to a self-hosted/BYOC deployment. BYOL is not the public
repository license; it is an enterprise licensing and deployment model.

Public Data Plane vs Commercial Control Plane

The public/source-available data plane includes:

  • local rule engine and SDKs;
  • YAML rules, operators, schema inference, windows, lookups, ONNX scores, and
    vector similarity;
  • JSON, Arrow, Arrow IPC, Avro, Protobuf, Kafka, file, S3, and CDC helpers;
  • local agent, local dashboard, local decision logs, DLQ, metrics, and hot
    reload.

Commercial or SaaS control-plane features may include:

  • hosted rule editor and schema-aware validation;
  • approval workflows, comments, RBAC/SSO, and audit logs;
  • centralized rule, lookup, and model registry;
  • signed releases and deployment gates;
  • fleet management and remote hot reload orchestration;
  • backtest orchestration and challenger/shadow-rule comparison;
  • enterprise connectors, certified builds, support, and SLAs.

Future Apache License

Each version made available under FSL-1.1-ALv2 receives an Apache License 2.0
grant that becomes effective two years after that specific version is made
available. The future license grant is version-specific; newer versions have
their own two-year timelines.

This page is a practical summary. The license text in LICENSE controls.