AWS Wickr Reviews

We use several products from Amazon, such as S3 with event triggers, EC2 instances, and many other products in our day-to-day work. We also use Azure Functions and DevOps pipelines.

I have not used API Axway, but I have worked with Amazon API Gateway, which functions similarly to a gateway server. I have worked with the same technology where Amazon has a similar tool, which is an API gateway that is built the same way as Axway API Gateway.

I have been using this technology since 2018, which is approximately seven to eight years.

Our current enterprise has purchased the Amazon enterprise and AWS enterprise completely, so we simply use it.

Most of the deployment is straightforward because we do not have to think much about it. We use OpenShift with Helm and other tools for production deployment. Once all our test cases and pull requests are passed and reviewed, everything is done, making it easier for us.

We perform both DevOps and development jobs here currently and have also deployed some applications to our production.

We use SQS for messaging services and also use Kafka currently. It depends on the team. For one of my requirements, we have used Kafka, and for something else, we have also used SQS.

AWS has infrastructure as a service, which means we do not have to worry much about it. Fast provisioning and everything is straightforward. EC2 instances are already available with auto-scaling and other features. The end-to-end experience is quite comprehensive. We do not see DDoS attacks, and even when disaster management has occurred, the AWS server has not gone down at our site location. AWS Wickr is much faster and provides good benefits overall.

The interface is very direct when compared to Azure and not overly complicated. It is straightforward and easy to use. However, I feel the cost could be improved. Additionally, AWS Wickr could introduce new AI features, which might be helpful given that AI is everywhere.

I have been using this product for quite a long time, approximately four to five years.

The customer service rating is a 10 out of 10. They will connect within a minute. Even when we raise a complaint, because of our package, they will consider it and reach out soon.

We follow a standard deployment schedule and deploy at a specific day and time. At the time of deployment, everything has to be ready. If everything is ready, it may take approximately 45 minutes to one hour. If not, we have to postpone our schedule and send a notification to the users about maintenance.

For deployment, we always know what comes through because we have three environments to test: development, test, and production. We only proceed to production once everything is working fine in development and test. We have CloudFormation and other templates which handle all those details, such as changing instances or auto-scaling if migration is needed. All those details are quite straightforward.

All our data are more secure, so we use the private cloud. AWS Wickr provides quite good service and functionality. I would rate the overall review a 10 out of 10.

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.

My main use case for Wickr is for secure communication, particularly when we want messages to disappear after a few days or even a few hours. We typically use Wickr for our more sensitive projects.

One of the good examples is being able to discuss and pass around sensitive data such as encryption keys and client secrets for projects, especially environment files. This makes the process much quicker. We do also have password managers such as Bitwarden that we use to send configs to each other, but that can be significantly slower. Using Wickr is much more instant, so we can chat instantly and then send secure information knowing that it's going to be removed very soon and it's encrypted.

That covers my main use case.

Wickr has positively impacted my organization by speeding up the processes we have, especially during secrets transfer. Being able to spin up environments and message the entire engineering team a secret file and have them immediately see and consume it has definitely helped, though we don't really have any formal metrics around that.

When I say it helped with speed, I would estimate it made those processes about 10 to 20% quicker across the team.

The best features that Wickr offers, in my opinion, include the security-first approach. With most workplace messaging tools, the primary focus is productivity and collaboration, whereas Wickr seems to be built around secure communication. I particularly appreciate the concept of end-to-end encryption and being able to control how long messages remain accessible. From an engineering perspective, which is my background, I can see the value of that when dealing with information that shouldn't necessarily remain in chat history indefinitely.

It is quite easy for my team to manage those features in day-to-day use. Most people are already familiar with messaging applications, so there shouldn't really be a steep learning curve to send a message or share information securely, and in my opinion, there isn't. The bigger challenge is often getting people to adopt another platform when they're already comfortable with tools such as Teams and Slack.

One area I would be interested in seeing Wickr developed further is the integration with existing workplace tools. In software engineering, we rely heavily on systems such as Jira, GitHub, and Teams. Having another communication platform can create some fragmentation between them. Anything that makes Wickr easy to incorporate into these existing workflows would be really valuable.

Adoption is another improvement needed, though that's a real challenge. A product can have excellent security features and be amazing, but it only becomes useful when other people you need to communicate with are also using it. For organizations already heavily invested in another messaging platform, it's an additional hurdle to get them over.

I have been using Wickr for around two to three years now. I wouldn't really describe myself as a power user, but I've used it enough to get an initial impression of the platform and its approach to privacy and how it works for us at Cloudhouse.

Wickr has been stable in my experience. The things I look for are consistent message delivery, notifications, and a good experience across devices, and they seem to work and do what they need to for me.

