Content Management Systems (CMS) > Kentico vs Open Source

Kentico vs Open Source

What are the differences between open source systems and licensed software such as Kentico? See the infographic created by Web Design Magic below...  
While it is in interesting concept, open source Content Management Systems are less secure because they typically use a combination of modules created by many different developers that are never security tested as a whole allowing hackers to leverage security vulnerabilities. As there are so many different modules the systems are hard to upgrade and the weaknesses are often ignored, leading to exposure & ultimately the risk of getting hacked increases. 

In addition to security vulnerabilities, open source systems tend to be less stable.  People who often contribute modules and features to the open source community often value features over quality.  Open source modules, developed for no pay by independent developers in the wee hours of the night simply do not go through the same design reviews and quality/testing processes that a licensed product has to endure each time a new version is released.  Who is going to test the module developed last year as a fun little project when the new browser is released?  In the open source community, the answer is frequently nobody, or worse, it's more often you when your site suddenly crashes the day after the latest browser security update is released.  

As a result, bugs are encountered at a higher rate with open source systems.  When a key feature on your web site stops working suddenly, who is going to fix it?  This is where the promise of open source as a low cost alternative really falls short.  When your event registration page suddenly throws an error and your customers start calling you, you call your web development team.  You lose a day as they and your hosting company point fingers at one another over who is to blame.  Then, someone finally finds problem.  Your web support company spends hours pouring through Blogs and discussion groups Googling for others who have experienced similar problems.  When that doesn't provide the answer, they dig through system logs and thousands of lines of code to try and find the issue there.
Who pays for this?  Well, that's easy - you do - in more ways than one.  But, by the time the problem is fixed you are so frustrated that you would be willing to pay anything just to have your site working again.  But, your biggest frustration is knowing that it could happen again at any time and there is really nothing you can do about it because it's not a matter of "IF" it will happen, but "WHEN" it will happen.  Who knows how long you will be down next time or what it will cost to fix it?
When considering an Open Source solution, the important thing is the total cost of ownership, not the acquisition cost.  Open source is free just like a free puppy.  If you've ever had a puppy and come home to your new Italian shoes laying in scraps in the living room while your new slobbering puppy peeks at you innocently from the corner of the room, you will know how it feels when your "free" Open Source Solution leaves a mess for you to clean up.  

Our project had some bumps and ups and downs, but JDB kept us informed and took resopnsibility and ownership and delivered exactly what they had promised, even though not everything had gone exactly as anyone had anticipated.

— Jason, Business Owner