module_01
Backend services with operational reality in mind
Authentication, role-based access, business logic, and the observability hooks needed to understand what the service is actually doing under production pressure.
Argentina · SysAdmin & Backend Developer
Backend systems.
Linux operations.
Cloud troubleshooting.
I build backend services and keep production infrastructure understandable, observable and recoverable. My day-to-day connects application code to Linux, Kubernetes, networking, CI/CD and the systems behind real production work.
Current role
Production SysAdmin
Backend
Node · TS · Python
Cloud
AWS · Azure · vCD
Focus
Production reliability
profile.frame
● live 
Live
A portfolio shaped like the systems behind it.
Synthetic stream — but the shape is honest: this is what production looks like once you've earned the right to read it calmly.
Value
Systems that are easier to deploy, observe, and repair.
My work connects backend development with infrastructure operations: service design, automation, observability, networking, and incident response.
module_02
Production infrastructure that can be repaired
Linux, Kubernetes clusters, Helm charts, CI/CD pipelines and cloud environments — kept in a shape where deployments and incidents both have a clear procedure.
module_03
Debugging across layers
Network, system, runtime, application. Logs, metrics, packet path, NAT, VPN, workers, cronjobs — read together instead of one at a time.
Technical operating system
LautaroOS — the working tree.
An interactive snapshot of the technical world I operate inside. Click any module — or use ↑↓ / j k — to inspect the typical operational use.
~ $ tree LautaroOS
↑↓ navigateLautaroOS/
├── Backend Runtime
├── Infrastructure Layer
├── Cloud & Network
└── Operations
module
Node.js / TypeScript
typical use
Web application development, REST and GraphQL APIs, background workers, third-party integrations and service-to-service communication.
Backend Runtime · 1/5
↑↓ · j/k
Commands I actually use
Operational evidence, not a cheat sheet.
The shell I live in, grouped by domain. Real commands from real production work — Kubernetes, Linux, networking, CI/CD, Docker, Terraform, debugging.
commands · daily ops
- $
kubectl get pods -A -o wideKubernetes - $
kubectl describe pod <pod> -n <ns>Kubernetes - $
kubectl logs -f <pod> --tail=200Kubernetes - $
kubectl get events -n <namespace> --sort-by=.lastTimestampKubernetes - $
kubectl rollout status deployment/<name> -n <namespace>Kubernetes - $
kubectl get configmap app-config -o yamlKubernetes - $
helm template ./chart -f values.yamlKubernetes - $
helm upgrade --install <release> ./chart -n <ns>Kubernetes
Selected projects
Backend and platform work outside the dayjob.
Personal and freelance work — backend services, infrastructure ownership, automation. Each entry includes problem, stack and operational impact.
case_study/001
Lau's Server Homepage
Personal server dashboard built to monitor and manage my homelab environment from a clean web interface.
impact
The dashboard centralizes operational visibility and common management actions, making the server environment easier to monitor, search, reorder, and control from the browser.
Astro Svelte 5 TailwindCSS 4 TypeScript Docker Cloudflare API
case_study/002
ShadowScan
Discord bot for authorized network diagnostics, service discovery, and security analysis using NMAP and external threat intelligence APIs.
impact
ShadowScan packages scan modes, threat intelligence, rate limiting, validation, audit logging, and administrative controls into a modular diagnostics bot.
Python discord.py NMAP aiohttp psutil VirusTotal API AbuseIPDB API OTX API
case_study/003
E-commerce API
REST API for an e-commerce platform with authentication, role-based access control, product catalog, orders, and media upload.
impact
The API provides a modular NestJS backend with authentication, role-based access, database utilities, stock validation, Swagger documentation, and Cloudinary uploads.
NestJS TypeScript PostgreSQL TypeORM JWT Auth0 Cloudinary Swagger