Systems operationalnyrone.net

Nyrone

I build and run the machines other people play on.

One engineer's stack, end to end: bare-metal virtualization, hardened Linux, custom FiveM scripts, and Nyrone RP, the roleplay server built on top of it.

Role
Infrastructure and platform engineer
Focus
Game servers, FiveM scripting, self-hosted infrastructure
Runs on
Someone else's hardware, my maintenance
Availability
Open to select work

What's running

Everything under this domain is something I keep alive.

A few things, mounted in the same rack. One is a place to play, the rest is what keeps it running, and all of them share the same hardware and the same on-call rotation of one.

  • Server

    Nyrone RP

    My own FiveM roleplay server, and the reason most of this exists. A heavily reworked roleplay framework with its interfaces being rebuilt one by one: inventory and crafting first, then the phone, HUD, radio, MDT and the admin tools.

    In developmentFiveM · Lua · React
  • Core

    Infrastructure

    The hardware everything here runs on: owned by someone else, maintained by me. Hypervisors on bare metal, ZFS underneath, KVM guests and containers on top, carrying the game server, its databases and every dev environment. Also where I get to break things on purpose.

    OperationalBare metal · KVM
  • Scripts

    Nyrone Scripts

    A growing set of custom FiveM scripts: an arena, garages, a HUD, an MDT and a tablet. Early days: some pieces are done, some are still being shaped.

    In developmentFiveM · Lua

Previously racked

Things that ran, and then didn't.

Before any of the above, and alongside some of it: a run of FiveM roleplay servers, Minecraft worlds, and the odd side project. Status varies from one to the next, and all of them are why the current ones are built the way they are.

  • FiveM roleplay servers

    Mixed status

    A handful of communities, a few years each: some are still running, some shifted ownership, some got nuked, some disbanded, and some are archived until further notice. Custom scripts, custom economies, and the first real lessons in what breaks once actual people are online.

    Several communities
  • Minecraft servers

    On demand

    Survival worlds and modded packs. Never fully switched off: it comes back up whenever the group feels like playing. Where running a server stopped being a hobby and started being a job I liked.

    Multiple worlds

Stack

What I reach for.

Infrastructure

  • Proxmox
  • KVM
  • ZFS
  • Debian
  • Docker
  • nginx
  • WireGuard
  • Linux hardening

Backend

  • Node.js
  • TypeScript
  • PHP / Laravel
  • MariaDB
  • Redis
  • MongoDB
  • Prisma
  • REST APIs
  • OAuth

Frontend

  • Next.js
  • Astro
  • React
  • Tailwind
  • Design systems
  • Accessibility

Game servers

  • FiveM
  • Lua
  • NUI (React / Vite)
  • Server-authoritative design
  • Economy systems
  • Discord bots

Track record

The work behind the uptime.

Different systems, same thread running through them: get on-call at 2am, find the actual cause, fix it so it doesn't need a person next time.

  • Ongoing

    Backend & Systems Engineering

    Confidential client work. Most recently: reviving a legacy point-of-sale system's compliance software after years of nobody touching it, fixing a build that hadn't compiled in a decade, recovering a lost piece of the program from old debug files, and getting every part of the system talking to each other again.

    Confidential clientSystems · Backend
  • 2022 to 2025

    Freelance Systems Consultant

    Deployed and hardened Linux environments for independent FiveM, Minecraft, and Rust communities. Diagnosed networking, configuration, and performance issues directly with server owners, and cut hosting costs by up to 30% through better resource allocation.

    IndependentLinux · Multi-game

Get in touch

Need someone who owns the whole path?

Infrastructure, the software on it, and the interface in front of it. Tell me what you're running and what keeps breaking.