AWS Wickr Reviews

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.

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.

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.

I have been using AWS Wickr for more than one year.

AWS Wickr is stable.

We were able to scale AWS Wickr to a larger extent, so I definitely vouch for its scalability.

Customer support for AWS Wickr is quite good.

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.

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.

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.

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.

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.

At Franc Farms, our main use case for AWS Wickr is out-of-band mission-critical coordination. While our primary data flows, such as our mango passports, telemetry, and supply chain auditing, are managed through our sovereign containerized infrastructure, we utilize AWS Wickr as our secure private channel for high-stakes operational communication.

Recently, we faced a logistic disruption involving a high-value shipment of processed mango products intended for our partner. Due to a sudden change in export regulations, our standard documentation had to be revised on the fly, and the shipment was held for inspection. AWS Wickr was essential for real-time documentation because we needed to share revised custom declarations and proprietary certificates of origin with our logistics lead immediately. Standard email was too risky due to the sensitive nature of the trade secrets and the financial impact of the delay.

Our primary sovereign infrastructure was focused on maintaining our mango passports traceability. We did not want to flood our system logs or standard communication channels with tactical, ephemeral chat. AWS Wickr provided a clean zero-trust workspace that allowed our team to coordinate the workaround without leaving a footprint in our permanent business archives.

The best feature that AWS Wickr offers our team is customer-controlled data retention. While we value privacy, we also have legal and regulatory obligations. AWS Wickr allows us to configure a private customer-controlled data store for information that must be retained for auditing or legal hold purposes. It acts as a secure BCC for our communications, and we can archive what we need for regulatory compliance without compromising the end-to-end encryption of the actual conversation.

When we engage in estate matters or supply chain disputes, legal hold used to be an IT nightmare. With customer-controlled retention, we can place a specific group of project channels on legal hold with a single configuration change. We do not have to worry about individual users accidentally deleting messages or losing evidence. It makes us significantly more professional and organized to our legal partners.

Open access capability is another important feature that serves as a hidden gem for operations in the field or in regions with restrictive network policies. AWS Wickr Open Access allows us to disguise our traffic as standard AWS traffic. If our team is at a remote site with a monitored or restricted public Wi-Fi connection, we can still maintain a secure tunnel back to our network. It is an always-on insurance policy for our connectivity.

The most immediate benefit AWS Wickr has brought to us is increased agility during incidents. Before AWS Wickr, if we had a supply chain hiccup or a minor infrastructure alert, we were reliant on email threads or consumer chat apps, which are inherently sticky and insecure. Now with our war room setup in AWS Wickr, we can deploy a secure, encrypted communication channel in minutes. It has reduced our time to resolution for logistical delays by nearly 40 percent because our team is not waiting for insecure fragmented communications to be cleared or decrypted.

The reduction in time to resolution has led to radical transparency for our partners. Customers today, especially high-end food processors, do not want just a delivery; they want visibility. From an operational impact perspective, if we resolve an issue in under two hours, we can report back to our partner with a solved status while they are still in their business day. This level of responsiveness makes us look an extension of their team. From a customer satisfaction perspective, it builds a predictability premium. Our partners know that if there is a problem, Franc Farms does not go silent. We communicate, we fix it, and we get back to business. This consistency is the number one reason we have seen such high retention rates in our B2B contacts.

User experience consistency across devices is something AWS Wickr can improve. We use a mix of workstations and mobile devices to manage the Franc Farms logistics. While core functionality is rock solid, we have noticed that the user experience can vary slightly between the desktop and mobile clients. Sometimes advanced administrative configurations are not as easily accessible on the mobile app as they are on the desktop, which can slow down our team when we are coordinating from the field.

We appreciate the customer-controlled data retention feature, but we would appreciate more granular visual analytics within the admin portal. Currently, it takes considerable effort to parse logs to see how our team is actually utilizing the tool, such as which groups are most active or what volume of file transfers looks like over time. More built-in dashboarding or visualization of communication metadata would help us better optimize our security policies without having to export raw data into internal analysis tools.

Currently, if our organization grows or needs to manage separate networks for different divisions, such as separate networks for Franc Farms logistics versus our R&D or bio-estates projects, the management can become fragmented. We would appreciate a global admin dashboard that allows us to manage policies, users, and data retention across multiple AWS Wickr networks from a single, unified view rather than logging into each network admin console individually.

I have been using AWS Wickr for one year.

AWS Wickr is stable in my experience.

It has not been particularly scalable for us since we are using a limited number of employees. However, due to its presence in the AWS ecosystem, scalability would be straightforward to implement.

The most significant metric for us was cost avoidance. In the agricultural export business, a single compromised communication regarding a shipping manifest or a regulatory certificate can result in shipment seizure, spoilage of goods, or heavy fines. We compare the annual licensing cost of AWS Wickr against the cost per incident of a potential data breach. By our internal estimates, preventing just one major logistics incident, which could cost us thousands in lost product and reputational damage, pays for our entire organization's AWS Wickr subscription. This is a strong return on investment from the moment a breach is prevented.

My advice to others considering AWS Wickr is to not deploy without a security policy. AWS Wickr is a powerful utility, but it is not a set-it-and-forget-it tool. Before you invite your first user, define your data lifecycle. Decide exactly what needs to be ephemeral and what needs to be retained for compliance. Segment your networks and use security groups to ensure that your internal management team, external auditors, and logistics partners operate in separate, siloed spaces. Never give everyone access to everything.

Aside from AWS Wickr being relatively affordable initially, you must ensure that you have a strong setup in place to maximize the benefits of AWS Wickr.

My overall review rating for AWS Wickr is six out of ten.

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.

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.

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.

AWS Wickr has been used for the past three months and has been really great.

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.

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.

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.