Blender 4.5 LTS, 5.0, 5.1 and 5.2. The whole automated test suite is run in all four before a release ships, so the same file gives you the same result whichever one you open it in. One exception worth knowing: the Sound field needs Blender 5.2, because it samples audio with a node that exists only there. Everything else works in every version.

No. Everything happens in one panel in the sidebar. Cloner Pro builds and maintains the node trees for you, and you never have to open a node editor. If you do want to look under the hood, nothing stops you.

Clones stay as instances until you ask for real geometry, and Proxy Display swaps heavy sources for lightweight stand-ins while you work. In a file that has no cloners in it, the add-on costs nothing measurable at all.

Yes, two ways. Either install the add-on on the farm as you would any other, or bake the cloner to real geometry or to keyframes first. After baking, the scene does not need Cloner Pro at all.

Yes. Everything you create with it is yours, for personal and commercial projects, with no royalties and nothing to credit. The add-on itself is GPL v3, as Blender add-ons are required to be.

An Array modifier repeats an object. Cloner Pro gives you the whole motion-graphics model on top of it: stacked effectors that transform the clones, and layered fields that decide which clones each effector touches and how strongly. It is all Geometry Nodes underneath. The difference is that you drive it with sliders instead of building it.

Bake to real geometry, then export the way you normally would: Alembic, FBX, USD, or anything else Blender writes.

Updates are free. The test suite runs against every supported version, so compatibility problems are found before they reach you rather than after.