Ship @imqueue in 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, with support on top. Same code, no changes.
We're shaping licensing around real needs — tell us how you'd use it and we'll follow up.
Thanks — we'll be in touch.
A member of our team will reach out within one business day.
Licensing FAQ
When does the GPL obligation kick in?
When you convey or distribute a product built on @imqueue. GPL-3.0's copyleft asks you to release that product's source under the GPL. A commercial license removes that requirement.
Do I need a license for internal tools?
Generally no. If the software isn't distributed outside your organization, the GPL obligation usually isn't 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 license terms, not the code. No fork, no migration.