RAW INPUT
The problem comes in, not the solution. We start by measuring real traffic, real costs, and real constraints. Without that, there is no design—only opinion.
ENGINEERING SYSTEMS
everlabs.dev is an independent
engineering lab focused on building,
testing and scaling distributed systems,
platforms and AI-powered products.
01
How the assembly line works
The problem comes in, not the solution. We start by measuring real traffic, real costs, and real constraints. Without that, there is no design—only opinion.
The smallest architecture that can handle the next order of magnitude. Code that can be deleted. Interfaces before implementations.
The quality gate is non-negotiable: unit, contract, load, and static analysis run in parallel on every artifact.
A canary release from 5% to 100% with automatic rollback. If deployment feels risky, deployment is not the real problem.
Metrics, traces, and logs in a single dashboard. An alert must arrive before the incident—or it is not useful.
02
Selected work, built and published
A CLI and full-screen TUI that turns Proxmox VM and LXC management into one workflow, orchestrating Terraform and Ansible without hand-written infrastructure code.
A bilingual engineering field notebook connecting long-form articles, practical guides, canonical references, and concise notes across software architecture, platforms, and AI.
03
Prototypes, benchmarks, and technical explorations
04
The engineer behind the lab
everlabs.dev is my public engineering lab—a place where systems, tools, experiments, and technical notes remain open enough to inspect, run, and question.
I’m Ever Cifuentes, a software architect and staff backend engineer. For fourteen years I’ve designed distributed systems for streaming, telecommunications, and large-scale commerce—work where reliability, boundaries, and operational clarity matter long after launch.
This portfolio is the experimental counterpart to that professional path. Some entries are production-ready tools; others are prototypes, benchmarks, or assessments. I publish both because the decisions and evidence behind a system are part of the work.
EXPLORE MY PROFESSIONAL WORK ↗05
Ideas, feedback, and technical conversations
For questions about a project, potential collaborations, or simply to compare notes, write to me. Include the project or idea that brought you here.