I can give you an answer from a web hosting perspective , but this is probably a good question to ask in general discussions as well:
So from a hosting perspective I usually urge clients to go with individual WordPress sites 99% of the time, why?
1. Everyone knows WordPress, WP MultiSite has it's own quirks and isn't as well know. In the spirit of keeping it simple that makes it a better choice IMO unless you have a specific reason to go with multisite.
2. The big advantage I always saw for MultiSite was keeping things upgraded and a better user management system for large blog networks. I think with the emergence of wp-cli and manage wp there is no need to use multisite as much though.
Internally at Site5 our internal KB, training system, and internal blog, run on WordPress MultiSite and all our frontend sites run on individual WordPress sites. We did that because on the backend we needed a unified user management system, where as on our frontend that didn't matter so much.
Hopefully some other people chime in too,
Replying to Multisite Wordpress Or Multiple Instances Of Wordpress
Posted 05 August 2013 - 02:15 PM
Posted 05 August 2013 - 02:14 PM
My problem with multisite in a client context is that they aren't able to install their own plugins. You also can't install it just for them since plugins are available to all sites on the network. Using the Builder framework, each client would have their own child theme, but I don't know if you can hide them from other users on the network (maybe using a hack you could, but at that point you're probably using the wrong tool for the job).
Posted 05 August 2013 - 12:31 PM
Don't know if this is the right place to ask this (I do host with Site5 and use BackupBuddy). What's the practical difference between setting up multisite WordPress to run websites for clients or setting up multiple instances of regular WordPress in WHM for each client? What are the advantages and disadvantages of each?