MYKOS documentation

These maintained guides include current operational features. Historical design baselines are identified in the guides that retain them.

Supported MYKOS hosts: RHEL 9 and RHEL 10 (x86_64). RHEL 8 host support has been dropped. Guest/image support is separate: RHEL 8 guest recipes remain available.

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

Highlighted feature: Snapshot Preview Inspect a saved point in time in a separate, temporary console without rolling back the running container. Desktop previews resume captured RAM and disks; native Linux previews open the saved filesystem in an isolated shell. How Snapshot Preview works.

See the screen examples gallery for the dashboard, snapshot actions and a separate preview console.

Project design and business value

Read the two-paragraph business pitch.

Guide	Use it for
Screen examples	Dashboard, VPN map and Snapshot Preview screenshots with example data
Example use cases	Practical workflows, starting with older applications on newer hardware
Security by design	Trust boundaries, identity, privileged operations, data protection, and deployment limits
Key innovations	Technical leadership overview of the design contributions
Performance by design	Engineering milestones, difficult problems, and the whole-instance design rationale
Deployment efficiency and business value	Business scenarios, customer self-service, cost-saving mechanisms, and an illustrative savings model

The key innovations, performance by design, and deployment efficiency guides include downloadable PDFs retaining their reviewed release146 baseline. Current task guides describe later operational additions; planned compliance scanning and alerts remain clearly marked as future work.

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 EL9 and EL10 host 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
Credits	Vendor and project logos, acknowledgments, Dell, Teleflora, Codex, and ChatGPT
References	Upstream projects, dependencies, compatibility references, development tools, and OS vendor sites
API usage	Authentication, endpoints, examples, and errors
OpenAPI specification	Machine-readable API schema
Developer’s guide	Human handoff, code walkthroughs, safe setup, tests and changing the system
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
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.

Documentation build

See the maintained build workflow for dependencies, rendering, link checks and the production operator-edit guard. Generated HTML keeps the permanent light theme.

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.