Precisely bitwarden movement proves my point. Bitwarden tried to degrade the features/compatibility of the solution and they couldn’t because of the vaultwarden implementation.

Can they always add new features after a pay wall? Sure! But once foss Sw is here it is simple impossible to remove functionality, at most, to get some coins for services not fully selfhosted.

If tailscale tries to do something similar is goint to be a shoot into their own leg, because all the sw already disclosed makes it impossible. Could they make the relay a paid one? Sure but then they will face the competence of a vps with the Headscale implementation.

This and only this is because in your home lab only foss Sw should be allowed, even if you need to pay some money from time to time

Honestly, this seems more than your assumptions and fears than anything else.

Clients are open source and foss, the moment something strange is in, Headscale could adapt.

If they finally goes to full close source, then the community will fork (emby - jellyfinn drama).

Your arguments don’t hold together, for the good of the community

I really don’t see how the enshitification could work when we have the fee version of the central servers Headscale

So yes, it could be a pay wall for some advance featuresike funnels and so on. But the primary use is secured…

I have more than 120 electronic identities, impossible to track the counter or to remember the tld of all websites I visit.

The concepts is only useful in a very small and defined scenario.