How Modernização Informática Elevated Performance and Operational Predictability with a Project Led by heimr
- Database volume performance jumped to a new level (e.g.: 6 → 9 Gb/s in non-sequential writes)
- Greater predictability during peaks and operational routines
- Faster troubleshooting with consolidated observability
- Scaling made possible without sudden cost increases
São Paulo, 2026 — Modernização Informática, a Brazilian govtech that develops integrated software for public entities, has completed a virtualization layer modernization project focused on a trio that matters to any critical operation: performance, resilience, and cost control. The initiative was led and implemented by heimr, with Red Hat OpenShift Virtualization Engine (OVE) as the foundation of the new architecture.
For those who support systems used by city halls, municipal chambers, funds, and autarchies, “infra” is not a backstage matter. It is what guarantees service continuity, compliance, and day-to-day trust.
“When performance becomes a variable, the impact is not limited to IT. It shows up in service predictability and operational peace of mind,” says André Frauches, Head of Operations at heimr.
“This implementation brought medium- and long-term innovation capacity, turning the hypervisor migration into not just a technological replacement, but a strategic decision. The platform enables the transformation of monolithic applications into microservices within the same base environment, supporting the investment strategy, enabling implementation in hybrid environments and clouds, and opening space for continuous innovation.” — Luciano Bustelli, Head of Innovation at heimr.
The context: when “just working” is no longer enough
Modernização Informática operates with solutions for tax management, public accounting, transparency portals, e-Social integration, NFSe, and administrative modernization routines. It is a scenario where demand grows, the need for traceability increases, and security/LGPD is a prerequisite.
Over time, the virtualization environment began operating closer to its limits. The result appears in a familiar way: latency variation, sensitivity to peaks, and greater impact from I/O bottlenecks in database workloads.
“At that point, the conversation changes. It’s no longer about ‘adding more resources.’ It’s about regaining predictability,” reinforces André.
The motivation: modernize without a big bang
The premise was clear: raise the platform’s level without rewriting applications and without creating disruption to operations. The focus was on maintaining the continuity of what was already consolidated (VM workloads) and modernizing what had begun to limit growth: the virtualization foundation and its performance and governance fundamentals.
“Modernizing, in this scenario, is less about changing technology and more about regaining control over performance, risk, and cost. Everything else becomes a consequence,” says André.
Why Red Hat OVE? A modern foundation with a clear path
Red Hat OpenShift Virtualization Engine (OVE) was chosen as the solution because it balances, in a balanced way, what enterprise operations need to sustain:
- Operational continuity: modernize the platform without touching the application layer
- Governance and observability: operate with clarity and fast response
- Path to hybrid workloads: VMs today, evolution at the business’s own pace tomorrow
It is not a bet on a trend. It is a foundation that reduces evolution friction and increases predictability.
How heimr conducted the project: production engineering, not just “setup”
The execution was organized in short cycles, with progressive validations and clear acceptance criteria. The goal was to reduce risk throughout the journey and not concentrate everything at the end.
The project followed four main movements:
- Risk-oriented Assessment – Mapping of contention points and definition of guardrails (performance, cost, and availability). The focus was on gaining clarity and priority.
- Target design and environment preparation – Implementation of OVE and necessary adjustments for production, with special attention to network, storage, and observability.
- Validation in short cycles – Checkpoints to prove real gains, predictability during peaks, stability in routines, and objective “go/no-go” criteria.
- Operational consolidation – Consolidated observability and more efficient troubleshooting routines, reducing diagnosis time and increasing the team’s response capacity.
Performance that becomes predictability (and scalability)
The modernization elevated database performance to a new level: database volume performance jumped to a new tier (e.g.: 6 → 9 Gb/s in non-sequential writes), directly impacting more sensitive routines and peak moments.
As a result, the operation gained predictability: less variation, more consistency in daily activities, and greater governance in a critical environment, where stability reduces risk and improves decision-making.
Another advance came in incident response: with consolidated observability, the time to detect and understand problems decreased, reducing the period of risk exposure and returning more control to the team.
And from a scalability standpoint, cost was treated as a guardrail from the design phase, creating a more controlled growth path without relying on emergency expansions or decisions made under pressure.
André concludes with the essence of the project: “Modernizing is not about changing technology. It is about regaining control. When the foundation becomes predictable again, the operation gains momentum and the business can once again make decisions calmly.”