BetterCorp/BetterFrame
1
0
Fork 0
mirror of https://github.com/BetterCorp/BetterFrame.git synced 2026-05-26 17:56:34 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 10
BetterFrame/LICENSE-COMMERCIAL.md
Mitchell R 70ecdd1b03 docs: dual-license declaration + vendored AGPL-3.0 text 
LICENSE.md states AGPL-3.0-only OR Commercial dual license (matches the
SPDX expression in every package.json + Cargo.toml). LICENSE-AGPL.txt
is the canonical FSF text. LICENSE-COMMERCIAL.md covers when a
commercial license is required and how to obtain one.
2026-05-15 04:47:46 +02:00

2.1 KiB
Raw Blame History

BetterFrame Commercial Licence

This file describes how to obtain a commercial licence for BetterFrame as an alternative to AGPL-3.0-only (see LICENSE.md).

When you need this

You probably need a commercial licence if any of the following apply:

  • You ship BetterFrame as part of a closed-source product (distributed binary, appliance, embedded system) and do not want to release your modifications under AGPL.
  • You host BetterFrame as a SaaS for paying customers and do not want to be required to disclose modifications under AGPL §13's network-use clause.
  • You combine BetterFrame source with proprietary code that you cannot re-license under AGPL.
  • You require a warranty, indemnity, or support SLA — AGPL is offered "as-is".

Internal use within a single organisation where end-users are employees typically does not require a commercial licence, but consult your counsel about AGPL §13 in your jurisdiction.

How to obtain

Commercial licences are issued per-deployment by BetterCorp. They cover:

  • Removal of AGPL source-disclosure obligations for the licenced deployment(s).
  • A defined number of devices/seats/instances.
  • Optional: support tier, SLA, warranty, indemnity, custom contract terms.

To enquire:

Include in your enquiry:

  • Intended deployment shape (single-site / multi-tenant SaaS / OEM / etc.)
  • Approximate number of kiosks / servers / customers
  • Whether you need source-redistribution rights, warranty, or support
  • Target start date

What you do not need a commercial licence for

  • Trying BetterFrame in development, evaluation, or testing.
  • Contributing patches upstream — your contributions remain under AGPL.
  • Internal IT use inside one organisation, as discussed above.
  • Self-hosting a personal instance for non-commercial use.

When in doubt: open an issue and ask. We'd rather clarify than chase.