Server guide
Minecraft dedicated server: a calm defaults-first setup
Paper versus Vanilla, JVM heap sizing, ports, and restart hygiene.
Guides and deep dives
Writeups from the operations side of the business. They exist because we would rather you understood your infrastructure than depended on us for trivia, and they stay useful whether or not you ever buy anything.
Server guides
Build and operate specific workloads without guessing at the defaults.
Server guide
Valheim dedicated server on Linux
SteamCMD, systemd supervision, UDP ports, and world persistence.
Server guide
Factorio headless: boring reliability beats clever
Application directories, autosave cadence, and multiplayer discovery.
Server guide
Terraria hosting: crossplay without the mystery errors
Port 7777, server passwords, and world file hygiene across platforms.
Operations
Docker for game servers: clarity over hype
Reproducible builds, update flow, and where containers stop helping.
Operations
Backups and snapshots: keep rollback boring
Snapshot timing, off-site copies, and restores you have actually rehearsed.
Networking
The layer that breaks most self-hosted projects before the software does.
Networking
Port forwarding that actually works
TCP versus UDP, static maps, hairpin NAT, and verifying from outside.
Networking
Double NAT and CGNAT: the silent party crashers
Symptoms, diagnosis, and when a hosted relay is the honest answer.
Networking
UPnP versus static maps: convenience against clarity
Security posture and reproducibility, and which belongs on a real network.
Game operations
Running a live community: patches, performance, and the things players notice.
Game operations
Live-service patches: schedule the disruption
Staged rollouts, communication templates, and a usable rollback posture.
Game operations
Tick rate, TPS, latency: separate the villains
How to measure each, and which bottleneck you actually have.
Game operations
Voice and game traffic: do not starve the upload
QoS and upload headroom so comms and gameplay coexist.
Mods and extensions
Extending a server without turning every update into an incident.
Mods
Minecraft Paper: first plugins that earn their keep
Moderation, logging, and backups before anything decorative.
Mods
tModLoader servers: keep crash logs boring
Memory headroom, load order, and crash log triage.
Mods
ARK modded: stability is a feature
Load order, update windows, and crash triage for clusters.
How we work
What you get from a small operator, and how we run engagements.
How we work
Small host, big context
Continuity of context, real change control, and honest diagnosis.
How we work
English-speaking teams, anywhere on the clock
Asynchronous updates, clear handoffs, and scheduled windows.
Prefer to hand it over
Every guide describes something we also run as a managed service. If reading it made you decide you would rather not, that is a legitimate outcome.