![Wickr [Private Offer Only] logo](https://d7umqicpi7263.cloudfront.net/img/product/30576b35-0151-4566-954f-dd1f8585826a.png)
Wickr [Private Offer Only]
Secure communication has protected sensitive audits and now supports fast cross‑team decisions
What is our primary use case?
My main use case for AWS Wickr is sharing information that is very sensitive with key stakeholders.
A specific example of how I have used AWS Wickr for sharing sensitive information with key stakeholders is that AWS Wickr provides the flexibility to integrate with open-source tools. In our organization, we have integrated it via Slack and some other Hangouts specific channels, allowing us to share key data points with the finance team. For example, when we conduct certain audits, we share sensitive details such as organizational sales figures or other key metrics.
I have covered all aspects of my main use case, including communication across key stakeholders, which spans multiple verticals such as finance, planning, replenishment, and multiple teams.
What is most valuable?
The best feature in AWS Wickr is its end-to-end encryption model, which provides enhanced data security and confidence regarding data breaches.
The end-to-end encryption in AWS Wickr impacts my day-to-day work by helping me gain confidence while sharing sensitive data points with internal team members or key stakeholders outside the company domain. Beyond encryption, the ease of use along with the functionalities it provides is commendable.
AWS Wickr has positively impacted my organization in multiple ways. We received very positive feedback from our stakeholders and external partners regarding the ease of use and the functionalities and features it provides, along with frequent updates that allow us to implement improvements regularly.
What needs improvement?
AWS Wickr still has good scope for improvement in terms of feature enhancement. There are additional features that can be added, such as external domain support. For example, Chroma, one of our external clients, has not fully adopted it yet.
Regarding needed improvements, a strong community exists within AWS where users can reach out with their queries or if they encounter difficulties using any functionality. This community really keeps people engaged and updated on how we can continuously improve.
For how long have I used the solution?
I have been using AWS Wickr for more than one year.
What do I think about the stability of the solution?
AWS Wickr is stable.
What do I think about the scalability of the solution?
We were able to scale AWS Wickr to a larger extent, so I definitely vouch for its scalability.
How are customer service and support?
Customer support for AWS Wickr is quite good.
Which solution did I use previously and why did I switch?
Previously, we were using legacy chat channels such as Hangouts and Slack. When we saw the benefits and advantages of AWS Wickr, we transitioned to it.
How was the initial setup?
AWS Wickr was the only tool we evaluated before choosing it. It was preferred by both our team and our leadership. After conducting a small proof of concept, we immediately converted this into a full-time tool for our organization.
What was our ROI?
I have seen a return on investment with AWS Wickr, as it saves a significant amount of time. We do not have to worry about what kind of data we are sharing, and AWS Wickr takes care of hashing and securing it, which is definitely a major benefit. While the return on investment is not measurable in concrete terms, it still eases and speeds up day-to-day activities.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for AWS Wickr has been seamless. The pricing is quite competitive compared to any of its competitors, the setup cost was very straightforward, and AWS provided good support wherever it was needed. We have used the pro version and recently upgraded as well.
What other advice do I have?
On a scale of one to ten, I rate AWS Wickr around nine.
I chose nine out of ten because there is always scope for improvement. As adoption increases, ease of use across domains or organizations would be really helpful.
My advice to others looking into using AWS Wickr is to proceed with it. Initially, you will see the kind of benefits it can bring, as the pricing and other aspects are competitive, and the features and broad community it provides will be really helpful for any organization. I give this product an overall rating of nine out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Secure messaging has protected our internal releases and supports confident daily collaboration
What is our primary use case?
AWS Wickr is used for end-to-end encrypted messaging, voice and video calls, and file sharing. The main advantage that I appreciated about AWS Wickr is that no one is able to see the message regardless of the sender and receiver.
A specific example of how my team uses AWS Wickr in our daily workflow is that previously we shared logs and screenshots directly over Teams, but with AWS Wickr, we can be assured that the developers, QAs, and PMs can discuss features, bugs, and releases securely, with no risk of leaks when sharing logs, screenshots, or test builds.
AWS Wickr is used for sharing logs and crash reports, sending test builds, secure calls, and screen sharing, and it has been helpful.
What is most valuable?
The best features AWS Wickr offers are end-to-end encryption, admin controls, compliance and retention policies, and user management. It fits the need for secure internal communication. Of those features, I find myself relying on the end-to-end encryption the most.
During the setup of AWS Wickr, I created the application from the AWS console, assigned the admin IT roles, and configured the user provisioning. What I appreciated was the easy onboarding, role-based access, and secure authentication. I set up different roles including mobile dev, backend, QA testing, and release management, which freed me from all the risk of release leaks.
AWS Wickr has positively impacted the organization as the features being used have made us confident that the resources we share are not going out of the organization and are not being leaked. AWS Wickr was rolled out to teams including mobile, QA, and product, deploying Wickr apps on iOS, Android, and macOS, and onboarding teams with usage guidelines, security best practices, and guidelines for shared data. It has been beneficial.
What needs improvement?
AWS Wickr was not embedded directly into the mobile app; instead, it was used as a secure internal collaboration layer for the development and operation teams, which supported secure coordination around mobile development, testing, and releases.
For how long have I used the solution?
AWS Wickr has been used for the past three months and has been really great.
How was the initial setup?
During the setup of AWS Wickr, I created the application from the AWS console, assigned the admin IT roles, and configured the user provisioning. What I appreciated was the easy onboarding, role-based access, and secure authentication.
Which other solutions did I evaluate?
Currently, while using AWS Wickr, I have not found any other app in the marketplace that provides the same features, so this is the best option.
What other advice do I have?
My advice to others looking into using AWS Wickr is that all that is needed is the integration part; if integration is sorted, then just create rooms in the AWS console and start using it. The difference will be apparent. I would rate this product a 9 out of 10.