When I was going for a selfhosted mesh tunnel solution this year, I originally steered toward Netbird given that Tailscale (the client) is rather obtuse to connect with alternate control servers.

I don't actively use Netbird, but rather did go with Headscale in the end. If you're satisfied with and your requirements for Netbird don't include anything that deviates from their setup scripts, I'd imagine your deployment would go fine. My requirements and my strong desire to have everything relevant in my selhost deployments be fully to mostly declarative, and be trackable via git had me finding out how incompatible Netbird is for me. I don't think I have seen an app more averse to being deployed declaratively, which as it turns out is likely the reason their deployment scripts exist in the first place.

The there's the (at the time at least) really confusing and contradictory documentation that describe two different generations of potential deployment of the software. Good documentation is half of what makes software deployments maintainable, and Netbird had (and might still have) outright misleading documentation that will have you looping in circles attempting to figure out reasonably standard functionality like using external oidc for accounts.