In times of austerity, efficiency concerns are greater in companies that want to continue growing solidly. Everyone discusses the best approaches for scalability, resiliency, governance, and growth. CEOs putting pressure on their teams to reduce expenses, improve processes and deliver more with less are a constant theme in the news. At Mercado Libre, the largest e-commerce, fintech & logistics company in LATAM with over 110 million active users, such concerns are an essential part of our culture, which moved us to seek the best practices since 1999, and with a natural process of searching for efficiency, led us to build our platform, Fury, which has already reached a very high maturity level, handling 900M+ requests per minute using 114K+ instances distributed among different clouds, orchestrating more than 26K microservices. We build a NoOps culture for our 12k engineers, which allows them to focus on creating great products in terms of architecture and functionalities, giving us an excellent time to market, going from zero to production in four steps, with an exceptional ability to react to problems. This talk shares our platform's benefits, the lessons learned on the journey to build it, trade-offs, and mistakes we made. We will perform a general view on Fury and then go deep into some solutions that we have implemented, and that can add value to the audience, such as: Dev Experience: How Fury optimizes Developer's productivity and creates the NoOps culture by providing Out-of-the-box management of code repositories, a robust CI/CD Pipeline, metric providers for complete observability and Cost Management; Opportunities creation that suggests or applies updates for Critical Vulnerabilities, cost optimization, and others; Performing feature inference using Sidecars and assigning better control about Security, Compliance, and NoOps on each of our microservices. Meet some of our sidecars such as Mysql Proxy, Traffic Middleware, Logs, and Metrics Agents; Acting quickly to solve issues such as Availability Zone's outages, the log4j vulnerability, or promptly responding to government regulations.