Commercial license

Embedding the runtime in a product starts here.

When the sound-to-space runtime ships inside something — a distributed product, a hosted service, an OEM integration, a fixed installation — the commercial license is the line where private study becomes commercial deployment.

Path /commercial-license
  1. Required for distributed products, hosted services, and OEM or installation use.
  2. Available in studio and enterprise-oriented tiers.
  3. Commercial inquiries go directly to the licensor.

When you need a commercial license

The commercial license applies when you go beyond personal, non-commercial use and move into distribution or service delivery. Common examples include:

  • Shipping an application, plugin, tool, or service built on or substantially derived from the engine
  • Running a hosted or managed service powered by the engine
  • Embedding the engine in hardware, installations, or OEM workflows
  • Any other use that moves from private study into product or service delivery

What remains free

Personal use, academic research, education, and contribution to this repository remain available under the engine’s PolyForm Strict terms. The commercial license is not required for private, non-commercial study and experimentation.

Commercial tiers

Baryon currently offers two commercial licensing paths:

  • Independent / Small Studio for individuals and smaller studios
  • Enterprise / OEM for larger organizations, negotiated integrations, hardware bundles, and installation use

Attribution

Products distributed under a commercial license must include visible attribution to the Baryon engine and the baryon.live property.

Contact

For licensing discussions, email licensing@baryon.live with a short description of your intended use case. That makes it possible to route inquiries quickly and keep the public terms aligned with the actual delivery model.