Glassmkr Documentation

#Start here

Two decisions, in order.

1. Choose where the dashboard runs. Self-host the whole stack from one compose file, with no node limit and no license key, or use the hosted service and skip operating it. Self-hosting guide Hosted signup
2. Install the agent on each machine you want to watch. The apt and dnf/yum families (Debian, Ubuntu, RHEL, Rocky, AlmaLinux, CentOS, Fedora) have a one-line installer; other glibc distributions with systemd use the single-file binary, which needs no Node. Getting started
3. Confirm the first snapshot arrives, then route notifications and tune what fires. Notification channels Configuration

Not ready to install anything? Paste command output into ChatGPT or Claude and the same alert rules read it, with no account.

#Guides

• Getting startedInstall the agent three ways, and which one your distribution needs.
• Self-hostingThe compose stack, backups, upgrades, retention, and pointing agents at your own dashboard.
• ConfigurationEvery field in crucible.yaml, with defaults and bounds.
• Notification channelsWhere alerts go, and what each channel needs.
• Alert rulesAll 72 rules, what each one watches, and the remediation it carries.
• Programmatic APIAccount keys, scopes, rate limits, idempotency, and error shapes.
• Automated onboardingEnrolling hosts from Ansible, Terraform or a script.
• MCPGiving an AI client your own fleet's health and alerts through scoped OAuth, and what self-hosting it requires.
• ChatGPT and ClaudePaste command output into an AI assistant and get a verdict from Glassmkr's own alert rules. No account needed.
• TroubleshootingWhen the agent will not start, or snapshots do not arrive.
• FAQThe questions that come up before people install anything.
• ChangelogWhat changed, by release.

#For machines

Every guide is served as Markdown at its own URL with a .md suffix, and every alert rule at /docs/rules/<rule_id>.md. The whole corpus in one file is at /llms-full.txt, indexed by /llms.txt. Fetch those rather than scraping HTML.