Revise Immortal Hosting documentation for clarity

Updated the content to enhance clarity and detail about the Immortal Hosting architecture, including changes to the introduction, leadership roles, infrastructure, CI/CD processes, security measures, and tech stack summary.

Author: m3ow-dev

content/post/immortal-host/index.md

@@ -1,108 +1,82 @@
 ---
 title: Immortal Hosting
-description: What is immortal.host?
+description: Inside the architecture of immortal.host
 slug: immortal-host
 date: 2025-07-30 00:00:00+0000
 tags:
  - immortal.host
 ---
 
 ## Introduction
-[Immortal Hosting](https://immortal.host)
- is not just a standard hosting provider; it is a sophisticated, self-managed infrastructure project designed to deliver high-performance application and game server hosting. Built on a foundation of modern DevOps practices, it leverages container orchestration, edge computing, and high-availability database clusters to ensure resilience and scalability.
 
-Below is a technical resume of the architecture and technologies currently powering the **Immortal.host** ecosystem.
+[Immortal Hosting](https://immortal.host) is a high-performance infrastructure project built on modern DevOps practices. More than just a hosting provider, it is a self-managed ecosystem leveraging container orchestration, edge computing, and high-availability clusters to deliver resilient application and game server hosting.
 
 ## Leadership & Architecture
 
-As the **Founder and Lead Architect**, I am responsible for the end-to-end design, implementation, and maintenance of the entire Immortal Hosting ecosystem. My role encompasses:
+As **Founder and Lead Architect**, I manage the lifecycle of the entire platform—from the metal up to the frontend. My focus includes:
 
-* **Strategic Architecture:** Designing a cloud-agnostic, containerized infrastructure capable of scaling from a single node to a distributed cluster.
-* **Full-Stack Development:** Spearheading the development of the frontend interfaces (Next.js) and integrating them with backend APIs and game server protocols.
-* **DevSecOps Implementation:** Enforcing a security-first mindset by implementing Zero Trust networking, rootless containers, and centralized identity management.
-* **Operational Leadership:** Managing the day-to-day operations, from database optimization to establishing the disaster recovery protocols that keep client data safe.
+* **Strategic Architecture:** Designing cloud-agnostic, containerized infrastructure that scales from single nodes to distributed clusters.
+* **Full-Stack Development:** Building reactive interfaces with Next.js and integrating them with backend game protocols.
+* **DevSecOps:** Enforcing a Zero Trust mindset with rootless containers and centralized identity management.
+* **Operations:** Handling everything from database tuning to disaster recovery protocols.
 
 ## Infrastructure & Orchestration
 
-At the heart of Immortal Hosting lies a commitment to modern containerization and orchestration standards. Moving beyond simple bare-metal deployments, the infrastructure utilizes **Kubernetes** to manage workloads dynamically.
+We moved beyond simple bare-metal deployments to a fully orchestrated environment.
 
-* **Kubernetes (K8s):** The core control plane for deploying and managing services. The environment utilizes custom YAML configurations to orchestrate complex deployments, ensuring that services like database clusters and control panels remain available and scalable.
-* **Rootless Podman:** For enhanced security and granular container management, the infrastructure leverages Rootless Podman. This allows containers to run without root privileges, significantly reducing the attack surface while maintaining full OCI compliance.
-* **Docker Compose:** Utilized for defining and running multi-container applications, ensuring reproducible development and production environments.
+* **Kubernetes (K8s):** The control plane. We use custom YAML configurations to orchestrate complex workloads, ensuring high availability for databases and control panels.
+* **Rootless Podman:** Used for granular security. Running containers without root privileges significantly reduces the attack surface while maintaining OCI compliance.
 
 ## CI/CD & Automation
 
-Efficiency and reliability are driven by automated pipelines, ensuring that code moves from development to production seamlessly.
+Code moves from development to production through a strict, automated pipeline.
 
-* **Managed Private Gitea:** The ecosystem is powered by a private, self-managed **Gitea** instance. This acts as the central hub for version control, hosting both application source code and Infrastructure-as-Code (IaC) repositories securely.
+* **Managed Private Gitea:** Our central hub for version control, hosting both application source code and Infrastructure-as-Code (IaC).
 ![Git](git.png)
-* **CI/CD Runners:** Integrated CI/CD runners are deployed to automate the software lifecycle. These runners handle testing, building, and deploying applications directly to the Kubernetes clusters, ensuring rapid iteration cycles and consistent delivery.
+* **CI/CD Runners:** Automated runners handle testing, building, and deployment directly to the Kubernetes clusters, ensuring rapid and consistent delivery.
 
-## Identity & Access Management
+## Security & Identity
 
-Security starts with identity. To protect the ecosystem, a unified authentication layer has been implemented across the board.
+Security isn't an afterthought; it's the foundation.
 
-* **Authentik:** The infrastructure relies on **Authentik** as the central Identity Provider (IdP). This creates a seamless Single Sign-On (SSO) experience while enforcing strict access policies for all internal tools and panels.
+* **Authentik (SSO):** A unified identity layer. **Authentik** acts as the central Identity Provider (IdP), enforcing strict access policies and providing Single Sign-On across all internal tools.
 ![Auth](auth.png)
+* **Zero Trust Networking:** By combining strict routing with trusted proxies, origin servers remain obfuscated and protected from direct internet exposure.
 
-## Database Architecture
+## Data & Game Management
 
-Data integrity and availability are prioritized.
+We prioritize data integrity and low-latency performance for gaming workloads.
 
-* **Backups:** S3 offsite backups are put in place for essential services, and a continuous backup policy is utilized to make sure even in the worst of disasters, the client's data is safe and sound.
-* **Containerized Deployment:** Everything is deployed via Kubernetes, Podman, or Docker, allowing for seamless updates and resource isolation.
-
-## Game Server Management
-
-A primary function of the infrastructure is hosting low-latency, high-performance game servers.
-
-* **Pelican Panel:** The infrastructure utilizes **Pelican Panel**, a modern, open-source game server management panel. This provides a centralized interface for deploying and managing game server instances.
+* **Database & Backups:** We utilize **MariaDB** in a high-availability cluster. For safety, we enforce continuous automated offsite S3 backups.
+* **Pelican Panel:** A modern, open-source interface for deploying and managing game server instances.
 ![Panel](panel.png)
-* **GTA V / FiveM:** A key workload includes **FiveM** servers, optimized for GTA V roleplay and gaming communities. The network is tuned to handle the UDP traffic and real-time demands of multiplayer gaming.
 
-## Networking & Security
+## Networking Stack
 
-The network stack is designed for speed, security, and ease of management, utilizing a modern reverse proxy architecture.
+Speed and security are balanced using a modern reverse proxy architecture.
 
-* **Caddy Web Server:** Unlike traditional heavyweights like Nginx or Apache, Immortal Hosting uses **Caddy** as its primary web server and reverse proxy. Caddy handles automatic HTTPS certification and routes traffic efficiently to internal backend services.
-* **Cloudflare Integration:** The entire domain sits behind **Cloudflare**. This provides:
-    * **DDoS Protection:** Shielding the infrastructure from Layer 3/4 and Layer 7 attacks.
-    * **DNS Management:** Fast propagation and secure DNS resolution.
-    * **Edge Caching:** Improving load times for web interfaces.
-* **Zero Trust Principles:** By combining Caddy's strict routing with Cloudflare's trusted proxies, the origin servers are obfuscated and protected from direct internet exposure.
+* **Cloudflare Integration:** Sitting in front of the stack, Cloudflare provides edge caching, DNS management, and critical DDoS protection against Layer 3/4 and Layer 7 attacks.
 
-## Operations & Reliability
+## Operations & Web
 
-Maintaining high uptime requires vigilance and a proactive stance on support.
-
-* **Continuous Monitoring:** The health of the infrastructure is tracked in real-time. Automated monitoring systems keep a pulse on server metrics, container health, and network latency.
+* **Monitoring:** We track infrastructure health in real-time. Automated systems monitor server metrics, container status, and network latency.
 ![Monitoring](monitoring.png)
-
-* **Unbeaten Support:** Beyond the code, the human element is a core pillar. As the founder, I provide responsive, technical support, bridging the gap between complex hosting infrastructure and end-user needs.
+* **Support:** As a founder-led project, support is technical and responsive, bridging the gap between complex infrastructure and user needs.
 ![Status Page](status.png)
-
-## Web Development
-
-Beyond infrastructure, the ecosystem supports custom web applications.
-
-* **Next.js (React):** The frontend components (such as landing pages or status dashboards) are built using **Next.js**. This allows for a reactive, component-based UI, capable of handling dynamic content like live server stats or image carousels with multi-language support (English/French).
+* **Frontend:** The public-facing web properties are built with **Next.js (React)**, allowing for dynamic, multi-language content.
 ![Main Website](website.png)
 
-
 ---
 
-## Summary of Tech Stack
+## Tech Stack Summary
 
 | Category | Technology |
 | :--- | :--- |
 | **Role** | **Founder & Lead Architect** |
 | **Orchestration** | Kubernetes, Docker Compose, Rootless Podman |
 | **DevOps / CI/CD** | Private Gitea + Runners |
 | **Authentication** | Authentik (SSO/IdP) |
-| **Database** | MariaDB HA Cluster |
-| **Web Server** | Caddy (Reverse Proxy) |
+| **Database** | MariaDB HA Cluster | 
 | **Network Security** | Cloudflare (DDoS Protection, DNS) |
 | **Game Control** | Pelican Panel |
 | **Frontend** | Next.js (React) |
-
-Immortal Hosting represents a full-stack engineering achievement, merging the complexities of game server hosting with enterprise-grade DevOps practices.