Kiteworks vs Microsoft Office SharePoint Server comparison

"The most valuable feature is the ability to send a large file of 30 GB in size and more. In Outlook and other email applications, you cannot send files that are larger than 20 MB. But with Kiteworks, 30 GB is transferable by default and, with the proper approval, a file of up to 100 GB can be sent. It makes file transfer very easy and smooth."

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

"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."

"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."

"The best part of this solution is that we can generate multiple reports about how the data is transferred and about user information or IP."

"The most valuable feature is the ability to allow end-users to manage their own information and data with minimal administration. That's the best feature from my perspective."

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

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

"Ability to collaborate with others in one location."

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

"The solution is pretty easy to use for the most part."

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

"The collaboration, the ability for multiple users to work on a single document."

"The support from Microsoft is very quick and they are very proactive."

"It's a very robust product."

"The implementation and configuring of the resolution are very easy in the online version."

"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."

"File location could be improved."

"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."

"In my experience, their technical support can be a little slow."

"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."

"We have experienced a few hiccups and bugs when using the admin console and from a user perspective."

"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."

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

"The permission management features need improvement."

"The ability to preview files in different formats should be expanded to include formats such as embedded postscript (EPS), AutoCAD, and Adobe Acrobat PDF."

"The solution is like a CRM, so the initial setup is complex. It takes a few days to deploy the solution and the length of time depends on how large the company's topology is and what the client's demands are."

"It is a bit restrictive to develop in the cloud version. A lot of features are in the cloud now, and you have to develop on the outside. As far as the platform and the programming side of things are concerned, it is moving more towards configuration management rather than programming. When we are doing solutions, we are basically just configuring it to make solutions happen rather than actually using the Visual Studio code and developing from scratch in the cloud. It is almost like creating an app. You have created an app for your phone, but the app doesn't really sit on your phone. It sits somewhere on a server, and the database sits on another server. The app is just pulling and pushing information. The whole development has changed. We used to install things directly on the server and then run the application from the server. Now, it is more of a modular architecture."

"I would like to see more Agile techniques and seamless integration with other applications."

"Workflows could be simplified."

"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 search feature needs improvement. I can never find the information I need when I use it."

"The price of Kiteworks is reasonable."

"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."

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

"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."

"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."

"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."

"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."

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