Licensing & attribution on Kriops

Licensing is where most marketplaces hide the fine print. Kriops does the opposite: every asset's provenance is part of its packaging, and the license rides inside the payload where you can't lose it. There are two kinds of assets on the shelves, and each has one clear rule.

Sourced assets — permissive, with attribution shipped

Part of the catalog is built on permissively licensed source material — licenses that allow commercial use, modification and redistribution, on the condition that the original notices are preserved. Kriops does the preserving for you: every sourced payload ships with an ATTRIBUTION file inside, listing the upstream projects and their license terms. You don't have to reconstruct provenance from a listing page after the fact — it travels with the files.

First-party assets — licensed by kriyaworks

Assets built by the studio are licensed to you directly by kriyaworks for use in your own commercial work — client projects included. You're buying the right to build with the asset and ship what you build. What the license doesn't grant is the right to relist the asset itself as merchandise — the value you resell should be the thing you made with it, not the thing you bought.

What to actually do

• Keep the ATTRIBUTION file with the code or design it arrived with — through forks, refactors and handoffs.
• Shipping a product that embeds a sourced asset? Carry its notices into your own attribution or licenses page.
• Check the license field on any listing before pulling it — every asset states its terms up front, so your agent can check too.

None of this is legal exotica — it's the same notice-preservation discipline open-source software has run on for decades, applied to creative assets and automated so the default path is the compliant one. The file is in the payload. Leave it there, ship honestly, and licensing on Kriops stays exactly as boring as it should be.