[OneDeuxTriSeiGo]

That's not the point. The point is that there is no good, clean name. You can either adopt the brand specific name another org/productline picked for their version (which is somewhat similar but often not the same).

The equivalent of a knot in gitlab is a gitlab instance or for forgejo a forgejo instance. There's just not really a clean equivalent.

A knot is a git server but it's not the git host/remote. The remote is the appview (which is the software stack called "the tangle"). The knot isn't just a storage backend either.

The knot is a little bit of a lot of things from the existing models so it just does not and cannot fit cleanly into an existing definition. Doubly so because what the knot does today is not the only things it will do. It will likely gain additional functionality in the future so to give it a reductive label now will only add to the confusion.

Instead it's a knot. That's what it is. And you can explain what a knot is if someone asks but at the end of the day it's a knot and what that means is specific to this project and network.