Do you need a commercial license for @imqueue?
@imqueue is dual-licensed. Everything is free and open under GPL-3.0 on imqueue.org. A commercial license lets you ship the same packages inside a closed-source product without the GPL's source-release obligation — plus support on top.
Two ways to use it. Same code.
The packages are identical — the license is what differs. No fork, no separate build, nothing to migrate.
Open source · GPL-3.0
Free forever. Use, modify, and distribute the @imqueue/* packages under GPL-3.0. The catch: if you convey or distribute a product built on them, the GPL asks you to release that product's source under the GPL too.
Commercial license
The right to ship @imqueue inside a closed-source product — the GPL source-release obligation lifted — with SLA-backed support and indemnification. Same packages, same APIs, private source.
Start open, switch anytime
Prototype and build on the open-source edition. When you're ready to ship closed-source, buy a license — you change the terms, not a single line of code.
When does the GPL-3.0 obligation apply?
The copyleft trigger is distribution. Here's the plain-language version — use it to figure out which side of the line you're on.
Shipping a closed-source product
You distribute an app, a device, or on-prem software built on @imqueue and don't want to release its source. A commercial license is the clean path.
Internal-only tools
The software runs inside your organization and isn't distributed outside it. The GPL's distribution trigger generally isn't hit — though many teams still license for support and indemnification.
A SaaS / hosted service
GPL-3.0 is not the AGPL: running @imqueue behind a network service you host usually isn't "conveying," so the source-release obligation generally isn't triggered by SaaS use alone.
This page explains how the licensing model works in plain terms — it isn't legal advice. If you're unsure how the GPL-3.0 applies to your specific situation, tell us your use case and we'll help you find the right fit (and involve your counsel where it matters).
A 10-second self-check
Are you distributing it?
If nothing built on @imqueue leaves your organization, you're almost certainly fine on the open-source edition.
Do you want your source private?
If you distribute a product and need to keep its source closed, that's exactly what the commercial license is for.
Do you need support or indemnification?
Even when the GPL doesn't force your hand, a commercial agreement adds an SLA and legal cover. See support.
Licensing questions
Is @imqueue really free?
Yes. The full framework is open source under GPL-3.0 on imqueue.org — free to use, modify, and distribute under the GPL's terms. The commercial license is only needed when those terms don't fit your product.
Can I use the GPL-3.0 version in a commercial project?
Yes — GPL-3.0 permits commercial use. The obligation is about source disclosure on distribution, not about charging money. If you distribute a product built on it, the GPL asks you to release that product's source; a commercial license removes that requirement.
Does running @imqueue in a SaaS trigger the GPL?
Generally no. GPL-3.0 is not the AGPL — providing access to a hosted service isn't "conveying" the software, so SaaS use alone typically doesn't trigger the source-release obligation. A commercial license is still available if you want support or indemnification.
Is the commercial code different from the open-source code?
No — the exact same @imqueue/* packages and APIs. A commercial license changes the terms you use them under, not the software. There's no separate fork to install or migrate to.
How is a commercial license priced?
We're shaping licensing around real needs rather than a fixed public price list. Tell us how you'd use @imqueue — team size and how you ship — and we'll follow up with the right fit.