Jorel del Portal

What I do // 01

I build systems that last.

I design and operate distributed systems with an emphasis on integration, resilience and observability, in banking and financial environments where operational continuity is non-negotiable. I turn architecture decisions into real products and document what I learn without simplifying it into uselessness.

My work combines three things: systemic thinking —designing from first principles, considering the full life cycle—, built-in resilience —architectures conceived to sustain operation predictably— and technical execution —implementation aligned with consistent production results.

Path // 02

The stages that formed my judgment.

A thematic arc, not a résumé: each stage left a discipline I still apply.

1. Operations and troubleshooting

   I started where you truly learn: diagnosing incidents on platforms that couldn't stop. That's where the systematic investigation method I now document in the Decision Logs comes from.

2. Enterprise integration

   Middleware and B2B integration —IBM Sterling, MQ, file transfer, EDI—: the contracts between systems nobody sees until they fail.

3. Architecture and technical governance

   Designing high-availability architectures, architecture reviews and decisions documented with their trade-offs.

4. Own studio and products

   I founded Del Portal Technologies to materialize ideas as products: the same rigor of critical systems, applied to building from scratch.

The proof // 03

The evidence is in the systems.

• 14+years in critical systems
• 99.9%continuity targets I have operated architectures under
• 100+production incidents diagnosed or managed
• ES · ENtechnical talks and sessions in both languages

Cases come from enterprise environments and are presented anonymized.

And in the products: TrainO (deterministic training engine), VaultOS (privacy by architecture, local AI) and BabelDestiny (spec-first game engine, documented before the first line).

Why I document // 04

I write down what survives production.

Most engineering judgment is lost because it never gets written down: it stays in the incident resolved in the small hours, or in the trade-off someone decided and nobody recorded. I document real decisions —context, alternatives, consequences— because it is the most honest way to transfer judgment, and because writing a decision down forces you to understand it.

That is where the Decision Logs, the Fundamentals and the newsletter come from: three formats, one rule — no theory that hasn't touched production.

What I'm exploring // 05

What has my attention right now.

A video game built spec-first (Babel Destiny, a data-driven engine in Godot), local AI running on your own machine —the foundation of VaultOS— and interactive tools that turn resilience judgment into something you can use.

The territory is the same as always —engineering, systems, applied technology—; the domains change on purpose: testing the method outside its comfort zone is part of the method.

Specialty // 06

Where I'm strong.

Languages and stack

Languages and talks // 07

I speak and write in two languages.

Spanish (native) and English. I give technical talks and sessions in both, on architecture, resilience, observability and troubleshooting — you can invite me to one here. I write Decision Logs, Fundamentals and a journal of work in progress.

Quotable bio // 08

If you need to introduce me.