Lekko wraps functions in your code to make them runtime configurable by users across the company from dev and ops to product and success without bypassing CI/CD, risking outages, invalid customer configs, or interruption to your dev flow.

Fills a much-needed niche in the software world.

Why we built Lekko: For 3 years I worked at Uber where I had the opportunity to work with Flipr, a dynamic configuration system that powered the entire business. We used it to make our software flexible for product and operations to change dynamically as the business required. As software engineers, we used it wherever we could, this let us respond rapidly and safely to changing markets and new requirements. When I left Uber to join a much smaller company, I immediately felt the pain of not having those tools at my disposal. I led my new team in implementing a feature flagging system, but it quickly became clear that existing tools fall far short of solving the problem. Feature flags added complexity, created difficulty debugging or reproducing issues, exposed applications to misconfigurations that caused issues for customers and led to churn churn, and ultimately frustrated the engineering team so much that the usage was limited. The problem Engineering teams today are expected to build software rapidly in an uncertain world. Existing feature flagging systems fall short because they have too tough of a tradeoff between the added speed and the risk and complexity that they introduce. Moreover, unintended outages often occur due to changes bypassing standard software controls like CI, reviews, and tests, leading to misplaced blame on the engineering teams and a lack of access for the rest of the business. How it works Lekko goes beyond feature flagging by offering a FAANG-class dynamic configuration system that minimizes risk while improving speed. Instead of defining feature flags in an external store, Lekko allows engineers to decorate functions written in their native language. Lekko wraps these functions to make them changeable at at runtime through our web based UI for software engineers and teammates who don’t write code. Lekko sits in your code so it’s easy to test locally, it doesn’t bypass CI/CD, and issue prevention can take advantage of code understanding AI to predict and prevent potential problems before they happen. With ten binary flags you have 1024 possible configurations, making it almost impossible to test every variation. So we allow you to group configurable functions and define legitimate configurations so that daily changes can be handed of to product, customer success, or sales without creating risks or the need to interrupt engineers for every small change. How to get started Your first 25 lekkos are free forever and we have a self serve signup available on our website right now. Thanks so much for your support! We’d love to get your feedback, questions, and comments! We’ll be online all day so don’t hesitate to reach out.

@konrad_niemiec1 Adding on my perspective from the business side! Why I Joined Lekko (From The Business Side) I joined Lekko because of its immense potential to bridge gaps between engineering and other crucial business functions like product, customer success, bizops, and sales. As Konrad said, engineering teams are expected to deliver more code more quickly with less context. The same is true for many other parts of the business. Product managers are delivering more products to more customer segments, customer success is expected to fix a wider variety of problems and get customers using a broader array of features in less time, bizops is expected to optimize systems and adapt to new markets, and sales is expected to close more deals amid ever-increasing competition. Everyone needs to make changes, no one has time for bottlenecks, and businesses can’t risk bad configurations taking down major customers. Lekko makes it easy, convenient, and safe for engineers to build flexibility and dynamism into their applications. Then, we make it safe for anyone in the business to make the changes they need to accomplish their work.

@konrad_niemiec1 Hey huge congrats on the launch! Excited to try this out. Feature flagging is a big unsolved problem 🙏

Thanks for the support @jem_white!

@konrad_niemiec1 one of the best product stories I have read. As an indie hacker, I still find this a very useful product. Cannot wait to try.

Thank you for the support @aris_nakos! Let us know if you have any feedback!

Congrats on the launch! How does Lekko integrate directly with code to prevent bypassing CI/CD? Can you explain more about how the code's understanding of AI predicts and prevents potential issues?

@kshitij11 Thank you! One of Lekko's core aspects is that the dynamic functions can be written in YOUR code, in your project repositories. So these functions are checked in, tested against, and run through CI/CD like the rest of your code, and you can use them in unit tests without your testing environment needing to be connected to an external service. On the AI aspect, there's a lot of stuff we're working on behind the scenes. But with a combination of static code analysis (again, because these dynamic functions can be defined/live directly in your code) and AI analysis of historical evaluations of your lekkos, we can predict when a change could be dangerous (i.e. affecting way more users than you might intend to) or help clean up unused code paths to reduce tech debt and product complexity, which also help to prevent issues. Happy to chat more if you're interested!

Congratulations on the launch! This concept is fantastic and seems like the missing piece in our code base. Well done!

@teon_stamenovic1 Thanks Teon for your support!

@teon_stamenovic1 Great to hear Teon! Would love to follow up and see if we can add value at DocsCube.

Lekko

Beyond feature flags: FAANG-class dynamic config for all

Do you use Lekko?