LaunchDarkly allows you to manage feature flags, progressive delivery, experimentation, and AI agents for teams building on AWS. Pay as you go, billed through AWS. Start with a 30-day free trial.
Move at AI speed. Stay in control.
LaunchDarkly is the runtime control platform for the AI era. Every change ships behind a feature flag with progressive rollouts, change-level observability, and automatic rollback when a metric regresses - no redeploy required.
Start with a free trial directly from AWS Marketplace and deploy alongside the AWS services you already build on.
Ship AI-built code confidently.
Guarded Releases monitor success and guardrail metrics in real time and roll back automatically - limiting blast radius on every release.
Govern AI agents in production.
Built to complement Amazon Bedrock and AgentCore: dynamically route invocations to the right model, roll out prompt and model changes with full targeting control, and revert in seconds. Teams set the guardrails, deciding per customer, at runtime, which model, prompt, and parameters each request uses.
Close the production loop.
With Kiro and the AWS DevOps Agent, agent-generated changes ship progressively and validate with experimentation before full production.
50T+ flag evaluations daily. 25+ SDKs, 80+ integrations. SOC 2, ISO 27001, ISO 27701.
Highlights
Ship AI-built code safely with progressive rollouts and automatic rollback
Govern AI agents on Amazon Bedrock and AgentCore - route models and revert in seconds, no redeploy
Free trial from AWS Marketplace - consolidate billing and draw down AWS spend commitments
Access real-time vendor security and compliance information through their Trust Center powered by Drata or Vanta. Review certifications and security standards before purchase.
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
This plan bills by usage across seven independent dimensions, with no seat or platform fees. Each dimension has its own free tier; you pay only for usage above it. Client-side MAU and AI Runs bill per thousand units. Logs and Traces bill per million units. Sessions and Errors bill per thousand units each month. Service Connections bill per connection. You can consume each dimension separately, so your cost scales with the specific activity you generate. The dimensions do not form tiers; they combine to reflect your total monthly usage.
Top-of-mind questions for buyers
What counts as one Service Connection, and how are short-lived processes billed?
A Service Connection is one server-side SDK connected to one environment for a month. Each unique pairing counts separately. Serverless and short-lived processes bill fractionally by connection time, so a process that runs briefly does not count as a full monthly connection.
What counts as one client-side MAU, one session, and one error for billing?
Each unique client-side user or device counts as one monthly active user (MAU). A session is one recorded user session, a single browser tab instance. An error is one unique error or exception. Each session and error stays stored for one month.
What happens to AI Runs if I pass the included amount each month?
The first 5,000 AI Runs each month are included at no charge. An AI Run is generated when you track an LLM request or run an online evaluation. Usage above 5,000 bills per additional thousand runs. Charges apply only to the runs beyond the included amount.
launchdarkly.com
Helpful?
Vendor refund policy
All fees are non-refundable except as required by law.
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
For billing inquiries related to your AWS Marketplace subscription, contact support@launchdarkly.com with your AWS account details.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Datadog is a SaaS-based unified observability and security platform providing full visibility into the health and performance of each layer of your environment at a glance.
ClickHouse Cloud is an extraordinarily fast, seamlessly scalable and delightfully easy-to-use online analytical database. Start today and receive $300 in free credits.
Integrate your applications, data sources, and AWS environment by leveraging robust solutions offered by Boomi in a frictionless, pay-as-you-go solution. With Boomi Pay-As-You-Go, there is no annual subscription or long-term commitment-just a standard monthly fee and usage-based pricing. Boomi Pay-As-You-Go provides a low-cost option to explore and use the Boomi platform at your own pace, making it easier to discover services to integrate, automate, synchronize, and manage your digital transformation initiatives.
The Databricks Data Intelligence Platform unlocks the power of data and AI for your entire organization on AWS GovCloud - Community. Upon registration, you will automatically be enrolled into a Databricks pay-as-you-go plan.
Feature flags have enabled controlled rollouts and have improved phased business validation
Reviewed on Nov 11, 2026
Review provided by PeerSpot
What is our primary use case?
My main use case for LaunchDarkly is managing the controlled rollout of capability in my in-house application named Escrow Navigator, a conversational assistant that helps the escrow team retrieve and interpret order information and documents. My use case includes enabling new document upload capability, introducing support for additional file formats, and allowing users to ask questions about newly uploaded documents without selecting them again. As a Lead Business Analyst, I define rollout requirements, document acceptance criteria, and coordinate validation with development, QA, and business stakeholders, focusing on feature behavior and release readiness rather than SDK implementation.
LaunchDarkly helps us manage the rollout of new features by using feature flags and user tagging, which are the most valuable capabilities for our workflow. These capabilities allow us to make a capability available to a pilot group while other users continue with the existing experience. For example, when introducing questions about newly uploaded files, we can enable the capability for designated testers, allowing them to validate upload status, document processing, conversation association, and citation before we expand access. This gives us a practical way to gather feedback on a complete business workflow.
How has it helped my organization?
LaunchDarkly has positively impacted our organization by helping our team introduce new capabilities through controlled phase releases, making features available to selected users, gathering feedback, and validating business requirements before expanding access. This improves coordination between business development and QA teams and gives us greater control over release readiness. The main organizational benefit is increased confidence when introducing changes while limiting the number of users exposed to potential issues.
We are currently tracking logs in Power BI to see how much feedback we are receiving, and negative feedback has recently been decreasing. We are more focused on UAT, allowing selected testers to validate newly uploaded questions, citation accuracy, and process status against defined acceptance criteria, which contributes to a greater impact on ROI in our project.
We have seen great improvement in metrics such as token input and output, and latency has shown significant improvement, particularly in the production environment.
What is most valuable?
The best features LaunchDarkly offers include giving us more flexibility in controlling technical deployment with business readiness. A feature can be deployed while access remains limited to the user responsible for validating it. For Escrow Navigator, this supports phase validation for document upload and processing changes, allowing business users to review the experience while QA checks acceptance criteria before broader availability. The main benefit is better control over feature exposure and release coordination, although we have not formally qualified the financial benefit.
The flexibility helps our team when rolling out features by enabling us to roll out a feature to a lower environment and disable it in a higher environment after some time, allowing us to manage features without conducting a major deployment.
Regarding the feature flag, in the UI, if we have enabled a feature such as giving feedback, but we want to hide that feature, using LaunchDarkly, we can disable that flag, and it will reflect in the UI immediately. We also manage document upload and document review features via flags, with LaunchDarkly helping us by providing more flexibility in coordinating technical deployment.
I use LaunchDarkly with GitHub. Our development team utilizes LaunchDarkly alongside GitHub, where GitHub manages our project source code and pull requests while LaunchDarkly controls the availability of features implemented behind flags. This allows teams to merge and deploy code, enabling capability for selected testers before a wider rollout. My role focuses on requirements and UAT validation while the development team handles technical integration.
What needs improvement?
From a business validation perspective, I would find a consolidated comparison of flag settings across environments helpful. Understanding differences in configuration and targeting when reviewing a feature in dev, UAT, and production is important, along with clear business descriptions, ownership information, and visibility into flags that are ready for retirement. This would make release review easier for stakeholders who do not work with technical configurations every day.
If there are links to documentation available, that would be really helpful, especially from a knowledge transfer perspective.
For how long have I used the solution?
I have been using LaunchDarkly for around one to two years.
What do I think about the stability of the solution?
LaunchDarkly is currently stable, and we have not faced any issues with reliability or downtime.
What do I think about the scalability of the solution?
From our project perspective, LaunchDarkly has supported our feature management across environments and pilot user groups without accessibility issues. As usage grows, maintaining clear flag ownership, naming conventions, and cleanup practices becomes essential. I have not personally conducted load testing, and my assessment is based on business validation and release activities.
How are customer service and support?
We have not faced issues with customer support, as we have raised tickets and received solutions within the expected SLA timeframe. I also coordinate internally with the development and platform teams who handle any vendor escalations, leading to a good experience overall.
I rate customer support an eight out of ten.
Which solution did I use previously and why did I switch?
Prior to LaunchDarkly, we used an in-house tool that managed feature availability through application configuration settings and coordinated deployments. This led to difficulties as enabling a feature for selected pilot users required additional deployment or configuration work. LaunchDarkly gives us a centralized way to manage feature availability and targeting, making phased rollout much easier to coordinate.
We previously used an in-house tool for delegated feature management that managed feature availability. My assessment of LaunchDarkly focuses on its support for our requirements in controlled rollout, pilot testing, and business validation, as we no longer need multiple deployments across environments for managing feature access. LaunchDarkly enables us to disable features for users from its settings without the need for deployments.
What was our ROI?
We definitely see a return on investment, with operational values in easier pilot releases, more focused UAT, and greater control over feature availability, although we have not formally measured financial ROI or confirmed specific amounts saved. The benefits assessed could reduce release coordination efforts and rework, but supporting data is needed to translate them into concrete cost savings.
What's my experience with pricing, setup cost, and licensing?
From a BA perspective, I assess value through the flexibility it provides for controlling release and pilot testing. My role in setup revolves around defining rollout requirements, identifying pilot users, and validating the enabling and disabling of feature behavior in Escrow Navigator, as the development team manages technical integration and configuration.
Which other solutions did I evaluate?
Compared to our previous approach of managing features through application configuration and deployment, LaunchDarkly stands out by offering more flexibility for controlled release and pilot testing. For Escrow Navigator, its main value is enabling selected users to validate new capabilities before wider availability, fitting projects that need phased rollout and clear release governance, though I have not conducted a formal evaluation of competing platforms.
What other advice do I have?
I would rate LaunchDarkly an eight out of ten.
I chose an eight because of the flexibility I have discussed earlier, along with the capability of supporting multiple environments, which I find good. However, since I am not sure about pricing, I do not give it a ten. In the future, when I have more understanding of pricing, I would definitely want to explore it and potentially change my rating.
In terms of accuracy and reliability, I find LaunchDarkly's capabilities to be really good, as it supports governance and indirectly enables our application changes for certain testers to validate extra data and documents. While it would not directly improve dependence on document extraction or validation, any measured accuracy improvement that is considered ground truth is very helpful for us.
Advice for others looking into using LaunchDarkly includes starting with a small pilot and a clear use case, such as enabling a new capability for selected users before a wider release. I recommend defining flag ownership, naming conventions, and cleanup responsibilities early, including both enabled and disabled behaviors in acceptance criteria during UAT, validating fallback behaviors, while keeping feature targeting separate from application security permissions. Finally, review pricing against expected user measures to assess value.
Himanshu Roy
Feature flags have reduced production incidents and support safe, gradual rollouts and A/B tests
Reviewed on Nov 11, 2026
Review from a verified AWS customer
What is our primary use case?
My main use case for LaunchDarkly is feature gating. Whenever I introduce a new feature, I put it behind a LaunchDarkly flag and then use it to release that feature percentage-wise. I release it for some percentage of people or some team members, then see if everything works fine, and then roll it out for 100% of the users. I also use it for A/B testing.
A quick specific example of a feature I released using LaunchDarkly is the new cancellation flow, which was basically to reduce some churn. I didn't roll it out for all users; I first tested with only basic plan users. When I saw that it was working fine for them, I rolled it out for another plan, like the professional plan, and so on. Then I introduced it for the enterprise plan users, and then it was rolled out for all the other plan users.
With AI coding tools helping my team ship code faster than ever, LaunchDarkly helps me maintain control once that code hits production by following a percentage-wise rollout strategy. I first roll out changes to a small percentage of users, then monitor them, and if everything works fine for them, I gradually increase the percentage.
With LaunchDarkly, I use Sentry for error logging and monitoring whatever goes on with the changes, and it helps in observability and catching and figuring out the errors or any issues the users are facing.
How has it helped my organization?
LaunchDarkly has positively impacted my organization as I have been able to test things to a small percentage of users before rolling it out to a larger audience. If I have a bug in my production rollout, the blast radius is very small with this percentage rollout strategy, and if I find something, I can just quickly roll back that.
From this approach, I can say that I have much less production incidents. In my four or five years here at my current company, I haven't seen any production issue where I have to roll out every change for all users because I catch it at an early stage as well because of LaunchDarkly, and that helps me improve my reliability metrics.
What is most valuable?
One of the best features that LaunchDarkly offers is that if I create a flag in one environment, such as beta, it is automatically created in other environments, in staging and production, and all I have to do is enable it in those environments whenever I want. Another feature I really appreciate is the simplicity of adding more conditions and making the flag more complex according to my use case. The interface is very straightforward, easy to understand, and intuitive.
The automatic flag creation across environments helps my workflow because, as I mentioned before, if I create a flag and test some rollout strategy, I would like to test it on my beta environment first, then on stage, and then finally roll it out to the production environment. If this feature was not there, I would have to create this flag three times in a row. However, since LaunchDarkly provides this feature, I create the flag only once, and then it is replicated to all the other environments, and then I can just turn it on in the other environments without creating it from scratch. The UI is seamless to take care of all of these things.
What needs improvement?
One improvement that I think LaunchDarkly could make is that the search can be improved. Sometimes I find it complex to search for my feature flags or the feature flags created by other users.
For how long have I used the solution?
I have been using LaunchDarkly for three years.
What do I think about the stability of the solution?
LaunchDarkly is stable.
What do I think about the scalability of the solution?
LaunchDarkly's scalability is good because I have a large user base of approximately 40 million users, and it scales pretty reliably.
Which solution did I use previously and why did I switch?
Since my start at this company in 2022, my organization has been using LaunchDarkly only, so I don't have any context about what my company was using before LaunchDarkly. My organization didn't use any different solution before LaunchDarkly.
What was our ROI?
I can comment that the reliability improved a lot with using LaunchDarkly.
What's my experience with pricing, setup cost, and licensing?
My organization purchased LaunchDarkly and received the license.
Which other solutions did I evaluate?
My organization directly chose it without evaluating other options.
What other advice do I have?
On a scale of 1 to 10, I would rate LaunchDarkly a nine. I picked nine out of 10 because of the search feature I mentioned.
LaunchDarkly is deployed in my organization as a public private cloud.
I advise others looking into using LaunchDarkly to increase the reliability of their product by adopting a percentage-wise rollout strategy. You can also use A/B testing to figure out which features are liked more by the users, so it's a very good product to do all of these things.
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Priyanshu Maurya
Feature flags have enabled instant rollbacks and gradual cluster-based releases
Reviewed on Nov 10, 2026
Review from a verified AWS customer
What is our primary use case?
I use LaunchDarkly mainly for feature management and backend-related activities, such as when launching a new feature. I flag it behind a feature flag so that I can revert it whenever required, which provides instant rollback.
For example, I used it in a migration where I had to migrate a service from one AWS stream to another stream. I put it behind a feature flag using LaunchDarkly, so that if something fails, I can revert it quickly without any PR or any merge using code or something similar.
Using AI, I usually see faster code delivery, but there is a possibility that it can break in production. Everything is gated behind feature flags in LaunchDarkly, so it helps me a lot in preventing incidents.
How has it helped my organization?
LaunchDarkly has impacted my organization in a very positive manner. Earlier, I had to wait for a deployment which went step by step in case of any incident, but now it is quick, so the resolution is fast.
Within five minutes, I can roll out in case of any incident. Earlier, it used to take two to three hours for a particular rollback, but now using LaunchDarkly, I can just turn off the feature flag and restart the service.
What is most valuable?
The features I like about LaunchDarkly are that I can roll using it by cluster by cluster and region by region. I have different types of tags that I can use for each feature flag, and I have a review system so that if someone tries to change a feature flag, then it needs to be reviewed so that others can also know about this. These options help me a lot.
The feature that has made the biggest difference in my day-to-day work is the rollout feature cluster by cluster, where I can set to which cluster I have to roll out a feature, and then I can gradually increase using LaunchDarkly. This is quick and fast.
There is also a feature where I can target LaunchDarkly feature flags by app level. For example, if I am migrating something, then I can put an app tag so that I can only target a particular app for a particular feature flag value.
What needs improvement?
I think the initialization of LaunchDarkly inside code can be made much easier because currently, every initialization calls the API.
I need to call the API again and again whenever I need to see the update for a particular feature flag value. If that can be automatically implemented in the backend so that the feature flag value can be automatically fetched by the SDK, I could use it more effectively.
For how long have I used the solution?
I have been using LaunchDarkly for the last six months.
What do I think about the stability of the solution?
LaunchDarkly is stable.
What do I think about the scalability of the solution?
Regarding scalability, LaunchDarkly is quite stable and scalable, which helps me a lot.
Which solution did I use previously and why did I switch?
Before LaunchDarkly, I maintained a backend JSON file, and every time I needed to make a feature flag change, I created a PR for that, changing that JSON value. Then that JSON value is fetched again and again in the backend to read the latest value.
I used to maintain a JSON file with embedded values for feature flags, which was time-consuming, so I switched to LaunchDarkly.
What was our ROI?
I save time with LaunchDarkly.
Which other solutions did I evaluate?
LaunchDarkly stands out as it is quicker in its approach and also cleaner, and I have different options, including a review system. These are all good things in LaunchDarkly.
What other advice do I have?
I chose nine out of ten because the initialization of LaunchDarkly requires me to call the API repeatedly to see updates for a particular feature flag value. If that could be implemented automatically in the backend, it would enhance the experience.
My recommendation to others reading reviews on PeerSpot is to use LaunchDarkly as much as possible. Whenever they launch a new feature, they should put it behind a feature flag created in LaunchDarkly, and it can be the best option for that purpose. When they want to roll out gradually, cluster by cluster or cell by cell, then LaunchDarkly is also the best option for that.
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)
Battula Ramesh
Feature flags have improved safe rollouts and now support gradual testing across environments
Reviewed on Nov 10, 2026
Review provided by PeerSpot
What is our primary use case?
My main use case for LaunchDarkly is to manage feature flags, enable or disable features without deploying code, and safely test new features across different environments.
I use feature flags in LaunchDarkly to control new features in different environments such as development, SIT, and UAT. First, I enable the features for testing, verify the functionalities, and fix any issues. Once everything is working properly, I gradually enable it for users, which helps reduce deployment risk.
LaunchDarkly helps me improve release management, reduce risk, and quickly roll back features if issues occur, giving me better control over feature releases without the requirement for frequent deployments.
LaunchDarkly helps me maintain control through feature flags and gradual rollouts once the code hits production.
How has it helped my organization?
LaunchDarkly has positively impacted my organization by making feature releases safer and more flexible, helping me reduce deployment risk, test new features with specific users, and quickly disable features if any issues occur. Overall, LaunchDarkly is improving my release management and development efficiency and effectiveness.
I have seen improvements in release flexibility and testing efficiency.
What is most valuable?
The best features LaunchDarkly offers are enabling or disabling features without a deployment and enabling features for specific users or groups.
Targeting specific users or groups helps my team validate a feature before rolling it out more broadly by allowing me to enable a feature for a specific user group first, collect feedback, and validate the functionalities. Once everything works as expected, I can gradually roll it out to all users and release features safely and confidently.
I would also highlight the monitoring and analytics features of LaunchDarkly, which help me track feature performance, identify issues early, and make better decisions during releases. Overall, LaunchDarkly makes feature management easier, faster, and safer.
What needs improvement?
I think LaunchDarkly could be improved by making the user interface simpler, providing better reporting and analytics, and offering more detailed feature flag monitoring.
I would suggest improving documentation, providing more practical examples, and making troubleshooting easier.
For how long have I used the solution?
I have been using LaunchDarkly for two months.
Which solution did I use previously and why did I switch?
Before LaunchDarkly, I mainly relied on traditional configuration-based feature management and a manual deployment process due to the limitations and difficulties I encountered.
Which other solutions did I evaluate?
LaunchDarkly stood out because of its easy-to-use feature flags, targeted rollouts, real-time updates, and environment management, and this flexibility along with the reduced release risk were the main reasons for choosing it.
What other advice do I have?
I rate LaunchDarkly an 8 out of 10. I give it an 8 because LaunchDarkly provides excellent features, flag management, safer releases, gradual rollouts, and flexibility.
I think LaunchDarkly's AI capabilities should provide strong governance and security, with access control, data privacy, audit logs, and transparency being very important.
Regarding reliability and accuracy, I think LaunchDarkly's AI capability improves productivity by providing safer and more accurate insights.
LaunchDarkly is deployed as a public cloud-based SaaS solution in my organization, which I access through a web platform to manage feature flags across different deployment and testing environments.
I use LaunchDarkly's cloud-hosted SaaS platform, although I'm not completely certain about the underlying cloud provider.
Luis Bravo
Feature flags and AI prompts have enabled rapid config changes and faster experimentation
Reviewed on Oct 20, 2026
Review provided by PeerSpot
What is our primary use case?
I use LaunchDarkly for feature flags to turn on and off features that we deploy into production. I have also used LaunchDarkly to manage AI in production. We're using it for AI config, which are basically the prompts. So we are using it for flags and we also use it for the prompts, to store the prompts.
How has it helped my organization?
LaunchDarkly has helped me solve the challenge of iterating quickly on prompts and instructions. Having the instructions and prompts in LaunchDarkly makes it fast to iterate and just like flags, I can go into a UI and make the change, rather than having to deploy code, because the CI workflows tend to be a lot slower. We ended up wanting to have the instructions as code anyway, so we had to work on a specific pipeline to be able to still store that from our side as code and also publish it to LaunchDarkly. The main advantage is the same as the flag's flexibility—basically being able to change it quickly without having to actually wait for a PR to be merged and something to be deployed.
What is most valuable?
LaunchDarkly works well and it's nice to have the control of a feature flag as a whole. It's very handy. The only thing that I would like is a more structured way to visualize the flags, especially when you end up having too many flags and there is some hierarchy. The UI and the way that it is presented is very flat. When you end up having structures and dependencies on flags, there is no dashboard that would give you exactly what you want, especially when you're working on a particular project. Because the way that we have in our organization is that we have multiple products, multiple features and multiple teams that are working on features. You end up having a lot of different flags that are presented in a flat manner, and you may have a main one that when it is turned on, the child ones are evaluated based on it, and you may have many depths on that relationship. If there were a dashboard or a certain view that would make that structure apparent and very obvious, it would be useful.
Also, because you have different values depending on whichever environment that you're interested in, you have to actually dig into what are the relevant flags and then go to a particular environment that you are focused on. If there would be some sort of dashboard that would give you all of that as a whole, not individually by flag, but as a whole structure is constructed and your interest checked on, it would be handy from the flag side.
What needs improvement?
I would like to see all of the flags and their relationships and I would like to see a tree type view. As a developer, I may be working on a particular piece from a particular team. If I'm able to just group them the right way based on the hierarchy of the flag and just select the particular feature that I'm working on and only see that and see all of the hierarchy, and also see all of the values based on the environment that I am interested in at a glance, would be very handy and that would save a lot of time.
For how long have I used the solution?
I have been using LaunchDarkly for maybe six months overall. I have been working in my current field for seventeen years.
What do I think about the stability of the solution?
There was one time that there was an outage, and we had to act on it because the default that we were getting actually ended up breaking some other feature.
What do I think about the scalability of the solution?
I am not aware of any performance issues, but I am aware of one time that there was an outage and we had to act on it to fix it.
How are customer service and support?
We have a thread in Slack where we are raising issues directly to LaunchDarkly support. I'm not really involved in that, but I do know that this thread exists.
Which solution did I use previously and why did I switch?
I have used an in-house solution previously. Comparing to that, LaunchDarkly is very feature rich, but it's basically because we were doing it ourselves. We are also using LaunchDarkly for AI configuration and that also seems intuitive, but it also ends up suffering from the same symptom of having everything be very flat. We have been having issues with certain variations of AI config being too large. There is a certain limit that LaunchDarkly imposes on how much you're able to post as a variation for an AI config. We have been having a lot of issues with that recently. We did a migration from the in-house solution to LaunchDarkly.
How was the initial setup?
I didn't actually do the platform part, but from my point of view, I was just moving existing flags to be in LaunchDarkly flags. I didn't do any work regarding that, but because it was already taken care of, I was just using the flags.
What about the implementation team?
There's a platform team that is taking care of the maintenance side, so it doesn't require maintenance on my end.
What was our ROI?
I wouldn't be in the position to actually compare metrics, but LaunchDarkly seems to be pretty performant. The client in the browser gets the events fairly quickly.
What other advice do I have?
I give LaunchDarkly a rating of eight out of ten overall for everything.