How Ouribank achieved 60% cloud savings with a FinOps strategy and AWS expertise

e-Core • March 18, 2025

The Client

With over 40 years in the market, Ouribank is a fintech leader in currency exchange and financial services — one of the main B2B players in this segment in Brazil, with over 700 partners and a strong presence among investment advisory firms. 


Its history is marked by excellence in personalized customer service, reflecting a commitment to innovation, efficiency, and exceeding customer expectations. In 2023, the brand transformed to turn boundaries into new possibilities. Ourinvest Bank announced its rebranding, investing heavily in technology and governance to expand its business, aiming to become a multi-product bank, starting with the resumption of credit operations. 


With over US 719 million in assets and US 134 million in revenue, the bank has a network of over 600 currency exchange correspondents and has completed more than 2.5 million currency exchange transactions, achieving an accumulated growth of 50% in recent years. Since 2021, it has significantly invested in digitalization and innovation.

The Client

In 2023, Ouribank experienced exponential growth, leading to a 147% increase in infrastructure costs. As an institution that handles transactions in various domestic and international currencies, it became critical to identify the specific costs associated with these operations.


In parallel with its revenue growth, the bank faced a significant challenge: the need for clear visibility into its cloud spending. Without this clarity, the continuous infrastructure expansion, coupled with the bank’s accelerated growth, made it difficult to evaluate its products’ return on investment (ROI), jeopardizing financial viability and strategic planning. Without proper controls, costs risked escalating unsustainably.

“In 2023, our cloud infrastructure costs quadrupled, and we lacked clarity on what drove these expenses. We knew costs were high, but we couldn’t pinpoint the causes due to a lack of resource standardization and tag tracking. As a result, we didn’t have sufficient visibility to determine the cost of each product and price them appropriately.”


Luis Eduardo dos Santos

IT Superintendent at Ouribank

The Solution

To address these challenges, leadership recognized the need to invest in a dedicated FinOps team. They hired a specialist to implement FinOps practices and partnered with e-Core to drive actions and disseminate best practices across departments.


Initially, e-Core conducted a detailed FinOps maturity assessment,analyzing Ouribank’s operational costs on AWS. This assessment identified inefficiencies and opportunities to optimize resource use for greater efficiency. Based on these insights, a roadmap was created using the FinOps.org framework, categorizing the implementations into four areas:

Cost Classification and Control

A taxonomy review resulted in the implementation of a tagging strategy for approximately 92% of resources. This allowed the bank to identify high-usage products and assign responsibility for optimization during the next project phase.


Daily anomaly and budget alerts were also implemented for key product accounts, enhancing spending predictability and preventing exponential waste.

Optimization, Savings Plans (SP), and Reservations

The bank prioritized cost-impactful yet low-operational-impact initiatives, starting with “quick wins.” This included shutting down idle resources and automating workload shutdowns during off-hours in development and testing environments. They also shifted ECS Fargate from “on-demand” to “spot” pricing.


Another “quick win” involved reducing over-provisioned resources. Using the AWS Cost Optimization Hub, the bank identified and adjusted these resources efficiently.


In Amazon S3, lifecycle policies were implemented to manage data life cycles. These policies automatically move less-accessed files to Amazon Glacier or delete them after the retention period. This approach reduced storage costs while aligning resource use with business needs.


Additionally, EBS volumes were upgraded to GP3, optimizing IOPS allocation based on workload requirements, improving performance, and reducing storage costs. Following these optimizations, Savings Plans and Reserved Instances were purchased for medium-term resource needs, securing more competitive pricing.

KPIs and Culture Development

After the initial phases, the following KPIs were established to ensure efficiency:


  • Savings Plans coverage
  • Reservations coverage for Redshift and ElastiCache
  • Cost classification coverage via tags
  • Proportion of Dev/QA workloads using Spot instances
  • Automation coverage for Dev/QA workload start/stop processes


