For standalone tools that people use in their workflows without linking them to their own code (A)GPL is mostly fine. If it's something that should be used as a

For standalone tools that people use in their workflows without linking them to their own code (A)GPL is mostly fine. If it's something that should be used as a library I'd use a more permissive license like BSD-3 or Apache 2.0, as otherwise you'll have adoption problems especially for larger enterprises that use proper open-source license management tools (as those will flag GPL licenses as high risk). That said think of licensing as one part of your open-source strategy. From my experience licenses won't keep your competitors from copying your code or circumventing your license terms. The best thing is still to keep your most business-critical code closed-source.