< Back

When does an Open Source CMS make sense?

We offer our clients a variety of Content Management options, including Microsoft Sharepoint, Ektron's CMS400.net and DotNetNuke. Each product has its strengths and weaknesses and while there are definite differences in the way individual features are implemented, for the most part the same level of functionality can be achieved using any of these three platforms. The major differentiator is cost. SharePoint and Ektron both require licensing fees while opensource products like DotNetNuke are free. This seems like an easy choice, but when you start looking at the costs of ongoing maintenance the advantage seems less clear.

Any portal implementation is by nature complex, usually made up of a combination of platforms and applications. With a product like Ektron or Sharepoint you have a single entity that you can deal with to resolve issues that might arise from upgrades to the CMS, to your network environment, or to programming enhancements you might have made in other parts of the site. That entity is legally bound to respond to you within the terms set out in your service level agreement. With open source products like DotNetNuke, there is an initial savings in licensing fees, but because there is no single entity responsible for the entire solution, you bear primary responsibility for resolving problems that might arise. And that usually means an additional overhead cost in terms of resources, or contracting with an outside party (like MResult) to provide support. In some cases that initial savings will justify the downstream costs, but in other cases they will not, so its important to work with a partner who can help you to think through the larger picture.