What is our primary use case?
We use it for three big use cases. The first use case is large files that are too big for email attachments, which is capped at 25 megabytes by the email protocol. If we want to send really large files and don't want to use Google Drive for that, because we're collaborating with someone who doesn't have Google Drive, then we use Kiteworks.
We also use it to send secure information such as credit card numbers or passwords; Things that we don't want to send over email or Google Drive or Box or the like.
And we use it for customer interactions, such as sending log files back and forth.
How has it helped my organization?
It gives us a secure way of communicating with our customers, when necessary.
Kiteworks also helps us demonstrate compliance with data privacy regulations. That's a necessary function for us and it fills that need.
What is most valuable?
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.
In terms of sensitive content, we can see the "to" and "from," but we don't see what the content is. We don't want to be able to see the content. We need a level of security and privacy. But being able to see the "to" and "from" is useful for troubleshooting.
It also helps protect our customers' privacy.
For how long have I used the solution?
This is year five. We switched over in 2018.
Buyer's Guide
Kiteworks
February 2025
Learn what your peers think about Kiteworks. Get advice and tips from experienced pros sharing their opinions. Updated: February 2025.
838,713 professionals have used our research since 2012.
What do I think about the stability of the solution?
It's stable. We haven't had any outages or downtime due to bugs.
What do I think about the scalability of the solution?
It's held, so far, at our size. I don't know if it would scale to a company 10 times our size. We would have to run multiple instances in that case. We have thousands of employees and we have licenses for about two-thirds of the folks.
How are customer service and support?
Their tech support is pretty helpful. They get back to us in a decent amount of time. I would put them at an eight out of 10.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We used Biscom. We switched to Kiteworks because of a security concern about the former tool. There may have been a breach or a vulnerability that they couldn't resolve in time for us and that caused us to move off of it.
How was the initial setup?
The initial deployment was straightforward. We have it deployed on-premises and in the public cloud on Amazon. We have two instances.
And in terms of maintenance, we have to do upgrades or updates when new software is available.
What about the implementation team?
We did it ourselves with assistance from their support team. We didn't pay for any services.
What was our ROI?
It's worth the money we pay.
What's my experience with pricing, setup cost, and licensing?
The license management is changing and confusing. If I could make one change to it, it would be better license management through the API. Currently, there's a license cap and you can't go over it. And removing licenses from users requires you to completely delete their account now, which we are hesitant to do.
Which other solutions did I evaluate?
One of the reasons for using Kiteworks for securing sensitive information, rather than Box or Microsoft OneDrive or another ECM system, is that it gives us complete internal control of the system.
What other advice do I have?
The fact that Kiteworks provides a unified and secure way to share sensitive content with third parties is of medium importance to us. Having a strategy where we have multiple avenues of communication is our preferred way. We have regular email, we do Slack, we have Google Drive, and Box. We are not looking at Kiteworks to be the single, unified communication platform. It's playing a role in a stack.
My advice is to look into the licensing structure.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.