David:

Product copyright indemnification

That means that if you deploy DotNetNuke for a client, and in turn the client sues you for something related to a shortcoming of DotNetNuke (Whatever that may be) that you will be indemnified. In other words, this is insurance for you and/or your client.

Also, for what it's worth $2k per year is a lot cheaper that I had expected. If you run DotNetNuke for critical business needs, that is a small price to pay for peace of mind.

In short, indemnification alone, for $2000 bucks is peanuts - especially if you can imagine being hacked (because of a security flaw in the framework, for example) and your customers' information is stolen (such as social security number, CC etc)... the $2000 is that case is money VERY well spent.

FYI - I don't work for DNN Corp, and I am in no way affiliated to the Corp (Other than contributing to the Community Edition - the pure open source side of things) - so my comments are purely speculative, and are an expression of my personal opinions, based on real-life business experience.

Cheers,

I have worked with LOTS of software in my 11 years of web application impelmentation and developer career, and I have never had to pay yearly just to keep software installed. Not ever. For support, training, or such things yes, but just to keep an application installed no.

A person should not need 2k a year of security and indemnifiction, whatever that is. The application should come with the features and seucirty it has and that should be that. Beyond that.  you should only have to pay for support - if you need it.

I have an example, I used to work on an ecommerce app called Itnershop. It cost 10k for a set number of licenses. It was very proprietery.  I learned it inside and out. I didn't need support for two years, then when I did, we bought a years support. Again, I don't mind paying for support, if I need it. If I don't I shoudn't have to pay 2k a year to just to keep the application installed.

I cant say I mind the DNN corp making a buck. They certianly deserve it. I was under the impression they got some comp from Microsoft since you DO have to pay for thier products and using DNN means you have to buy MS products. However, even if they don't, I think there is room for a commercail version and they should get something for thier efforts.

What I can't apprecaite is the year after year fee., Even for large clients. My clients are mostly small and I can't justify 2k even once for some clients, much less hear after year so I am trying to figure out who this product is for, exactly.

No, you are incorrect, there are LOTs OF CMS out there and none of them charge aa couple of grand a year just so you can keep them running, whether you need ruther support or not. Even osme of the top rate CMS are just not this expensive, even once.

You know, my sister work with McKesson Horizon clinical applications and they cost a few million dollars, but only once. I just can't imagine how I could use this at this price and still charge my client for working on it. Most of mine just pay hosting year after year and no development costs after the intial outlay.

I am also worried the systems I have in place will quickly become obselete soon. DNN has pushed for people to use this system in mission critical environs, and isn't evernone's site and system critical? Now they say if we want a product that continues to work well we have to pay a toll year after year? I wouldn't even mind a one time fee for the CE.

Beth Vest
DotComDominion.com.

Frankly I don't really see what the fuzz is all about.  From what I can see the code base for the two editions are virtually the same apart from the name difference of couse. 

If you, including myself, can not afford the PE version there is always the CE version available.  Its not like DNN is now closed sourced and  the Corp is forcing people to join the PE crowd.   You are all still free to use the CE version and if at times require professional support purchase a support subscription or upgrade to the PE version.