One page per vendor, read from its own published pages
Every vendor gets a page read from its own priced pages, help centres and published licences. The clause is quoted, the plan it attaches to is named, and the date it was read is printed beside it. As of 2026-09-12.
Terms pages are written to be defensible, not to be read quickly. The sentence that grants commercial use is rarely the sentence that looks like it does, and the grant is often narrowed two clauses later by a definition of the plan it applies to.
So each page keeps the quote and the plan together. A permission granted to paying customers means nothing until the terms say which plans count as paying, and that definition lives on the pricing page rather than in the contract.
Where the terms say nothing about a use, the page records silence rather than permission. Silence is the most common finding on this grid and the most expensive one to assume your way past.
1The vendors
- SceneMixer — SceneMixer grants commercial use to every user, free credits included, frames ownership around authorship, and publishes one input restriction.
- Pika — Where Pika says a commercial licence begins, what its free tier carries, and which of the four points this register keeps it leaves unstated.
- LTX Studio — Where LTX Studio says a commercial licence begins, what its free tier carries, and which of the four points this register keeps it leaves unstated.
- Kling AI — Where Kling AI says a commercial licence begins, what its free tier carries, and which of the four points this register keeps it leaves unstated.
- Luma — Where Luma says a commercial licence begins, what its free tier carries, and which of the four points this register keeps it leaves unstated.
- Runway — Where Runway says a commercial licence begins, what its free tier carries, and which of the four points this register keeps it leaves unstated.
- invideo AI — Where invideo AI says a commercial licence begins, what its free tier carries, and which of the four points this register keeps it leaves unstated.
- Synthesia — How Synthesia attaches its use restriction to the avatar rather than to the subscription, and what its licensing page lists as allowed and not allowed.
- HeyGen — Why the HeyGen permission sits in a help article about exporting rather than on the plan table, and what condition the wording attaches to it.
- Hailuo AI — How Hailuo AI answers the ownership question and leaves the commercial-use question unworded, and why the disclaimer is conditional on paying.
- Higgsfield — The entry that fills all four register columns from one help centre answer, including the ownership line and the restriction on images of other people.
- Fliki — The free tier that writes its exclusion down instead of implying it, and the ownership line Fliki publishes alongside the commercial licence.
- Leonardo.Ai — The entry whose free tier grants commercial use and charges for it in visibility, and where ownership turns on whether a generation stayed private.
- Adobe Firefly — Why the Adobe Firefly statement is a claim about how the models were trained rather than a permission attached to one of the plans on the page.
- HunyuanVideo — The licence that answers the commercial-use question with a map and a user count instead of a subscription tier, and what it says about outputs.
- Wan — The shortest answer in this register: an Apache 2.0 licence on the weights and one sentence disclaiming any rights over what the model produces.
- Stable Video Diffusion — The licence that sets its commercial-use boundary with an annual revenue figure, and what it says happens to the grant once a business passes it.
A vendor earns a page when its own documents answer more than one of the grid's questions.
Also on the grid: Fields, Records, Pairs, Questions, Words, Learn, Data. What makes a clause quotable is set out on the reading page.