Superhive switched Support Periods on for creators on 22 June. Every take I have read on the policy was written by somebody who buys Blender add-ons. I sell eighteen of them there, plus two training titles, and from this side of the desk the argument is happening over the wrong clause.
Opting a product in commits you to three things, for twelve months, for everyone who buys inside that window. Reply to support through the Superhive inbox within three business days. Give the customer permanent, unrestricted access to every version you ship during the period. And keep the product compatible 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 of them is LTS. 5.0 landed on 18 November 2025, 5.1 on 17 March 2026, and 5.2 LTS on 14 July 2026, supported until July 2028.
Read the commitment literally and it is narrower than the panic suggests. You owe compatibility with the current LTS, not with every build the Foundation ships. That is a once-a-year obligation on a schedule published years in advance, and as contracts go it is survivable. I think the people describing this as an enterprise support contract have not read that line.
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, or the point release they upgraded to for one feature. Your obligation is to one version. Your inbox is every version. Nothing in the policy closes that gap and nothing was ever going to.
What a release actually does to an add-on
Worth being specific, because "Blender updates break add-ons" is the kind of sentence people nod at without picturing.
When 4.0 shipped, the Principled BSDF was rebuilt to line up with OpenPBR and its inputs were renamed. Specular became Specular IOR Level. Subsurface became Subsurface Weight. Transmission became Transmission Weight. Every add-on that addressed 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. The bl_info block inside the script gave way to a blender_manifest.toml beside it, and anything headed for the Extensions platform had to be repackaged.
Neither of those is a bug in anybody's add-on. Both are days of work that produce no new feature, on a date somebody else chose.
Maintenance tracks API surface, not price
My cheapest listing, Batch Converter, is four dollars. Roughness Builder is twelve, and its page declares Blender 4.0 and up, which means its floor is the exact release that renamed the shading sockets underneath it. Across the eighteen, declared minimums run from 3.0 to 5.0.
Here is the part sellers know and buyers do not. That socket rename is the same mechanical fix on the four-dollar tool as on the twelve-dollar one. Find every socket name, change it, retest, repackage. It would be the same fix on an eighty-dollar one. Maintenance cost scales with how much of Blender's API a tool touches, and not at all with what you charged for it. Something that calls one render operator can sit on a 3.0 minimum for years and keep working. Something that builds materials is exposed to every shading change the Foundation makes.
So a support period is cheap to promise on half my shelf and expensive on the other half, and the split has nothing to do with the prices. The renewal ladder — the creator picks 25, 50, 75 or 100 per cent of the current price — is real money on a sixty-dollar add-on and a rounding error on a four-dollar one. The policy funds maintenance at the top of the market. At the bottom, where most Blender add-ons actually live, it names an obligation without paying for it.
Where I part company with the criticism
The sharpest version of the objection I have read is Hideki Saito's, published on Medium on 14 May. Blender add-on developers are not software companies. They are solo developers, freelancers, technical artists keeping a project alive next to a full-time job, and a support contract shaped for a company was not built for that.
He is right about who we are. I think he has the damage in the wrong place. Three business days is not the burden — a seller who cannot answer a customer inside three working days has already lost that customer, policy or no policy. The weight sits in the compatibility clause, and specifically in the distance between the one version you owe and the several versions people are actually running.
And I would still rather have it written down. Before June, every add-on on that marketplace carried an invisible support promise. Buyers assumed forever, sellers assumed goodwill, and the two only met when a tool broke on a new Blender and the seller had moved on.
The "as is" label is the half nobody is discussing
A product without a support period is labelled as is. That is the genuinely useful part of this policy and almost nobody is talking about it.
It is the first time a Blender marketplace has let a seller say in public that a product is finished, without that reading as abandonment. Finished is a real state for a tool. Not everything should be a living project, and pretending otherwise is how a shelf fills up with things quietly rotting behind a badge.
If you buy add-ons rather than sell them, that label hands you a question you could not ask before. An add-on whose page says Blender 4.2 and whose last update predates 5.0 is three releases behind. Ask whether it carries a support period. The answer is on the listing now, either way, and that is the point of it.
What I am doing with twenty listings
Opt in where the add-on touches something Blender is actively moving: shading, geometry nodes, packaging. Those break whether I promise anything or not, so I may as well be on the hook for the fix and say so on the page. Where a product's price cannot fund a year of maintenance, the honest options are to raise the price or to ship it as is. What is not honest is a support badge on a four-dollar tool nobody intends to maintain, and Superhive has said that creators who fail to meet the commitment risk removal from the marketplace.
Where the opposite is true
None of this should reach texture packs, alphas or material libraries, and 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 specifically about the way code rots when the host application moves underneath it. Attach one to a folder of images and it becomes a badge everybody buys and nobody means, which is the invisible promise the policy was written to kill.
