I keep servers running so you can sleep

DevOps specialist from Argentina. Two decades of breaking things, fixing them, and eventually learning not to break them in the first place.

Let's talk What I do
DevOps illustration
20+
Years in the trenches
9x
Cloud cost cut (yes, 9x)
99.99%
Uptime (the good kind)
150+
VMs under my watch

About me

I got into networks and Linux servers back when dial-up was still a thing. Over the years I moved from cables and racks to VMs, then containers, and now Kubernetes clusters. The tools changed but the goal stayed the same: keep things running and spend as little as possible doing it.

My recent work has been in fintech, the kind of environment where downtime costs real money and a security gap turns into a compliance problem overnight. That taught me to treat CIS benchmarks, audit trails, and infrastructure hardening as requirements from day one, not things you bolt on later. I also spent over a decade running infrastructure for a public university, where you learn to do a lot with very little.

I teach telecommunications and infrastructure at university level, and I hold a degree in Systems. Teaching forces me to actually understand things instead of just knowing which buttons to press.

What I do

Mostly I make infrastructure boring. Boring is good. Boring means it works.

Cloud & Kubernetes

  • I run Kubernetes clusters on AWS and Azure. Started with VMs, migrated to containers. The clusters stay up.
  • Moved workloads from old VMs to containers. Cut costs, improved scalability, fewer 3am calls.
  • Autoscaling, load balancing, failover. The stuff that lets you sleep at night.

Automation & CI/CD

  • Pipelines that deploy in minutes instead of hours. Azure DevOps, GitHub Actions, GitLab CI.
  • Terraform and Ansible. I stopped clicking buttons in consoles years ago.
  • Grafana dashboards, Prometheus alerts, Loki logs. When something breaks, I know before users do.

Networking & Security

  • VPNs, firewalls, WAF rules. Keeping the bad stuff out.
  • IPv6, BGP, MikroTik. I won the LACNIC IPv6 Challenge in 2018, which was a nice surprise.
  • TLS certs with automatic rotation. No more expired certificate emergencies.

Compliance & Hardening

  • Infrastructure hardened following CIS benchmarks. Not checkboxes on a form. Actual security configuration, applied and verified.
  • Logging, access controls, and change tracking set up so auditors find what they need without chasing anyone down.
  • Network segmentation and least-privilege access as defaults, not afterthoughts. In fintech, you learn that the hard way or the expensive way.

AI & LLMs

  • This website was built with AI assistance. I use LLMs daily for infrastructure work — writing Terraform, debugging configs, automating repetitive tasks.
  • I test every model I can get my hands on. Cloud APIs, local models with Ollama, different providers. Knowing what each one is good at matters.
  • AI is already part of how I work. Not a replacement for thinking, but a tool that makes the boring parts faster so I can focus on the interesting ones.

After hours

I automate my house like I automate servers. My wife thinks it's excessive. She's probably right.

Home Assistant

Home Assistant on a local server. No cloud, no subscription, no one else controlling my lights.

Frigate NVR

Security cameras with object detection. My own hardware, my own rules.

Alexa

Voice control hooked into Home Assistant. Lights, AC, coffee maker. The usual.

IoT & Zigbee

Sensors everywhere. Temperature, motion, doors. The house knows what I need before I do.

Tools I use

These are the ones I actually use, not just list on my resume

Cloud & Containers

AWS Azure Kubernetes Docker VMware Proxmox

IaC & CI/CD

Terraform Ansible Azure DevOps GitHub Actions GitLab CI

Observability

Grafana Prometheus Loki New Relic ELK Stack

Networking & Security

MikroTik BGP IPv6 WireGuard WAF CIS Benchmarks

Databases

PostgreSQL SQL Server MongoDB Redis

Scripting

Bash Python TypeScript

Need help with infrastructure?

Drop me a line. I don't bite.