Licence
What a subscription includes, and what you may do with library items and generated pages.
What a subscription includes
A CreativePower subscription gives you two things while it is active:
- Generating pages. You describe a page and CreativePower has it written, using your project's DESIGN.md and motion patterns from CreativePower's own catalogue. There is a per-user daily limit on how many you can generate; the app tells you when you reach it. [Decision 16: whether to publish the allowance, and its number]
- The library — 3,427 items (motion patterns, page sections, UI components, design systems, prompts, agent skills, effects and material for video) drawn from 98 open-source projects. Each item keeps its own licence: 3057 are under the MIT licence, 198 under the Apache License 2.0, 140 are prompts dedicated to the public domain (CC0 1.0), 28 under the zlib licence, and 4 dedicated to the public domain under the Unlicense.
Every library item has a complete record of where it came from, who wrote it and under what licence, and carries its licence notice. Each one is cleared for you to use: nothing in it is hotlinked from someone else's server, needs a paid font licence, or uses a real company's logo. Who made each one is on the credits page.
What you may do
- Use library items in your own work and your clients' work, commercial work included, as each item's own licence allows.
- Change them, combine them and ship them, keeping the licence notice that comes with each one.
- Copy an item or export a page, knowing the notices travel with it (see below).
- Keep the pages you generate and use them as the terms and the licence of anything they contain allow.
What you may not do: remove a licence notice, present someone else's work as your own, resell the library itself as a library, or use any item beyond what its own licence allows.
Using library items
Every library item you copy comes with its licence notice attached: a prompt has the notice appended, and code carries it as a comment at the top of each file. You may use an item in any way its own licence allows — for MIT and Apache 2.0 that includes commercial use, changing it, and shipping it in your own and your clients' work, on the condition that the notice goes with it (see below). CC0 items carry no condition at all.
[Decision 20: whether items copied during a subscription may still be used after it ends]
Pages CreativePower generates for you
A generated page is AI-generated output, written by Anthropic's Claude model from your brief, your project's DESIGN.md and a set of motion patterns from CreativePower's catalogue. Library items are never used in generation: the generator refuses them, because a generated page cannot yet carry their notices.
[Decision 4: what rights you have in a generated page — ownership, commercial use, client work — and anything we keep]
[Decision 5: whether every generated page may be used commercially, given where some of the catalogue's patterns come from. Until this is decided, this page cannot promise unrestricted commercial use of every generated page.]
The notices that travel with the code
Some licences allow reuse on one condition: that the copyright and licence notice goes wherever the code goes. For MIT that is the licence text itself; for Apache 2.0 it is the licence and any attribution notice the project requires. CreativePower attaches these notices for you:
- Library items: every way of copying an item — its prompt, its code, the library API — returns it with the item's own notice attached, and that notice is the item's whole licence text: for MIT the full permission notice and disclaimer, for Apache 2.0 the full License. In a code bundle each file carries it. An item with no notice on file is refused rather than handed out bare.
- Generated pages: if a pattern the generator used requires a notice (today, patterns adapted from the Apache-2.0 project motion-anything), the notice — the attribution and the full text of the Apache License 2.0 — is written into the page as a comment directly after its DOCTYPE. Copying those patterns from the pattern library carries the same full text.
- Exports: exporting a page as static HTML, React or Next.js ships a NOTICE.txt file holding every notice and the full text of each licence, and each code file carries the attribution and points to that file. This includes recognised patterns whose comment was removed from the page.
Your part: when you ship code or a page that carries a notice, keep the notice in it. Do not delete the comment. If you copy only part of an item into your own file, bring the notice with it.
Generated pages may also load open-source libraries from public CDNs — the generator is instructed to use GSAP, Lenis, AOS and the Spline viewer. Those libraries are not copied into your page and their licences are not among the notices above; they are their authors', and apply to you as they would to anyone loading them. They are listed on the credits page. GSAP is free to use, commercial use included, under GreenSock's own licence, which is not an open-source licence. [Unverified: the current GSAP licence terms, checked at gsap.com — they were not re-read when this page was written]