MYKOS documentation

Use these guides to install, operate, integrate, and recover MYKOS. Start with the guide for your task, then follow its prerequisites and verification steps.

Installation and recovery

Guide	Use it for
IP installation and optional domain HTTPS	IP access, optional HTTPS, and bootstrap retries
Installation updates and recovery	Source installation, updates, verification, backup, and restore
RHEL RPM packages	Signed EL8, EL9, and EL10 packages and repositories
Identity management	Browser accounts, permissions, passwords, and API keys

Images containers and networking

Guide	Use it for
Unattended image builds	Build and capture reusable OS images and manage base console sessions
Windows macOS and Ubuntu desktops	VM requirements, private storage, consoles, and snapshots
Managed networking	Container interfaces, VPN modes, persistence, and topology
Guest ballooning	Memory behavior and native snapshot compatibility

Integration and reference

Guide	Use it for
API usage	Authentication, endpoints, examples, and errors
OpenAPI specification	Machine-readable API schema
Architecture and deployed paths	Components, trust boundaries, ownership, and systemd units
Operator script catalog	Commands, menus, helper protocols, and legacy limitations
Validation record	Recorded checks and remaining integration work
Host monitoring review	Observations, findings, and implemented optimizations
Licensing	Licensing status
Third-party icon credits	Bundled icon attribution

Administrator guide and operator notes

The Markdown administrator guide is a reference edition of the guide dated 21 October 2026. Its historical commands and caveats are retained. Use the maintained task guides above for current source procedures. The original Word guide is preserved.

Operator notes retain the author's original text verbatim. They record context and proposals; they do not establish verified deployment behavior.

Diagrams

SVG images display the diagrams without requiring a Mermaid renderer. The editable Mermaid files describe the same nodes and connections. Relative links, Markdown tables, and language-tagged command blocks keep the guides portable across GitHub and Azure Repos.