Reltroner

  • 🏠 Home
  • ℹ️ About
  • 📝 Blog
  • 👤 Characters
  • 🎬 Series
  • 🌆 Places
  • 🎎 Cultures
  • 🧠 Philosophies
  • ⚖️ Laws
  • 🧬 Technologies
  • 🗡️ Items
  • 🛡️ Factions
  • 🕯️ Myths
  • 📊 Statistics
  • 🏢 Organizations
  • 📅 Events
  • 📜 Principles
  • 🧳 Portfolio
  • 📬 Contact
  • ⚠️ Disclaimer
For Recruiters & Collaborators ↗
© 2026 Reltroner Studio. All rights reserved.
JournalJournal dossier

For Recruiters & Collaborators – Professional Profile

System Architect–oriented backend engineer focused on authentication, modular ERP, and long-term system stability.

2026-01-122 min readRei ReltronerPublished

Archive signal

Collection
Blog
Sections
14
Length
462 words
For Recruiters & Collaborators – Professional Profile
Blog illustration

Reading path

  1. 🧑‍💻 Rei Reltroner (Raidan)
  2. 🧭 Professional Orientation
  3. 🧠 Core Principles
  4. 🔧 Technical Focus
  5. Backend & Architecture
  6. Authentication & Security
  7. Data & Reliability
  8. Testing & Delivery
  9. Documentation
  10. 📁 Selected Work
  11. Reltroner ERP (Ongoing)
  12. 📄 Curriculum Vitae (Notion)
  13. 🤝 Collaboration & Roles
  14. ✉️ Contact

🧑‍💻 Rei Reltroner (Raidan)

Backend / System Architect Engineer
Authentication Systems · Modular ERP · Long-Term Maintainability

Founder of Reltroner Studio — an independent engineering practice focused on building production-style internal systems with clear boundaries, strong guarantees, and disciplined scope control.


🧭 Professional Orientation

I focus on systems that must not fail silently.

My work emphasizes:

  • centralized authentication (SSO, OIDC, trust delegation),
  • modular ERP-style architectures,
  • failure isolation,
  • and long-term sustainability over feature velocity.

I do not optimize for demos or short-term novelty.
I optimize for architectural correctness, auditability, and future-proof decisions.


🧠 Core Principles

  • Boundary Discipline
    Every system has explicit responsibilities. Auth is centralized once — never duplicated again.

  • Correctness Over Speed
    A system that is slow to build but hard to break is preferable to a fast system that leaks complexity.

  • Freeze What Must Not Change
    Critical layers (authentication, trust boundaries) are frozen once validated to prevent regressions.

  • Documentation Is Part of the System
    Decisions, trade-offs, and failure modes are written — not assumed.


🔧 Technical Focus

Backend & Architecture

  • PHP 8+, Laravel 12
  • RESTful APIs
  • Multi-repository modular architecture
  • ERP-style domain modeling

Authentication & Security

  • Keycloak (OIDC, Authorization Code Flow)
  • Centralized Identity Provider
  • Short-lived JWT delegation
  • Zero-trust service boundaries
  • Session isolation (no shared cookies, no re-auth)

Data & Reliability

  • MySQL
  • Schema design & migrations
  • Audit logging
  • Transaction integrity

Testing & Delivery

  • PHPUnit (feature & unit tests)
  • GitHub Actions (CI)
  • Production-style debugging & root cause analysis

Documentation

  • Markdown-driven architecture docs
  • Phase freeze & audit reports
  • Explicit “what was not done — and why”

📁 Selected Work

Reltroner ERP (Ongoing)

A modular ERP platform built entirely solo, designed to mirror real enterprise constraints.

Highlights:

  • Centralized SSO Gateway using Keycloak
  • Finance module integrated as a passive SSO consumer
  • No shared sessions, no duplicated auth logic
  • Explicit trust delegation via short-lived tokens
  • Public audit reports & frozen authentication phases

This project is intentionally minimal in features but high in systemic complexity, focusing on long-term maintainability rather than surface polish.


📄 Curriculum Vitae (Notion)

For a structured, up-to-date CV with detailed experience and artifacts:

👉 Notion CV:
https://immense-corn-a5c.notion.site/Raidan-Rei-CV-2f786ce37ade8083a9a5d0bfee103913?pvs=143


🤝 Collaboration & Roles

I am open to:

  • Backend / Platform / System Architect roles
  • Authentication / IAM-focused work
  • Internal tools & ERP platforms
  • Remote or async-first collaboration

I work best in environments that value: clarity, trust boundaries, written communication, and long-term thinking.


✉️ Contact

  • Email: studio@reltroner.com
  • Website: https://www.reltroner.com/blog/for-recruiters
  • GitHub: https://github.com/Reltroner

“I don’t optimize for visibility.
I optimize for systems that remain correct long after the excitement fades.”


🔙 Back to Blog

Reading path

  1. 🧑‍💻 Rei Reltroner (Raidan)
  2. 🧭 Professional Orientation
  3. 🧠 Core Principles
  4. 🔧 Technical Focus
  5. Backend & Architecture
  6. Authentication & Security
  7. Data & Reliability
  8. Testing & Delivery
  9. Documentation
  10. 📁 Selected Work
  11. Reltroner ERP (Ongoing)
  12. 📄 Curriculum Vitae (Notion)
  13. 🤝 Collaboration & Roles
  14. ✉️ Contact

Continue through the archive

Associated records

Nearby entries linked by shared topics, category echoes, or archive lineage.

Blog

For Recruiters & Collaborators

Professional overview for recruiters and collaborators seeking a deterministic backend/system engineer

Blog archive2026-04-11

Blog

Real Cost Hidden in ERP Systems: A Developer’s Hard Lesson

A firsthand story of how building an ERP system taught me the painful reality of hidden infrastructure costs—especially for solo developers. This post uncovers unexpected billing from cloud hosting, the contrast with free deployments, and how this experience became my competitive edge.

Blog archive2025-07-02

Blog

🎭 Narrative Comparison: Puss in Boots (2022) vs Reltroner Studio

A philosophical narrative analysis between a cat facing mortality and a civilization architect resisting erasure through system design.

Blog archive2025-08-04