Systems, product, and code

Renzo Ezagui

Designing useful products and solid systems with a bias for clarity and quality.

Years of experience in demanding environments shaped how I think about architecture, product decisions, and long-term maintainability. Personal projects are where that mindset stays close to the code.

Approach
  • clarity over noise
  • scalable before clever
  • product sense close to the code
What / How
  • Products, systems, and internal tooling built with long-term structure in mind
  • Architecture, solution design, and implementation kept practical and close to delivery
  • Creative, simple solutions that still respect scale, quality, and maintainability

Selected work

Projects in motion

Early mock data for the public catalog. The final version will be sourced through the backend once the `projects` domain is modeled.

2026

Spot Analytics

active

A high-contrast market dashboard for tracking positions, movement, and execution context with a focused operator view.

  • Weighted position tracking across active pairs
  • Operator-facing metrics for buy, sell, and net flow
  • Live snapshot rhythm designed for decision speed
  • Next.js
  • TypeScript
  • Binance API
  • SQLite

2026

Linkforge

iterating

A self-owned short-link service with analytics hooks, clean governance, and an operator-first admin workflow.

  • Self-owned slug management without external dependencies
  • Structured redirect governance and analytics hooks
  • Clean internal workflow for issuing and revising links
  • NestJS
  • SQLite
  • Redis
  • Vercel

2026

Proxy Ops

iterating

A controlled operational surface for orchestrating rebuilds and maintenance actions on local proxy infrastructure.

  • Protected rebuild triggers for local proxy infrastructure
  • Operational visibility before running sensitive actions
  • Designed for small, reliable internal maintenance flows
  • NestJS
  • Docker
  • GitHub Actions

2026

Project Catalog

active

A structured project inventory with rich metadata, admin workflows, and a clean public-facing presentation layer.

  • Rich project metadata prepared for public presentation
  • Internal publishing flow for growing catalogs over time
  • Clear separation between public view and private editing
  • Next.js
  • NestJS
  • SQLite