Kiteworks vs Microsoft Office SharePoint Server comparison

"The most valuable aspect of Kiteworks is undoubtedly the private content network. This feature is particularly beneficial for us. Furthermore, it serves as a centralized platform that enables us to track and manage our information exchange."

"The top two features are the two-factor authentication, which is pretty good. It's easily understood by the users. And their API is rather robust. We have numerous integrations that work off the API."

"We could see whether the customer with whom we shared a file had downloaded it, which was not available with GitHub."

"The solution removes the limitations with file attachment size that is found with regular email."

"Scalability is impressive."

"The solution can be used remotely; it's easy to upload and share files."

"I like Kiteworks or Accellion because it's continuously upgraded. I also know that it probably works with a lot of clients."

"We can see when people are sending things. We can definitely see who is sending to whom. From the administrative logs, we can see who is sending to an outside entity, and those logs are retained for quite a while."

"This solution has provided us with a collaborative workspace to allow everyone to work together and be on the same page."

"The most valuable feature is the "Alert Me", which provides the ability to set an alert when content is either added or changed and that the alerts can be either real-time or aggregated for the day or the week."

"Document management and records management features are the most valuable."

"The forms aspect of the solution, for example, the creation of surveys, is its most valuable aspect."

"The most valuable feature is that it is very usable. I can navigate it, I can have a media call, I can have a call with my project team, so we can chat with every team kind of like WhatsApp. Any time there are projects or other things, we can chat in a secure way. It's automation-specific secure."

"The most valuable features for us are their document management list and hybrid forms. and We also use third party ad-dons to achieve workflows and other recent apps."

"The solution is scalable. You can do both horizontal and vertical scaling."

"It's a very robust product."

"I would like to see immediate releases of fixes because now it takes at least a week. If that time span can be reduced to one day or two days, that would be very helpful for users so that things are sorted and transactions work smoothly."

"There is no offboarding process for end-users in Kiteworks. It's a manual process. There is no automated syncing with LDAP and checking to see if the account is still active. It's a manual process to get people out of here, which isn't the best way."

"It could be more stable. In the next release, it would be better if it was more stable with improved performance."

"There are always issues when there are bugs or upgrades. The challenge with upgrading is getting more storage from the customer. Every time we have a new version, it requires additional storage. This means that the customer would need to procure more storage for their server, which they don't like because it means additional cost to them. So, I think my request would be that the version upgrades don't require any significant storage requirement."

"Kiteworks could benefit from enhancing the proposal knowledge base section, specifically regarding the type of work involved. Currently, the knowledge base seems insufficiently dedicated to this topic, making it challenging for new users to access the relevant administrative law. Improving the visual aids and providing clearer explanations could alleviate this issue."

"It would be nice if Kiteworks could provide a free version of the platform so that it could be used for a certain number of file transfers. We could be charged a fee if we exceeded the number of allotted file transfers."

"Perhaps there could be a notification to users about their bandwidth or network packet loss."

"The one feature, which I have also requested directly to Kiteworks, is to have a scheduled upgrade function. Currently, one of my engineers logs in after hours for the upgrade. We're a hospital, and we're 24/7, but the primary users are seven to five. So, we log in the early evening just to push a button to tell it to do the update. It would be nice if that could be very easily scheduled."

"The search feature needs improvement. I can never find the information I need when I use it."

"The GUI is outdated."

"The permission management features need improvement."

"I would like to see the integration with Teams reinforced."

"Workflows could be simplified."

"This solution is not very stable. It is useful to arrange data but it's not the best for big data. Sometimes we have issues with our reports as a result."

"The user interface needs improvement because there is a lot of stuff in there. I use five to eight navigation buttons. It should be more user-friendly. Frequently used menu items should be arranged in a proper way. That would be helpful."

"Sharepoint doesn't integrate well with Oracle, and we use a lot of Oracle products at our company. Therefore, it makes more sense for us to go to Oracle instead of continuing to use Sharepoint."

"The price of Kiteworks is reasonable."

"The solution is very expensive because we are buying with Malaysian Ringgit and it's sold in US dollars."

"They changed it midstream. We were being charged a certain flat rate for SFTP traffic. For whatever reason, at the beginning of the year, our pricing changed, and we are now being charged more for using a feature of the product than we were when we first bought it. That has been our experience with billing. It turned out to be more expensive than when we started with it."

"The license management is changing and confusing. If I could make one change to it, it would be better license management through the API."

"It is not really expensive. I mean, to me it's obviously expensive, but it's worth it."

"I believe it's a little costly, but given the faith that we put into it from a security perspective to maintain the integrity of our patient information that is being transferred through this system, that's a small price to pay. So, on the surface, it might look like a lot of money, but depending on the need for security, which is where we feel it shines, it's okay price-wise."

"One of the reasons why we don't recommend the cloud version of SharePoint is the cost. With the on premise version, you pay for the license once. For the cloud version, there is a recurring fee. It is very expensive. They expect everyone to pay $20 or $30 per user per month."

"It can be expensive for on-premises deployments, especially when you have to support SQL Server as your backend database. That's where the cost comes into play. SQL Server has its own licensing, which Microsoft keeps on changing. Therefore, it can become costly. In the earlier versions of SharePoint, version 2007 or 2010, they had an express version where the SQL Server licensing was free. It wasn't like a full-blown SharePoint. It was only a slimmed-down version. It used to be whatever your hardware costs. You would install the free software and work with it, but you were very limited in what you could do in SharePoint. If you wanted the SharePoint Enterprise Server with all the bells and whistles, then you had to pay more to get the SQL Server license based on the number of users or servers. The subscription model is different for cloud deployments. Licensing is per user and per month. The cost also depends on the storage required. If you have a lot of sites or documents, then you need to expand it based on your needs."

"There are some aggressive discounts offered by Microsoft for organizations that are not for profit, which we are, and it makes it quite attractive to consider."

"Pricing plans may be flexible depending on volume usage and your corporate relationship with Microsoft."