No more typing reviews! Try our Samantha, our new voice AI agent.

Share your experience using Plutora

The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.

Use our online form to submit your review. It's quick and you can post anonymously.

Your review helps others learn about this solution
The PeerSpot community is built upon trust and sharing with peers.
It's good for your career
In today's digital world, your review shows you have valuable expertise.
You can influence the market
Vendors read their reviews and make improvements based on your feedback.
Examples of the 118,000+ reviews on PeerSpot:

PeerSpot user
DevOps Engineer
Real User
Nov 17, 2026
Automated test-driven promotions have reduced manual deployments and improve release control
Pros and Cons
  • "Akuity Platform also helps us manage Argo CD, including scaling, managing, and security."
  • "We have not been using Akuity Platform for a long period."

What is our primary use case?

Our main use case for Akuity Platform is automation based on test results. When we came up with this approach, we started using Akuity Platform, where our Argo CD helps us automate based on the test results in each environment. For example, if I want to publish a build and it passes the test cases, it goes to the next stage. We don't have this kind of check otherwise. As we have many clusters, they are tough to manage, so we started taking help from Akuity Platform.

Here is a specific example of how we use Akuity Platform in our workflow. Every time we need to deploy the services, the developers first push their code, and the code is deployed. Once it is deployed and all the test cases pass, we release the build to QA2 and QA3. The QA2 publish and QA3 publish are manual, and we need to publish each service one by one. To overcome this situation, we have our developer regression test. On top of that, we have all the test case results, and based on them, we get the result. Argo CD runs some test cases.

Once it passes, the build goes to the higher environment. After that, it goes to QA3. If everything passes and the test results are as expected, the build automatically goes to the next environment. Otherwise, it publishes the older version as required. If everything is successful, we don't need to manually go and publish all the time. We can release it in one click.

Beyond our main use case, in general, Akuity Platform helps us manage Argo CD, including scaling, managing, and security. If we deploy hundreds of applications at a time, it can sometimes crash. Akuity Platform also helps us with automation, similar to Argo CD.

How has it helped my organization?

From a DevOps standpoint, Akuity Platform has had a positive impact on our organization. Instead of promoting each service, Argo CD helps us promote the entire project, which has multiple services. It depends on the success rate. It used to publish to another environment. After deploying, we need to wait for the pod to come up before moving forward.

What is most valuable?

The best features of Akuity Platform are many, and it offers promotions from one environment to another. It can also manage ECR repositories, for example when any new versions are deployed. It has a Freight approach that shows the last 10 or 15 versions, and we can pick any version at any time. We can achieve many different features that are not available in Argo CD.

These constraints and feature management have helped us when we release. For example, when we merge one of my repositories, it takes from the CI each time, and I have seen Async-related issues. When we go to Argo CD management, it manages this, which helps us scale up and scale down.

Freight is another feature of Akuity Platform, where we can see the last 10 or 15 Docker containers.

For how long have I used the solution?

We have not been using Akuity Platform for a long period. Initially, we started with Argo CD, and we have been using these services for six months.

What other advice do I have?

My thinking on Akuity Platform is clear: it is a good platform. We got to know that it is a test panel.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Last updated: Nov 17, 2026
Flag as inappropriate
reviewer2926467 - PeerSpot reviewer
Software Engineer at a tech vendor with 1,001-5,000 employees
Real User
Nov 17, 2026
Feature flags have enabled safe incremental rollouts and faster incident mitigation
Pros and Cons
  • "LaunchDarkly has positively impacted our organization because, as I mentioned, it is a reliable service and does what it is advertised to do."
  • "LaunchDarkly can be improved because there are often feature flags that default to true for a very long time, and we accumulate such feature flags over time."

What is our primary use case?

I mainly use LaunchDarkly for live feature flag management.

A specific example of how I use feature flags in production is making app parallelism in some part of the code a configurable feature flag on LaunchDarkly. We can then set the number of parallel threads to a higher amount during an incident or outage to resolve the incident quickly. Similar adjustments can be made with other parameters as well.

Roles are assigned to the engineers and various other people in the company, which determines who has permission to change production flag values during an outage. Usually, the developers have the right to change the feature flags. Developers are the only ones with access to LaunchDarkly; other people do not have access. Those developers can view the feature flags and possibly change them as well.

In addition to my main use case, we also use LaunchDarkly for making incremental changes to code, ensuring that we do not break anything.

With AI coding tools helping our team ship code faster than ever, we do incremental rollouts using feature flags, as I already mentioned.

AI-assisted coding has not really changed the way we release with LaunchDarkly; the workflow remains the same.

We use GitHub as an integration with LaunchDarkly.

What is most valuable?

The best feature LaunchDarkly offers is the SDK integration, which I suppose is very good. That is the best one.

What works especially well for our team is reliability. Reliability is key here.

LaunchDarkly has positively impacted our organization because, as I mentioned, it is a reliable service and does what it is advertised to do.

In terms of outcomes, when making large changes in the logic of code, we use feature flags for incremental rollout. That leads to fewer incidents and faster mitigation via the parallelism example that I mentioned.

What needs improvement?

LaunchDarkly can be improved because there are often feature flags that default to true for a very long time, and we accumulate such feature flags over time. We would like to clean them up, but there is no good way of doing that using LaunchDarkly. I believe there could be a separate tab for just that.

For how long have I used the solution?

I have been using LaunchDarkly for my entire period of time, which is five months.

What do I think about the stability of the solution?

In terms of stability, LaunchDarkly is stable.

What do I think about the scalability of the solution?

LaunchDarkly's scalability is great.

How are customer service and support?

The customer support for LaunchDarkly is good too.

On a scale of 1 to 10, I would rate the customer support eight out of 10.

Which solution did I use previously and why did I switch?

Before LaunchDarkly, we had an in-memory cache and an in-house solution, but it was not great.

The limitations and difficulties with that in-house solution that led us to switch to LaunchDarkly were that it was hard to maintain and had reliability issues.

What was our ROI?

I have not really seen measurable improvements in metrics such as token spend, latency, or evaluation scores since implementing LaunchDarkly.

What's my experience with pricing, setup cost, and licensing?

We did not purchase LaunchDarkly through the AWS Marketplace. We purchase it separately.

Which other solutions did I evaluate?

I was not the one who chose LaunchDarkly.

When compared to alternative solutions, LaunchDarkly stood out because it was very reliable and scalable.

What other advice do I have?

On a scale of 1 to 10, I would rate LaunchDarkly an eight overall.

I give it an 8 out of 10 for the reasons I already mentioned: it is a good service, but there are a few gaps.

The advice I would give to others looking into using LaunchDarkly is that it is a great product. You must at least try it.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

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.
Last updated: Nov 17, 2026
Flag as inappropriate