# Commercial licensing

Froam is released under [FSL-1.1-MIT](../LICENSE) — source-available, not
OSI-approved open source. Most people never need to buy anything. This page
exists so you can tell in about a minute which group you are in.

---

## You do not need to pay us

The licence already grants these, at no cost:

- **Using Froam inside your own business.** Your team, your sites, your client
  work, commercial or not. "Internal use and access" is an explicitly Permitted
  Purpose.
- **Professional services.** Agencies and freelancers may use Froam to deliver
  work for clients, provided the client is also using Froam under these terms.
- **Non-commercial education and research.**
- **Modifying it.** Fork it, patch it, build on it — the same terms carry over
  to your copies.

If that describes you, you are done. Use it, and tell us what breaks.

Every release also converts to the **MIT licence two years after that version
ships**. Froam 8.3.0 became available in September 2026, so it becomes MIT in
September 2028. That is a commitment in the licence text, not a promise on a
webpage.

---

## You do need a commercial licence

**1. You want to put Froam inside a product you sell.**

The one thing FSL withholds is what it calls a Competing Use: making Froam
available to others in a commercial product or service that substitutes for
Froam, substitutes for something we already offer using it, or provides
substantially similar functionality.

In practice that means a commercial licence is required if you are building a
website builder, CMS, page editor, design tool, or hosting platform and want to
ship Froam's editor as part of what your customers get.

**2. Your organisation cannot approve a non-OSI licence.**

Some companies run a blanket "OSI-approved licences only" policy. You are
permitted to use Froam under FSL, but your own rules will not let you. A
commercial licence replaces FSL for your organisation and removes the blocker.

If you are unsure which side of the line you fall on, ask. Describing what you
are building takes one email and costs nothing.

---

## What a commercial licence grants

- The right to use Froam for a Competing Use, including embedding it in a
  product or service you sell.
- Standard commercial terms in place of FSL, suitable for procurement review.
- A named point of contact for questions about the software.

It does not include support obligations, an uptime commitment, or a
custom-development entitlement unless those are agreed separately in writing.

---

## Pricing

| What you are doing | Price |
| --- | --- |
| Using Froam in your own business, or for client work | **Free** under FSL — nothing to buy |
| Individual commercial licence | **$5 per month** |
| Embedding Froam in a product you sell (OEM / redistribution) | **Quote on request** |
| Replacing FSL for an organisation that cannot accept it | **Quote on request** |

Embedding and organisation-wide licences are quoted per product and per company
size, because a two-person studio and a funded platform are not the same deal.
Tell us what you are building and we will come back with a number.

---

## Getting a licence

Email **ahmadnuhu14@gmail.com** with:

1. Your company name and where you are based.
2. What you are building, and how Froam would sit inside it.
3. Roughly how many people or customers it would reach.

Short is fine. Three sentences is enough to start.

---

## Notes

This page summarises the offer in plain language. It is not legal advice and it
is not itself a contract — a commercial licence takes effect through a signed
agreement, and that agreement governs if the two ever disagree. The
authoritative terms for the free licence are in [LICENSE](../LICENSE); read it
rather than relying on this summary.