Superhive turned on Support Periods for creators on 22 June.
Every article I have read about it was written by someone who buys Blender add-ons. I sell eighteen of them there.
From this side of the desk, everyone is arguing about the wrong clause.
What you actually sign up for
Opt a product in and you commit to three things, for twelve months, for everyone who buys in that window:
- Answer support through the Superhive inbox within three business days.
- Give buyers permanent access to every version you ship in that period.
- Keep the product working with the current Blender LTS release.
Almost all the noise has been about the first two. The third one is the policy.
The window is twelve months. The obligation is one release.
Blender ships three releases a year and exactly one is LTS. 5.2 LTS landed on 14 July 2026 and is supported until July 2028.
Read literally, the commitment is narrower than the panic suggests. You owe the current LTS, not every build — a once-a-year job on a schedule published years ahead.
Now read it the way a customer will.
They are not running the LTS. They are running whatever was current when they installed Blender, or whatever their studio pinned.
Your obligation is one version. Your inbox is every version. Nothing in the policy closes that gap.
What a release actually does to an add-on
"Blender updates break add-ons" is a sentence people nod at without picturing.
When 4.0 shipped, the Principled BSDF was rebuilt and its inputs were renamed. Specular became Specular IOR Level. Subsurface became Subsurface Weight.
Every add-on that called that node by socket name stopped working on release day. Not because it was written badly — because a string changed.
When 4.2 shipped, packaging moved too. Anything headed for the Extensions platform had to be repackaged.
Neither is a bug in anyone's add-on. Both are days of work that produce no new feature, on a date somebody else chose.
Maintenance tracks the API, not the price
My cheapest listing, Batch Converter, is four dollars. Across the eighteen, declared minimums run from Blender 3.0 to 5.0.
Here is the part sellers know and buyers do not. That socket rename is the same mechanical fix on a four-dollar tool as on an eighty-dollar one.
Maintenance cost scales with how much of Blender's API a tool touches. It does not scale with what you charged.
A tool that calls one render operator can sit on a 3.0 minimum for years. A tool that builds materials — Edge Wear is one — is exposed to every shading change the Foundation makes.
The renewal ladder lets a creator charge up to 100 per cent of the current price again. Real money on a sixty-dollar add-on, a rounding error on a four-dollar one.
So the policy funds maintenance at the top of the market. At the bottom, where most Blender add-ons live, it names an obligation without paying for it.
Where I disagree with the criticism
The sharpest objection I have read is Hideki Saito's: Blender add-on developers are not software companies. They are solo developers keeping a project alive next to a full-time job.
He is right about who we are. I think he puts the damage in the wrong place.
Three business days is not the burden. A seller who cannot answer inside three working days has already lost that customer, policy or no policy.
The weight sits in the compatibility clause. Specifically, in the distance between the one version you owe and the several people actually run.
And I would still rather have it written down. Before June, every add-on there carried an invisible support promise.
Buyers assumed forever, sellers assumed goodwill. The two only met when a tool broke and the seller had moved on.
The "as is" label is the half nobody discusses
A product without a support period is labelled as is. That is the genuinely useful part, and almost nobody is discussing it.
It is the first time a Blender marketplace has let a seller say a product is finished without that reading as abandonment.
Finished is a real state for a tool. Not everything should be a living project.
If you buy add-ons, that label hands you a question you could not ask before. An add-on whose page says Blender 4.2, last updated before 5.0, is three releases behind.
Ask whether it carries a support period. The answer is on the listing now, either way.
What I am doing with mine
Opt in where the add-on touches something Blender is actively moving: shading, geometry nodes, packaging. Those break whether I promise anything or not.
Where a price cannot fund a year of maintenance, the honest options are to raise it or ship as is. A support badge on a four-dollar tool nobody intends to maintain is not one of them.
Where the opposite is true
None of this should reach texture packs, alphas or material libraries. I hope Superhive keeps it that way.
A 4K PNG does not break when Blender updates. A support period is a promise about code, and about how code rots when the host moves underneath it.
Attach one to a folder of images and it becomes a badge everybody buys and nobody means. That is the invisible promise this policy was written to kill.
