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:

Parth Kalsi - PeerSpot reviewer
Software Engineer at a tech vendor with 501-1,000 employees
Real User
Top 20
Nov 21, 2026
Feature flags have accelerated data pipeline releases and make controlled rollbacks simple
Pros and Cons
  • "Our deployment speed has increased by about 30% since we started using LaunchDarkly."
  • "The reason I give LaunchDarkly an eight, rather than a 10 or a lower score, is that the rules can sometimes be confusing in the UI."

What is our primary use case?

Our main use case for LaunchDarkly is managing our releases and introducing new features to our data pipelines. We put our new features behind LaunchDarkly flags, which helps us enable or disable them at will, so that we can run our data pipelines with or without those features. That makes rollbacks very easy, and it also helps us with A/B testing. This is important for us because we need to make sure that our data pipeline produces correct data. If, for example, any feature messes up the data, we can disable it, run the pipeline again without that code path, and get the correct data that we generate. That is how we use LaunchDarkly.

We mostly use it in that way.

With AI coding tools helping our team ship code faster, LaunchDarkly helps us maintain control once that code hits production by making our deployments very precise. Using the rules we can set in each flag, we can precisely enable a flag for a few test tenants or test users first. If everything goes fine with them, they do not report any issues, and we do not see any difference in our own metrics, then we go ahead and deploy it or enable it for everyone.

With AI tools helping us write some of our code, we now create a lot more flags with LaunchDarkly, and we also do a lot more cleanup. I think that is expected when you have this velocity.

We do not use integrations such as AWS, GitHub, Sentry, New Relic, Anthropic, or others with LaunchDarkly.

How has it helped my organization?

Using LaunchDarkly for feature flags and A/B testing changes my day-to-day workflow by reducing the tiring work of constantly merging our changes and then reverting them. We do not have to go through all of those merge and revert MRs when we use LaunchDarkly flags, so it speeds up the whole process.

LaunchDarkly has impacted our organization positively by helping our entire organization move faster. It helps us deploy features faster. I think one of the most important capabilities is that you can do a lot of differentiation. For example, we use Apache Airflow, where we have multiple DAGs, and inside those DAGs we have multiple tenants. We can specifically disable or enable a feature for one particular DAG. Before rolling out to all tenants or all the DAGs, we can precisely run the feature for one of the tenants, verify it first, and then do a wider rollout. Staged rollout is also one of the features that helps a lot.

Our deployment speed has increased by about 30% since we started using LaunchDarkly. We are rolling out more features sooner because we have the option of doing staged rollouts and of quickly reverting the features that do not work as intended.

Since implementing LaunchDarkly, I have seen measurable improvements, and the latency has improved.

What is most valuable?

I think the best features LaunchDarkly offers are the dashboard, which is very helpful, and the different environments you can create. All of those environments get evaluated differently, so we do not have to make any differentiation in the code itself. Depending on the environment the request originates from when it checks the value of the flag, LaunchDarkly automatically makes sure that only the value for that environment is served. That is very useful. The dashboard is also very useful for seeing all the flags we have and for later cleanup if we need to delete any flags. We also have the audit history, which shows who turned on a flag, and that is very helpful as well.

The audit history and environment separation features help our team in practice because we sometimes need to differentiate between environments. We have a pre-prod environment before prod, so we can usually turn the flag on or off in pre-prod and test. That is where the differentiation of environments helps. The audit history is helpful because we are a cross-functional team, and there are teams that create their own LaunchDarkly flags so they can enable or disable them. We can know who is enabling or disabling a flag and make sure we have an audit, at least, so that we can point out who has flipped the flag.

What needs improvement?

I think LaunchDarkly can be improved in the hierarchy of some of the rules we set to precisely enable or disable some DAGs. It is not very intuitive. The way it is shown, you would not know that the order of those rules matters.

From what I have noticed, that is the only improvement that would help.

For how long have I used the solution?

I have been using LaunchDarkly for the past year.

What do I think about the stability of the solution?

LaunchDarkly is pretty stable. The uptime is good, and I do not have any issues with uptime.

