Documentation

System Ops brings host resources, runtime inventory, logs, and optional monitoring integrations into one self-hosted console for a single Ubuntu VPS.

Start here

• Quick start: install and open the console.
• Installation: native Ubuntu/systemd, Docker, and deployment limits.
• Configuration: credentials, binding, storage, and integrations.
• Troubleshooting: common permission, discovery, and update failures.

Operate

• Authentication
• Integration discovery
• PM2 monitoring
• Discovery and navigation
• Availability checks, alerts, and metrics
• Persistent history and incidents
• Traffic retention
• Updates and recovery
• Atomic release details
• API overview

Develop and contribute

• Contributing
• Architecture
• Collector ownership
• Collector scheduling
• Release process
• Publish the public site
• Resource measurements
• Reliability evidence
• Support, security, and governance

The public site renders these maintained Markdown sources. Run npm run docs:build before publishing web/. Historical planning files under docs/superpowers/ are design records, not current installation instructions.

Scope

Native Ubuntu/systemd is the primary host-monitoring deployment. Docker provides a narrower view. Integration availability depends on installed services, permissions, and configuration. The console uses one administrator password; it does not provide multi-user roles. Backup listings and log indicators do not prove restorability. Memory, uptime, and deployment claims need measured evidence from the relevant environment.