The pricing model
Baryon has three clear use boundaries: public engine access for study, the desktop product for performance use, and a commercial license for anything that ships, hosts, embeds, or deploys to a client. Keeping those boundaries explicit keeps the source license honest and the commercial path predictable.
Personal and non-commercial engine use
The engine is source-available for personal, educational, research, and other non-commercial use under PolyForm Strict. This path is for studying the runtime, modifying it privately, and contributing improvements back.
Desktop product path
The desktop app is the paid path for performance use. It is where the runtime becomes a usable instrument: stage output, multi-surface operation, session persistence, performance controls, and verified host-routing paths as desktop releases support them.
Commercial license path
A separate commercial license is required when Baryon becomes part of something you ship, sell, host, embed, or install for a client — distributed products, hosted services, OEM embedding, fixed installations, and similar deployments.
How to choose
- Public source path — you are studying the runtime or experimenting privately.
- Desktop product path — you want Baryon as an instrument or performance source in your own work.
- Commercial license path — Baryon becomes part of a distributed, hosted, or deployed product.