Licenses

Every Klyna product ships under an open-source license. This page is a friendly summary; the legal text lives in each repo's LICENSE file and that file is what governs in a dispute.

WordPress plugins — GPLv2 or later

Required by WordPress.org. You can use, modify, host, and redistribute Klyna WordPress plugins, including in commercial work and on client sites, as long as derivative distributions stay GPLv2-or-later and ship their source.

Shopify apps — MIT

Use, modify, distribute, sublicense. Keep the copyright notice. We give no warranty. Most permissive license in the bench.

Browser extension — MPL-2.0

Mozilla Public License 2.0. File-level copyleft: you can ship the extension inside a larger product (open or closed), but if you modify an MPL-licensed source file, that file stays MPL.

Marketing site (klyna.dev) — MIT

The Astro source for klyna.dev is MIT-licensed. Fork it, learn from it, ship something of your own. Copyright on the words and images stays with the studio.

Blog posts and docs — CC BY 4.0

Articles on klyna.dev/blog and help.klyna.dev are Creative Commons Attribution 4.0. Quote, translate, re-publish — just credit Klyna with a link back.

Shared engine (@klyna/core) — AGPL-3.0

The SEO/GEO audit engine and TF-IDF linking core is AGPL-3.0. If you run a modified version as a hosted service, you must offer the modified source to your users. This is to keep SaaS-style forks honest.

"Klyna" name and logo

The licenses above cover the code. The name "Klyna" and the violet mark are trademarks of the studio and are not licensed for use in your own product name. See Trademark for the rules.

Where to find the actual LICENSE file

Every repo at github.com/klynahq has a top-level LICENSE file. If anything on this page disagrees with that file, the file wins.