What do I think about the scalability of the solution?

LaunchDarkly's scalability is strong because we have not faced any issues, even with a million requests per day for most of the flags. It is pretty scalable.

How are customer service and support?

We never contact customer support because we mostly do not have to.

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

Before LaunchDarkly, we were not using any solution, to be honest. We were introduced to this new category of product, which is staged rollout and related capabilities. It is a new solution that our organization came up with to increase deployment speed and reliability.

We do not use any previous or different solution, so LaunchDarkly is our first.

What was our ROI?

I would say LaunchDarkly has saved a lot of time, and it is not that expensive either. We have saved about 20% of our time, since we would otherwise be unnecessarily spending it on reverting rollouts to production.

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

The IT team handles all the purchases.

Our experience with pricing, setup cost, and licensing is fine. We are on the Enterprise plan with around 120 seats, which is fine for us.

Which other solutions did I evaluate?

When comparing LaunchDarkly to alternative solutions, I am just an engineer who leads the way. In terms of competitors, we are not aware of many. LaunchDarkly is the one that came up, and we just got to work with it.

Before choosing LaunchDarkly, we did not evaluate other options.

What other advice do I have?

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

The reason I give LaunchDarkly an eight, rather than a 10 or a lower score, is that the rules can sometimes be confusing in the UI. If that were fixed, it would help. Other than that, LaunchDarkly is stable most of the time, so there is very little downtime, except for a few times. That is why I give it a solid eight.

I think LaunchDarkly is doing a decent job of disclosing its AI capabilities, governance, and security. However, it is still a black box to most users how it is being managed.

We do not use LaunchDarkly's AI capabilities a lot. From what I have heard from my colleagues on some of the teams, it is decent, albeit a bit expensive.

LaunchDarkly is deployed in our organization on public cloud only.

The ops team will know exactly where they have deployed it, but we are mostly using AWS.

My advice to others looking into using LaunchDarkly is to make sure that, since you are doing so many releases or deployments, you have a way to go back and revert those changes. That helps you quickly fix whatever issues might arise due to the volume of MRs that are being merged.

Which deployment model are you using for this solution?

Public Cloud

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

Amazon Web Services (AWS)
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 21, 2026
Flag as inappropriate
PeerSpot user
DevOps Engineer
Real User
Top 20
Nov 18, 2026
Automated test-driven promotions have reduced manual deployments and improve release control
Pros and Cons
  • "Akuity Platform simplifies Argo CD management by providing centralized control, improved scalability, security, and high availability. It reduces the operational overhead of maintaining the Argo CD infrastructure, while making it easier to manage multiple Kubernetes clusters, monitor application deployments, and maintain consistent deployment workflows across environments"
  • "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 QA3 and QA2. The QA3 publish and QA2 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 perspective, Akuity Platform has significantly improved our deployment and release management process.

One of the key benefits is that instead of promoting individual services separately, we can promote an entire project consisting of multiple microservices across different environments.

The promotion process is based on predefined success criteria and verification results. After deploying to an environment, the platform waits for the pods to become healthy and the required checks to pass before allowing the promotion to proceed to the next environment.

This helps us automate deployments, reduce manual intervention, ensure deployment stability, and maintain consistency across environments.

What is most valuable?

One of the best features of the Akuity Platform is its release promotion and artifact management capabilities. It allows us to promote releases from one environment to another based on predefined conditions and verification results.

Another useful feature is its integration with container registries such as Amazon ECR. Whenever a new Docker image version is published, Kargo can discover and track that version as a new Freight.

The Freight feature is particularly helpful because it maintains a history of available releases. We can view the previously published versions, select a specific version, and promote it whenever required. This also makes it easier to roll back to a previously stable release.

Akuity Platform also provides better management of Argo CD at scale. Instead of handling all the operational aspects of a self-managed Argo CD setup, we can use Akuity's managed platform to reduce control-plane maintenance and operational overhead.

Overall, features such as Freight management, environment-based promotions, verification, release history, and centralized Argo CD management help us improve deployment consistency, simplify release management, and reduce manual effort.

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 18, 2026
Flag as inappropriate