Synoria AI CorporationEmpresa de software autónoma
Herramientas de desarrollo

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.

← Todos los productos

Este producto esta hecho para el mercado: United States.

Herramientas de desarrollo

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.

Cómo funciona

  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.

Qué obtienes

  • 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.

Captura de pantalla

Licence Triggers: the axis is distribution, not money

Detalles técnicos

Estándar9.99 USD · 1500 solicitudes · licencia de 31 días · pago único · acceso de 31 días
Pro19.98 USD · 6000 solicitudes · licencia de 31 días · pago único · acceso de 31 días
Aislamientoinstancia dedicada por licencia
Medición de usouso de LLM medido por licencia
Accesoacceso web con clave de licencia

Como configurar y usar

  1. Compra la licencia — tu clave (lic_...) aparece en la pagina del pedido y en tu correo.
  2. Inicia sesion en app.synoriaai.com con tu clave de licencia.
  3. Sin instalacion — el producto funciona en el navegador, en tu instancia aislada.
  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.

Preguntas frecuentes

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.

Con stablecoins USDT o USDC en una de las redes mostradas al pagar. Escaneas un QR con el importe exacto rellenado — no hace falta tarjeta ni conectar una cartera.
El pago se detecta on-chain y se asocia a tu pedido por su importe único. Tras las confirmaciones, se genera tu clave de licencia y se prepara tu instancia del producto; la página del pedido se actualiza sola.
No. Haces un pago único en stablecoin por una licencia de 31 días con una cuota fija de solicitudes. No hay renovación automática — para seguir usándolo, simplemente compras de nuevo.
Cada plan incluye un número fijo de solicitudes por período de licencia. Hay un pequeño margen adicional; al agotarse, las solicitudes se pausan hasta comprar una nueva licencia.
Sí. Cada licencia corre en su propia instancia aislada con su propio directorio de datos — los clientes nunca comparten instancia ni datos.
Los pagos on-chain nunca se pierden. Guarda tu número de pedido y contacta con soporte; el pago siempre puede asociarse a tu pedido.
Cada producto se construye para su mercado objetivo y usa el idioma de ese mercado; esta tienda está disponible en 9 idiomas.

Productos relacionados