Skip to content

minato Documentation

minato (南) is 7KGroup's Kubernetes-native platform for hosting persistent, multi-game dedicated game servers. It is designed for enterprise use cases: hosting providers running many games for many tenants, and operators running large fleets of persistent worlds for a single game. A game-agnostic operator reconciles CRDs into Kubernetes resources, while per-game agents (sidecars) encapsulate all game-specific knowledge — RCON dialects, lifecycle quirks, and action execution — behind a public, versioned gRPC API.

minato on GitHub

What lives here

Section Contents
Architecture How the platform fits together: the Architecture Overview and the Controller Flow.
Operations Running minato in production: installation, configuration, the CLI, multi-tenancy, scalability, metrics, security, and troubleshooting.
Runbooks Operational procedures for common failure modes: unreachable agents, crashlooping operators, pending PVCs, and pending StatefulSets.
Compliance Compliance posture and controls mapping.
Security The security model: control plane authentication & authorization and the communication security architecture.
Agent Developers Building a per-game agent: the quickstart, SDK reference, API stability guarantees, and the console streaming protocol.
Design Design explorations and assessments, including modern Kubernetes features and server sharding.

Why we publish this

Engineering buyers trust what they can read. Our architecture, our decisions, and our operational runbooks are public because they're the strongest evidence of how we work. If you're evaluating minato, your engineers should start here.