About Nodrius

Nodrius is the result of learning through real systems, experiments and failures.

Who I am

I learn by building, testing and breaking things.

Nodrius grew out of two years of hands-on experimentation across networking, servers and virtualization, cybersecurity governance, automation and AI.

I don't learn technology only by reading about it. I build labs, develop projects, test systems, investigate failures and document what actually happens. The goal is to turn concepts into practical knowledge that can be understood, reproduced and challenged.

AI has become an important part of this process, not as a replacement for understanding, but as an accelerator for research, experimentation and iteration.

Nodrius is the structured result of that process: a place to understand how things work, build them independently, and avoid the mistakes that cost time and money.

An open-frame server rack in a home lab: three Dell PowerEdge R-series servers — an R720, an R820 and a second R720 — stacked above a shorter PowerEdge unit and a Dell PowerConnect 5524 switch, with a bundle of network cables hanging below it.
The lab behind Nodrius.
A place to build, test, break, troubleshoot and learn.

What I do

Four areas, explored through practical work, experimentation and structured documentation. They are interconnected: a network problem becomes a server experiment, a server experiment becomes a question of governance, and automating one of them feeds the others.

What they have in common is the way they are learned: a real system, a test, an observed result and a written record that someone else can follow.

How I do it

Every entry follows the same cycle, and the cycle is not a straight line: most of the work happens between testing, breaking and troubleshooting. That cycle runs in my own lab, on real hardware — network and server experiments, development environments, projects, tests, failure analysis, validation and documentation. I chose the hardware around what I actually needed to test, configured it, kept it running and made it more efficient as the work changed. Hardware maintenance is part of that, not an exception to it.

The lab is not a demonstration of what I already know. It is the environment where I learn what I don't know yet.

A hand applying fresh thermal paste from a syringe onto the bare die of a graphics card resting on a blue anti-static mat, with the heatsink, screws and thermal pads laid out around it on a wooden bench.
The bench, mid-job.
High temperatures, the card opened, new paste, everything back together — and then the reading that says the problem is closed.

Why

AI has dramatically reduced the cost and the time required to explore a technical question. In this workflow it accelerates:

  • research
  • comparison
  • design
  • implementation
  • troubleshooting
  • iteration
  • documentation

Acceleration, however, does not remove the need to understand. It makes verification and understanding more important: a model can produce a plausible answer that is simply wrong, and only the system in front of me can tell the difference.

AI is not the replacement for the lab. It is an accelerator for the cycle of exploration.

The goal

The goal is not personal branding and it is not a demonstration of expertise. It is to build a structured body of practical technical knowledge that helps people:

  1. understand how systems work;
  2. build and experiment independently;
  3. avoid mistakes that waste time and money.

Nodrius is not a collection of shortcuts.

It is a structured record of experiments, systems, failures, decisions and technical knowledge.

The goal is not simply to make technology easier. It is to make it understandable enough to build with confidence.

contacts: [email protected]

Nodrius Field Kit — cover

Get the Nodrius Field Kit

Enter your email and we'll send you the complete Field Kit: eight technical resources in one download.

Your email address is sent to Nodrius and used to deliver the Field Kit to you by email. Marketing messages are separate and optional: the checkbox does not affect your download, and you are only added to our updates list if you tick it. Privacy Policy.

Privacy & cookies

This site does not use cookies, analytics or tracking, and it does not profile you. There is nothing technical to switch off, so Accept and Reject change nothing about how the site works: either choice lets you browse everything normally.

The only difference is what your browser remembers: two entries in local storage — your choice here, so this notice is not shown again, and a marker that the Field Kit offer has already been made — so the offer is presented once and not on every page. They contain no identifier, they are not shared with anyone, and the site sets no cookie for either.

What we do with your data
How your email address is used when you ask for a Resource, how long it is kept and which rights you have — in the Privacy Policy.
What the site stores in your browser
Two entries in local storage — your choice on this notice and whether the Field Kit offer has been shown — and no cookies, no session storage, no third-party content: in the Cookie Policy.