AUNE — Infrastructure and Observability

Start Your Project

Infrastructure as code and observability for AUNE

Case Study

Our Solution

AUNE is a capital markets infrastructure entity in Argentina. Deployments were slow and depended entirely on the development team, even for simple operational tasks. There was no centralized visibility into the state of the infrastructure, and without prevention and contingency tooling, the team ended up handling cases that had already turned critical.

Solution Delivered

We migrated AUNE's entire stack to Infrastructure as Code with Terraform and adopted an observability stack built on Grafana, Loki, and Prometheus across AWS and Azure. We also built an internal operations platform that lets support teams and other non-technical roles run deployments and manage tickets without depending on development for tasks that previously required its direct involvement.

Project Results

  • Deployment times reduced significantly
  • Operational tasks decentralized away from the development team
  • Real-time visibility and control over the infrastructure

Significantly faster deployments

Significantly faster deployments

Deployment times dropped significantly compared to the previous process, which depended entirely on the development team.

Decentralized operations, no development dependency

Decentralized operations, no development dependency

The internal operations platform lets support and other non-technical roles run deployments and manage tickets on their own.

Real-time visibility and control

Real-time visibility and control

The observability stack built on Grafana, Loki, and Prometheus centralizes the state of the infrastructure and gives the team prevention and contingency tooling before a case turns critical.

What is nearshore software development?

Nearshore means hiring a tech team in a country geographically and culturally close to yours — typically within 1–3 time zones. For US companies, that means Latin America. You get real-time collaboration, overlapping work hours, and engineers who operate in English, without the communication friction that comes with offshore teams 10+ hours away.

What time zone does Renaiss operate in?

We're based in Argentina — UTC-3. That means 4–5 hours ahead of the US West Coast and 2 hours ahead of the East Coast. In practice, we maintain a daily overlap of 4–6 hours with most US-based teams, which covers standups, code reviews, and real-time problem-solving without anyone working at midnight.

What cloud services does Renaiss specialize in?

Our work sits at the intersection of cloud infrastructure, application architecture, and AI. Concretely: cloud-native architecture design, infrastructure automation, platform engineering, data pipelines, and GenAI integration. We don't do generic cloud support — we build and run systems that need to scale.

Do you work with AWS, Azure, or GCP?

Our primary depth is in AWS. We also work with Azure and GCP depending on the client's existing stack — the goal is always to work within your environment, not to push a preferred vendor.

Can Renaiss help us modernize a legacy application?

Yes — and it's one of the problems we work on most. App modernization usually means one or more of the following: breaking a monolith into services, re-platforming to cloud-native infrastructure, replacing outdated dependencies, or improving the CI/CD pipeline so your team can ship faster. We start with a technical assessment before recommending any approach.