TrueCore Hosting

TrueCore is a privacy-first, low-bloat hosting platform built around the idea that web infrastructure should be understandable, deterministic, and owned by the people running it. At its core, TrueCore is not trying to be another glossy reseller panel glued together from heavy third-party systems. It is a full-stack hosting ecosystem: DNS, web hosting, mail, SSL, customer isolation, support, billing integration, monitoring, backups, security, and recovery, all designed to work together under one human-readable operating model. The philosophy is simple: less magic, more control. TrueCore rejects the modern trend of bloated, opaque infrastructure where every service depends on layers of containers, dashboards, agents, orchestration tools, and mystery state. Instead, TrueCore aims to be inspectable. Configuration should live in clear files. Services should have obvious names. Logs should be readable. Recovery should be possible without a cathedral of hidden dependencies. The project is built around the wider FlameOS / FlameCore stack: a custom Linux-style infrastructure layer made from small purpose-built components. Rather than relying on systems like Kubernetes, Docker, or large control planes, TrueCore uses direct binaries, TOML configuration, simple process supervision, explicit networking, and predictable file layouts. A normal hosting customer should never need to care about that complexity. From their perspective, TrueCore is a hosting company offering fair pricing, honest limits, support, websites, domains, mail, SSL, backups, and a customer portal. But under the hood, it is something much more ambitious: a self-built hosting operating system. TrueCore includes components such as: flame-super — the service supervisor. This manages TrueCore services, restarts failed components, handles service state, and is intended to eventually become the system’s main init layer. flame-dnsd — the authoritative DNS daemon. This handles DNS zones directly from TrueCore’s own configuration files instead of depending on a bloated external DNS control panel. flame-guardian — the security guard. This watches logs, detects suspicious activity, bans hostile traffic, and can sync bans across the fleet. flame-bubble — the customer isolation layer. Each customer can be placed inside a restricted environment with network and filesystem controls, keeping hosting accounts separated from each other and from sensitive management services. flame-mod-web — the web hosting module. This handles web vhosts, nginx lifecycle, SSL handling, site configuration, and hosting plan logic. FlameX / flame-mail / flamerelay — the mail layer. This is intended to provide mail handling, spam filtering, relay logic, authentication checks, and user-level controls. flame-panel — the control panel. This includes the customer portal and operator/admin panel: tickets, support, sites, billing-related status, capacity, loyalty stars, security controls, and possibly future site editing. flame-sentinel / flame-doctor / flame-watch — the health and security tooling. These check node health, configuration problems, backups, service status, suspicious file changes, and operational risks. The current TrueCore infrastructure is planned as a fleet, not a single-box toy. Nodes have specific roles: primary services, secondary nameservers, web nodes, mail nodes, and monitoring/security functions. WireGuard is used internally, allowing nodes to communicate over a private network. Public services can be exposed cleanly, while management traffic remains private. A major design goal is that TrueCore should be able to survive real problems: failed nodes, bad updates, broken configs, exploit attempts, corrupted services, or operator mistakes. That is why the project includes signed releases, backup verification, recovery vault planning, restic backups, node health checks, and rollback thinking. The customer-facing side is meant to be brutally honest. No fake “unlimited” hosting. No introductory scam pricing. No pretending a £2 hosting plan has infinite CPU, RAM, storage, and support capacity. TrueCore’s plan model is based on understandable resource units and visible capacity. The idea is to tell customers what they are buying and not bury the truth in marketing sludge. Support is also part of the core identity. TrueCore is designed to have a real ticket system with priorities, queue positions, estimated response times, customer replies, operator notes, Discord alerts, and AI-assisted diagnostics. The AI is not meant to replace the operator blindly; it is meant to gather facts, suggest fixes, and reduce repetitive checking.