Long-time reader here… Though ultimately, you’re entitled to do as you wish with your product and your code, I do have to point out that you may working under a misconception with regards to the GPL. There are many successful companies whose products are open source under GPL and/or other open source licenses who are doing extremely well from a financial perspective.

Take MySQL for example, their product is GPL but customers and OEM/ISV’s can purchase a commercial license which effectively creates a dual-licensing model. In a nutshell, paying customers and OEMs are excempted from the viral aspects of the GPL. This occurs because MySQL owns the IP to their code much as you do.

In the case of MySQL they also have an FOSS exception which excempts other open source projects licensed under different (but approved) open source licenses from having to be, in turn, released under GPL. This helps create a productive environment for innovation and contribution while offering enterprises the comfor that they’re protected from the GPL provisions.

Please understand that I’m not a raving open source purist, my boss likes to talk about “open source capitalism” and you have the opportunity, should you desire, to take advantage of that and grow out your community of users and contributors while still being able to license a commercial version as you see fit.

This is the way we’ve been doing business at my company for the last two years and it’s worked out very well for us. Believe me when I tell you, we’ve had no customers look elsewhere just because of our license.

Some useful links:
http://www.linuxinsider.com/story/38172.html
http://www.mysql.com/company/legal/licensing/foss-exception.html

We’d love to be doing business with Accenture, EDS, Organic, RazorFish, Sapient, PA Consulting and any other ad agency or web house that produces web sites, social networks or blogging plaforms. And all those resellers would be pretty pissed and go find a solution elsewhere the MOMENT I told them about my GPL code.

I’m not challenging your decision to go no-GPL, it’s your business, but you need to be careful there, Marc. You have a gift for hyperbole. There are clear reasons for GPL versus owning and controlling your own code base. I have had some dealings with two of the companies you mentioned in the quote above and GPL is not a no go zone for working with those companies. It depends on what the business partnership entails. You can’t simply paint them with a NO GPL brush.