You could make it available upon request, see the reasons for the request, then decide to remove the option if people aren't taking it for the right reasons. M

You could make it available upon request, see the reasons for the request, then decide to remove the option if people aren't taking it for the right reasons. My guess is that few would ask, but those who would are the ones that could help you improve the program. People trying to take your market won't beat you just by tweaking your source and selling it. I've been thinking about a related idea: opening the security code, at the very least. How do you make the security of a web app public so that smart people know about it, but control it so that if not enough people are looking, exploiters see the holes first? I think it's the kind of thing you wait to do when you're bigger, but we don't see much openness on web security like we do for most FOSS.