Hi @Muchemi, I've not used both systems but as you may already know me from this list as pro-propreitary ( can be adobe , M$, MAC etc ). I'd like to offer you some advice, so that you may make the right decision. Here's my view : - In a production environment, you must ensure that you taken on the huge responsibility of learning in depth the free-code system that you are planning to implement. Anything short of this and you are going to head into big time trouble. Because production, small or medium enterprises have heavy demands on uptime, reliability and sustainability you are placed in a very difficult and stressful situation. And this will certainly happen, at some point as there are pitfalls you may not be aware of. - A simple example. You may not have brushed up your knowledge on mysql but if such is being used for retaining username/passwords/profile data, sometimes there will be problems as is common with databases. Maybe the user had put in special character combinations as a password, and this for some reason causes errors, you will now have to not only troubleshoot but also fix the system very quickly. - Unix-clones are really stable, just as other systems, but that is not where you will find the problems. It is the add-ons that create many issues. You must then also know the Unix-clone OS quite well to troubleshoot any issues e.g stopping services, flush or even re-start, creating cron-jobs etc - Another example is if you intend to use the system as a mail server, you must partiton your system hardware harddrives according to the number of users/email traffic/logfile traffic. - Data backups and images are the most critical part, you must know how the Unix-clone handles this. There's quite a lot to the production environment, I'm sure you are already aware. Whatever you do, don't do it just because its free-code, do it because you know how to sustain the services. HTH's and my view. Rgds.