Wickr scales fine in my organization with no issues.

I have never had to interact with customer support, so I cannot comment on that.

I mentioned earlier that we used and still do use Bitwarden password manager for sending secure things and sharing notes between the team, but that is significantly slower.

The return on investment is just time saved, as I mentioned before, around 10 to 20%.

I haven't been responsible for purchasing or managing Wickr licenses, so I cannot really give a detailed assessment of its pricing. I think its value depends heavily on the organization. If secure communication is a major business requirement, then a dedicated platform such as Wickr is worth the additional investment in my opinion.

If you're particularly concerned about security and data privacy, then Wickr is particularly important. It's especially relevant for teams dealing with sensitive information or those who require more control over communications. However, for everyday software development collaboration, I would probably still lean towards Teams or Slack.

Regarding Wickr's AI capabilities, I haven't noticed its AI capabilities in particular, but it does have end-to-end encryption, so it's quite secure. It seems very reliable and accurate, and I would hope all my messages are always being encrypted.

I rate Wickr an 8 out of 10. The reason I rate it an 8 is that it's very useful for its specific use cases, but there are definitely some improvements needed around integrations and adoption that I think could be helpful.

My main use case for AWS Wickr is encrypted messaging.

A specific example of how I use encrypted messaging with AWS Wickr is communicating back and forth with government agencies in collaboration with them when we potentially place artist candidates in government roles.

AWS Wickr offers excellent features that include support for group chat in addition to video calls and file sharing of higher gigabyte load than most comparable solutions, which is very useful, along with screen sharing.

AWS Wickr has positively impacted my organization by providing a helpful encrypted solution for matters of this sensitive nature.

It has definitely improved efficiency, lowered risk, and made communication easier, especially in the sense that larger files can be shared so readily and securely between parties.

I am not certain how AWS Wickr can be improved further.

I have been using AWS Wickr for one year.

AWS Wickr appears to be stable based on my experience.

I am not entirely qualified to answer how AWS Wickr's scalability performs, but based on my instincts and good experience with similar solutions, it seems as though it would be pretty scalable, though it would take some training adjustments perhaps to make it a little more user-friendly to novices.

The customer support is strong, clear, and concise, and I have never had a lingering problem.

I would rate the customer support as a ten on a scale of one to ten; I have never had an issue.

I have seen a return on investment with AWS Wickr; it definitely saves time, and while I do not know about fewer employees, I think it definitely boosts confidence, security, and lowers liability in terms of its ephemeral messaging and all of the security features.

I would rate AWS Wickr a nine on a scale of one to ten.

I chose nine because I think that there is a little bit of a steeper learning curve associated with it than I would have expected, but it is very operationally efficient and powerful, and there is nothing ultimately wrong with it.

Regarding AWS Wickr's AI capabilities, I think it has a really strong data retention policy in terms of what is private and how things are managed and kept secure and kept flowing with good momentum, so it all seems sensible to me.

Regarding AWS Wickr's AI capabilities, it seems to be about as accurate as something of this nature you would think would be at a high level; it is much better, and it is not as crude as a lot of the other inaccurate or improvisatory things out there that are similar; it is pretty accurate.

The advice I would give to others looking into using AWS Wickr is that I think whatever training can be provided by a native user as opposed to by the system itself would help, just to make sure that the learning curve is not as steep as perhaps it was for me jumping in on my own; otherwise, I do not have anything to share.

My overall review rating for AWS Wickr is nine.

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.

A specific example of how AWS Wickr was used for secure communication in my setup is that it is mainly important for file sharing. It is not possible to intercept the files during the sharing process, and it uses an encryption mechanism to send the files.

I primarily use AWS Wickr for secure communication and file sharing, along with group chat and one-to-one chat capabilities.

Regarding the features, we can add a user as an administrator in AWS Wickr. As an administrator, we can add users, create users, and manage or delete users. It is easy to manage users as a login administrator to AWS Wickr.

AWS Wickr has impacted my organization positively as it ensures the security of communication and has helped us avoid security threats for the company. I measure those security improvements by noting that after using AWS Wickr, we have not received any complaints or security threats, such as DDoS attacks or man-in-the-middle attacks.

Overall, AWS Wickr has more features and I am satisfied with the product.

Regarding AWS Wickr's AI capabilities, I think it ensures the security of communication and satisfies the governance and security requirements as it aligns with the governance policies and security protocols. When discussing AWS Wickr's accuracy and reliability of output, I have not encountered any issues with accuracy, and I find it to be more reliable.

We use AWS for AWS Wickr. I recommend this product because it ensures communication between organizations and is easy to manage with a few employees. Therefore, I suggest that companies obtain this product to ensure security from threats during communication and file sharing, particularly for internal communication.