In parallel, leadership aligned on a FinOps best practices adoption strategy. e-Core also conducted a workshop for the technology team to enhance skills and foster understanding.

A blue target with an arrow in the center on a white background.

Results

The e-Core team’s consultancy and the implementation of new processes resulted in:


  • 60% reduction in cloud costs
  • 18% increase in availability and processing capacity
  • Improved visibility and spending predictability for product engineering squads and executives
  • Tagging implementation increased from 0% to 94%, enhancing cost tracking and control
  • Greater operational efficiency and transparency, including 70% Savings Plans coverage and 100% Spot instance usage in Dev/QA environments
  • Continuous and effective budget monitoring
  • Strengthened FinOps culture

“Today, we have cost predictability and a clear mapping of our needs, providing much more confidence in our operations. In less than a year, leadership gained more security in allocating investments, while the bank continues to grow. We’ve implemented a FinOps culture that avoids negative surprises and has already avoided significant additional costs, which could have reached up to USD 1 million by the end of 2024. The process led by e-Core helps us achieve the bank’s strategic financial indicators.“


Gustavo Tortoza

FinOps Specialist at Outibank

Conclusion

Ouribank’s adoption of FinOps, with e-Core’s support, significantly optimized cloud costs while increasing transparency and clarity around cloud spending. This enabled better investment planning, ensuring efficient resource use and allowing the bank to price services and calculate ROI more accurately.


These practices also fostered a FinOps culture, enabling teams to understand costs better and make more informed investments. IT now supports the bank from both technical and business perspectives, providing insights that impact daily operations and drive Ouribank’s growth.

“The success of this project stemmed from the collaboration between AWS, e-Core, and Ouribank teams. While our team focused on the business, e-Core played a crucial role in providing technical insights and solutions. This partnership enabled tools for daily cost visibility and anomaly alerts, allowing swift actions on significant variations. The result is greater financial control and the ability to competitively price our products—essential for our growth.”


Luis Eduardo dos Santos

IT Superintendent at Ouribank

With more efficient processes and clearly defined responsibilities, the bank can now align investments more strategically with business objectives.

Let's build your AWS journey together

Ready to unlock your business potential with a partner who’s as committed to your success as you are?

Contact us today →


e-Core

We combine global expertise with emerging technologies to help companies like yours create innovative digital products, modernize technology platforms, and improve efficiency in digital operations.


You may also be interested in:

