License and attribution.

1. What this covers

Flowy's own work on this site: which plugins we picked and which we left out, how they are categorised and ranked, the routing in every FLOW.md, our summaries and descriptions, the glossary, the comparisons, and the guides. That work is licensed Creative Commons Attribution-ShareAlike 4.0.

It does not cover the plugins and skills we index. Those belong to their authors under their own licenses. We index them, link to them, and describe them. We do not relicense them, and nothing here gives you rights to them. Section 6.

2. Attribution, and exactly what form it takes

CC BY-SA 4.0 lets the licensor state the manner of attribution. Ours has five parts, and they apply to every use, paid or free:

1. Credit by name: Flowy.
2. A live, followable link to flowy.sh. On the web that means a real link a reader and a crawler can both follow. Not nofollow, not hidden, not behind a click.
3. The license named and linked: CC BY-SA 4.0.
4. A link to the specific page you took it from, not just our homepage.
5. A one line statement of what you changed, if you changed anything.

It has to appear where the audience for your copy will actually see it. Not only in a file nobody opens. The test: can somebody who found your version find ours without already knowing we exist?

3. Commercial use is allowed

You can use this in a paid product. You can put ads around it. You can be a competitor. CC BY-SA 4.0 permits all of that and we are not asking you to stop.

Two things come with it, and they are conditions of the license rather than requests. Attribute, exactly as in section 2, with no commercial carve out. And share alike: anything you build on this work has to carry CC BY-SA 4.0 or a compatible license, and you cannot add technical or contractual measures that take those freedoms away from the next person. Sell it if you like. Keep it open on the same terms.

If share-alike genuinely does not fit your business, ask. A separate commercial license is a conversation, not a refusal.

4. AI crawlers and AI products

You are welcome here. We want to be indexed, quoted, and cited, and /llms.txt exists to make that easy.

The same condition applies. When our work informs an answer, cite it as Flowy and link flowy.sh. Training on public web content is unsettled law and we are not pretending otherwise. Reproducing our curation, rankings, routing, or descriptions in a product is not unsettled: that is reuse, and reuse carries the conditions above.

5. What we do not claim

Saying this plainly is what makes the rest worth taking seriously. We do not claim facts: that a skill exists, who wrote it, what license it carries, how many stars it has. Facts are not copyrightable and we will not pretend otherwise. We do not claim the idea of a directory, of routing an agent to a skill, or of a hook that keeps routing in context. Ideas and methods are not copyrightable either. Build your own.

What we claim is the selection, the ordering, and the words: which things we chose and which we rejected, how they are arranged, and how they are described.

6. The plugins and skills we index

Every plugin, skill, agent, command, hook, and MCP server in this catalog belongs to its author under its own license. We bundle none of them. Install commands point at the author's own repository, and their license governs your use of their work. Each Flow ships an attribution file naming the author, the license, and the source for everything it routes to.

If you are an author and want your work removed from the index, email us and it comes down. No argument.

7. If something is off

Almost every attribution problem is an oversight, so we start with an email and it almost always ends there. You add a line, we say thanks. Formal steps exist under the license and we would rather never use them. We would rather have the link.

Questions, permission requests, commercial licensing, or takedowns: maximo@flowy.sh. Full repository terms, including the code license and how copies are detected, live in flowy-core.

8. Not legal advice

This page states our terms in plain language. The license text governs, and where the two disagree the license text wins.