FileCloud vs Kiteworks comparison

"The granularity for the audit log in FileCloud is extremely valuable."

"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 benefits that Kiteworks has provided to its customers in terms of data sovereignty."

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

"Scalability is impressive."

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

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

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

"Currently, FileCloud's compatibility for Linux implementation is limited to only Ubuntu or Red Hat Enterprise Server."

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

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

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

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

"I noticed the Kiteworks login UI is very basic, lacking customization. Allowing more HTML tags to add hyperlinks or user-friendly information on the home page would be very useful."

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

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

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

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

"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 price of Kiteworks is reasonable."

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