Bread

Personal non-business use and genuine evaluation are always free. Evaluation has no countdown or commitment to buy. Routine work with adopted software, including product development, follows business-use rules.

Business use is free below US$1m in annual consolidated revenue. Count the ultimate controlling parent and its controlled entities for the last completed financial year. Financing, investment proceeds, valuation, and headcount are excluded. With no completed year, count revenue since formation without annualizing it.

Assess eligibility at first operational use and annually, or earlier when a control change alters the group. Losing eligibility in good faith allows 90 days to obtain permission or stop uncovered operational use. Free business eligibility does not create permanent paid-up rights. Read the business eligibility rules.

Your company group keeps permanent rights to covered releases. A purchase covers existing official releases and those first published during an update period of at least twelve calendar months, excluding material outside the Licensor’s authority identified before purchase. There are no seat, machine, application, or execution counts.

Nonrenewal stops coverage of later official releases. Covered releases and their permitted modifications remain usable, and company growth does not reprice those acquired rights. No particular update or maintenance schedule is promised.

Hosted access follows the service period. Exporting software to operate independently requires your own applicable permission. Read the company purchase terms.

You may share or sell Bread-licensed software without royalties. There is no publisher coverage tier, sales reporting, or product approval. Include source and notices, identify the software and official purchasing channel, and explain that recipients need their own applicable permission. An existing purchase may already cover those releases across another application.

A supplier can arrange a purchase for an actual customer. With the customer's authorization, name its company group in an ordinary upstream purchase. The upstream authorized seller accepts the order and issues confirmation directly to the customer. Coverage begins with upstream payment or an expressly accepted credit order identifying who owes payment. Payment to the supplier alone does not create permission; the supplier's receipt or company license cannot replace that entitlement.

Your independently operated hosted service uses your permission. Customers need no separate permission merely to access it, including free plans, dedicated tenants, and services running customer-authored programs or workflows. A browser client supplied for that provider-controlled service is included, even when it computes locally.

A customer's own deployment uses the customer's permission. This includes a customer-controlled installation administered by a supplier. Responsibility follows who controls and commissions the deployment and bears responsibility for its operation. Generic infrastructure rental supplies no software entitlement.

Independent applications and separately licensed components keep their own terms. Read the distribution rules and hosting rules.

Share the Bread-licensed code you distribute, including your changes. Give recipients source code, build instructions, and license notices they can keep. Separate files containing only your own application code can stay private. Using or hosting the software privately does not, by itself, require publishing changes.

Sharing a modified version does not add another license fee. People using your modified version follow the original project’s license and payment rules. You cannot charge a second permission fee for your changes, but you can charge for copies, support, and independently licensed additions. New versions from the original project still need the right coverage.

Read the source-code and patent terms.