# Pricing & commercial license for @imqueue

Source: https://imqueue.com/pricing/

A commercial license lets you ship @imqueue inside a **closed-source product**.
The open-source edition is GPL-3.0: convey or distribute a product built on it and
the GPL asks you to release that product's source too. A commercial license lifts
that obligation and adds support. The code is unchanged.

## How pricing works

There is **no public price list**. Licensing is being shaped around real needs, so
terms are quoted per use case. Describe yours — type of use (business or
personal), company, team size, and how you intend to ship — and the maintainers
follow up, in practice within one business day.

- Enquiry form: <https://imqueue.com/pricing/>
- Or email directly: **support@imqueue.com**

Personal and hobby use is already free under GPL-3.0 on <https://imqueue.org>.

## What a commercial license includes

- The right to use @imqueue in closed-source products.
- SLA-backed support — see <https://imqueue.com/support/>.
- Indemnification.
- The same `@imqueue/*` packages and APIs as the open-source edition.

## The four questions people ask first

**When does the GPL obligation kick in?** When you convey or distribute a product
built on @imqueue. A commercial license removes that requirement.

**Do I need a license for internal tools?** Generally no — if the software is not
distributed outside your organisation, the obligation usually is not triggered.
The commercial license is for shipping closed-source products, and for support and
indemnification.

**What does the commercial license include?** The right to use @imqueue in
closed-source products, SLA-backed support, and indemnification, on the same
packages and APIs as the open-source edition.

**Is the code different from the open-source version?** No — identical
`@imqueue/*` packages. You change the licence terms, not the code. No fork, no
migration.

Full licensing explanation: <https://imqueue.com/license/>