I work with IT teams and technical leaders to define strategy, design solid cloud architecture, and automate critical processes. Less unnecessary complexity.More focus on efficient, sustainable systems aligned with growth.
Growth brings technical challenges that, if left unmanaged, become bottlenecks for the business. I help organizations overcome these operational and architectural barriers, transforming friction into scalable and predictable systems.
Lack of observability and manual deployment processes keep the team stressed and stagnant. You need stability to innovate again.
The cloud bill goes up every month but performance doesn't. Without a FinOps strategy and intelligent scaling, you're burning budget.
Accumulated technical debt makes any change a risk. You need a transition to modern, resilient architectures without stopping the business.
The team has brilliant AI ideas but doesn't know how to integrate them safely and scalably into the current product.
Before talking about technology, I need to understand what's happening in your business. I work primarily in three areas — cloud architecture, process automation, and AI integration — but the starting point is always the same: your specific problem.
Design and implementation of scalable architectures in Azure and AWS. Migrations from legacy systems with zero downtime and documented AS-IS / TO-BE strategy.
Automatic pipelines with GitHub Actions and Azure DevOps. Business process automation with n8n. Infrastructure that deploys and monitors itself.
Integration of OpenAI, Gemini, and Azure Cognitive Services into your applications and processes. No hype — just AI that solves concrete problems and generates measurable ROI.
In all my projects I use tools like OpenAI, GitHub Copilot, Claude, Cursor and Gemini to accelerate development — not to replace technical judgment, but to amplify it. The difference lies in supervision, fundamentals and best practices. In a field that evolves every week, staying up to date is not optional.

Over 14 years I held different roles — developer, tech lead, DevOps specialist, and architect — and that left me with something more useful than a title: a complete vision of the solution lifecycle.
I understand what each decision implies from the inside: how it's founded, how it's governed, how it's implemented, how it's tested, how it's deployed in CI/CD, and how it's improved over time. Not just the part that shows up in a diagram.
No client names due to confidentiality — but with real metrics. These are the transformations that make the difference.
Business teams were moving forward with their own initiatives without aligning with bank policies and standards, generating technical and regulatory risk. I designed AS-IS / TO-BE solutions using C4 methodology, guiding each team so their proposals fit within the corporate architecture before entering development.
Executives were manually reconciling bank statements against pending payment operations — an error-prone process that consumed hours every closing cycle, coordinated over a shared Excel spreadsheet that was a constant source of outdated versions and editing conflicts. I developed a platform where the executive uploads the statement and the system automatically generates the match with business operations, detecting differences instantly and eliminating the spreadsheet entirely.
When operations are distributed among multiple SaaS providers, communication between them becomes chaotic: no traceability, no control, and with silent errors difficult to detect. I implemented a custom Service Bus on Azure as a transversal channel, providing complete visibility over every message between providers and turning the integration into something governed and auditable.
What works, what fails, and what I learn along the way. Notes on architecture, devops, and business.
View all posts →The first consultation is free. Tell me about your technical challenge and I'll give you 3 concrete recommendations — no strings attached.
I reply in less than 24 business hours.