Skip to content
lfm.sys SysAdmin & Backend Developer Contact

Open to scoped technical work · Argentina

Infrastructure you can understand, measure, and repair.

I'm Lautaro, a SysAdmin and Backend Developer. I help small teams stabilize Linux/Docker systems, verify backups, improve observability, and automate processes without starting with an impossible-to-scope project.

Linux · Docker · Kubernetes Backups · Grafana · Zabbix APIs · n8n · CI/CD
How I can help

Concrete services, not an endless technology list.

Every engagement starts with a stage that can be understood, priced, and verified before the scope grows.

01

Linux & Docker audit

Inventory, exposure, logs, resources, backups, and a prioritized correction plan.

02

Backups & hardening

Scoped changes, encrypted backups, recovery testing, and rollback documentation.

03

Monitoring & incidents

Useful alerts, operational dashboards, and troubleshooting for services that need to stay up.

04

n8n & API automation

A measurable first automation across APIs, Sheets, Notion, Telegram, or existing systems.

How I work

Less heroics. More traceability.

A solution is only good if it remains easy to operate after the handoff.

01

Understand

What is happening today, what cannot break, and how the result will be validated.

02

Scope

A small first stage with deliverables, boundaries, and acceptance criteria.

03

Solve

Observable changes, reversible where appropriate, backed by evidence.

04

Handoff

Documentation, open items, and a clear way to operate afterwards.

Selected case files

Real work, anonymized and explained with evidence.

View all case files →
P2 case_file/001
Open →

Production reliability improved

Monitoring Agent Migration at Scale

A fleet of production Linux servers was running a monitoring agent version approaching end of support. The migration covered messaging, DRM, licensing and backend services.

impact

Approximately 50 hosts were migrated by Lautaro. No rollback was required, and no host lost monitoring visibility for more than approximately two minutes.

Linux Observability Automation Change Management
P2 case_file/002
Open →

Operational cost improved

Temporary Capacity Doubling for a High-Traffic Load Test

A UAT environment needed to run a representative stress test before a high-traffic event, but its standard capacity was not enough to model the expected load.

impact

The stress test passed without issues. The temporary capacity increase provided a representative test profile without leaving permanent overprovisioning afterward.

Capacity Planning Performance Cloud Change Management
P1 case_file/003
Open →

Incident stabilized

RabbitMQ Backlog and Controlled Message Flush

Consumers connected to a production RabbitMQ cluster were not processing messages fast enough. The backlog grew and the affected node became stuck under resource pressure.

impact

The manual flush discarded queued messages but prevented the stuck node from continuing toward a more severe resource-exhaustion condition. The exact recovery time is not documented.

RabbitMQ Linux Incident Response Observability

Have a concrete problem?

Let's understand it before trying to sell you a huge system.

Tell me what is failing, what you want to improve, and what cannot break. I will reply with an initial read and a proposed first stage.

Start a conversation