Por e-Core 22 de julho de 2025
A strategic approach to modernizing code At e-Core, we often partner with organizations whose software technically “works” in production, but just barely. Over time, shifting teams, competing priorities, and tight deadlines lead to codebases that are fragile, expensive to maintain, and risky to enhance. In this context, software refactoring becomes more than a technical task. It’s a business strategy that preserves continuity while unlocking future growth. Defining refactoring: Evolution without disruption Software refactoring is the disciplined restructuring of existing code, improving readability, modularity, and performance, without altering its external behavior. Unlike a full rewrite, refactoring delivers incremental value by: Accelerating feature delivery through cleaner, more modular code. Reducing operational risk by eliminating brittleness and regressions. Lowering total cost of ownership by making enhancements less labor-intensive. Why refactoring matters for business Healthy codebases have a direct business impact: Faster Time-to-Market: Modular components support parallel development and faster releases. Greater resilience: Decoupled services isolate failures and simplify maintenance. Easier onboarding: Clear architecture and design patterns help new developers ramp up quickly. Sustainable cost savings: Less firefighting, fewer regressions, and lower maintenance overhead. What may look like a simple “cleanup” is often the first step toward digital reinvention. Refactoring techniques In enterprise environments built on Java, C#, or Python, we apply proven object-oriented refactoring techniques to increase cohesion and extensibility: Class decoupling: Split monolithic classes into focused, single-responsibility components. SOLID principles: Apply interface segregation and dependency inversion to stabilize architecture. Composition over inheritance: Build flexible, interchangeable structures. Testability enhancements : Isolate side effects and inject dependencies for better test coverage. These techniques form the foundation of our incremental software refactoring roadmaps. Beyond OO: Choosing the right tools for each paradigm Modern languages blend programming paradigms. We help clients apply the right tools to the right problems: Functional patterns in Python to create concise, side-effect-free data pipelines. Kotlin/Scala hybrids that combine OO structure with expressive functional constructs. C# LINQ and Async for declarative data queries and scalable concurrency. This multi-paradigm approach ensures that systems remain robust, flexible, and expressive. A refactoring story: From debt to differentiation Case Study: Regional logistics provider
Por e-Core 16 de julho de 2025
Background Ricksoft is known for its popular work and project management apps on the Atlassian Marketplace, including WBS Gantt-Chart for Jira and Excel-like Bulk Issue Editor for Jira. Originating in Japan, the company has grown to serve over 8,000 customers worldwide through nine apps. Their tools are trusted by some of the world’s most innovative companies to boost productivity and manage complex work. By 2019, Ricksoft was seeing growing demand from customers in the Americas and Europe, and needed to scale its support operation beyond Japan. To serve new markets effectively, they had to provide fast, high-quality service in English and across time zones, while maintaining the responsiveness and care that defined their brand. That’s when they turned to e-Core. Our approach We designed a support solution based on three key principles: timezone alignment, consistent high-quality service, and cultural alignment . To get things right from the start, our analysts flew to Japan for in-depth training. They didn’t just learn the products; they learned how Ricksoft works , communicates, and supports customers. Once training wrapped, we built the support operation around Ricksoft’s priorities: timely responses, consistency, and a thoughtful, human tone. We created detailed documentation and a clear process for hiring and onboarding, ensuring every new analyst could step into the role with confidence and alignment. We also introduced monthly updates to the knowledge base and took responsibility for keeping existing articles relevant. That work paid off: most tickets are now resolved in just two to three exchanges , and self-service performance has improved across the board. Today, Ricksoft holds a satisfaction rate of 89 percent and a CSAT of 4.63 out of 5 , well above industry averages. As new analysts joined over the years and support expanded to more products, the service quality remained consistent. “We place great confidence in e-Core’s hiring decisions,” says Alessandro Cristiano, Support Manager at Ricksoft. “They understand how we work, and their mission, values, and culture attract good talent. We had five different generations of agents in seven years, and the work was consistent all the time.” Building long-term value through support. To make support even more impactful, we set up a feedback loop between support and product. Recurring issues and feature requests are flagged and shared with product managers, turning support into a valuable channel to inform product strategy. Tone and empathy matter, too. Ricksoft’s brand is rooted in respect, clarity, and thoughtful communication. We greet returning customers by name, tailor our closings, and have consistently met their SLA targets—with 99% first-response compliance within 12 hours or less. “What is special about e-Core is that they listen first,” Cristiano says. “They don’t try to mold things just for efficiency if it doesn’t work for you. First, they absorb your culture, and then transform it.” To strengthen Ricksoft’s presence in the Atlassian Marketplace , we introduced a post-ticket review request process. That simple step led to more customer reviews, better app ratings, and increased visibility. “We’re now at the top search results, which helps increase our app installs, and ultimately our revenue,” says Cristiano. We also monitor Ricksoft-related activity in the Atlassian Community. When their apps are mentioned, our team responds quickly and accurately, helping Ricksoft remain visible, helpful, and credible in the ecosystem .
Por e-Core 16 de julho de 2025
A successful cloud migration doesn’t start with tools, it starts with the right plan . Download this guide to discover a structured, strategic approach to migrating and modernizing workloads on AWS . Whether you’re just starting your cloud journey or looking to optimize an existing environment, this whitepaper gives you the clarity and framework to do it right. What you’ll learn: A 3-phase cloud assessment and planning framework AWS tools that support discovery, migration, and modernization How to reduce cloud spend, improve security, and scale with confidence Real-world planning strategies, including containerization, serverless, and data modernization