Synoria AI CorporationAutonomous software company
Developer Tools

Licence Triggers: the axis is distribution, not money

"It's a side project, I'm not selling it, so the licences don't matter" is the wrong axis. Copyleft is triggered by distributing a work - and, under the AGPL, by letting people use it over a network - never by charging for it. A free app on a store distributes; a free web service is a network use. The two places this costs people money are the same two every time: GPL-3.0 behind a service obliges nothing by itself while AGPL-3.0 obliges source, and a single AGPL dependency raises the floor of a project you licensed MIT to AGPL-3.0 the day you ship it. Enter your dependencies, your outbound licence and how it reaches people, and each row says what fires, what it requires, and where two licences simply cannot be combined.

← All products
Developer Tools

Developers shipping side projects and small products who pulled in dependencies before reading their licences, and the teams who would rather find the conflict now than the week they launch.

How it works

  1. Choose your project's licence, how it reaches people, and whether it is or might become commercial.
  2. Add each dependency with the licence as declared and how it is included.
  3. Read the verdict column: conflict means the combination is not permitted, check means the answer needs facts this page does not have.
  4. Read the obligations under your shipping mode, and the licence floor your combined work inherits.

What you gain

  • Tells you plainly whether using a piece of open-source software triggers a licence obligation for your project, based on how you actually ship it, not on whether you charge money for it.

Screenshot

Licence Triggers: the axis is distribution, not money

Technical details

Standard9.99 USD · 1500 requests · 31-day license · one-time payment · 31-day access
Pro19.98 USD · 6000 requests · 31-day license · one-time payment · 31-day access
Isolationdedicated instance per license
Usage meteringLLM usage metered per license
Accessweb sign-in with license key

How to set up & use

  1. Buy the license — your key (lic_...) appears on the order page and in your email.
  2. Sign in at app.synoriaai.com with your license key.
  3. No installation — the product runs in your browser, on your own isolated instance.
  4. 1. Open the Licence Triggers page and select your project's outbound licence (for example, MIT) from the dropdown.
  5. 2. Choose the shipping mode that matches how you distribute or provide the software: internal use, distribution, or network/SaaS.
  6. 3. Indicate whether the project is commercial (this does not affect the licence result, but helps tailor the output).
  7. 4. Add each dependency by entering its name and selecting its licence from the list, then click 'Add dependency'.
  8. 5. Review the results: the tool shows the licence floor for your combined work, flags any impossible combinations, and lists concrete obligations per dependency under your chosen mode.

Frequently asked questions

Does this tool tell me if I can use a GPL-3.0 library in my SaaS product?

Yes, but only if you select 'Network/SaaS' as the shipping mode. The tool will then show whether the AGPL obligations apply to your dependencies, and what source code you may need to provide.

What happens if I add a dependency with a licence that conflicts with my outbound licence?

The tool will name the combination as impossible (for example, Apache-2.0 into GPL-2.0-only) and explain why it cannot be made, rather than just warning you.

Is my project data stored or shared?

No. All data you enter (project name, dependencies, licences) is processed in your browser and is not sent to any server. The tool does not store or transmit your project information.

With USDT or USDC stablecoins on one of the payment networks shown at checkout. You scan a QR code with the exact amount pre-filled — no card and no wallet connection is required.
The payment is detected on-chain and matched to your order by its unique amount. After confirmations complete, your license key is generated and your own product instance is prepared; the order page updates by itself.
No. You make a one-time stablecoin payment for a 31-day license with a fixed request quota. There is no auto-renewal — to keep using the product, you simply purchase again.
Each plan includes a fixed number of requests for the license period. A small overage allowance is defined beyond that; once it is used up, requests pause until a new license is purchased.
Yes. Every license runs in its own isolated instance with its own data directory — customers never share an instance or data.
On-chain payments are never lost. Keep your order number and contact support; the payment can always be matched to your order.
Each product is built for its target market and uses that market's language; this storefront is available in 9 languages.

Related products