This documentation hub covers architecture, design model, deployment patterns, operational analytics, security controls, and troubleshooting. Use it as your single reference from pilot to stable production.
Use this map to open the right runbook for your environment and ownership model.
Full cloud runbook with prerequisites, ingress, storage, and validation.
Step-by-step Google Cloud Platform deployment — Compute Engine, VPC, Cloud DNS, SSL, Load Balancer, monitoring, backups, and security hardening.
Package install, service setup, backup strategy, and hardening controls.
IIS, service installation, firewall, and operational baseline validation.
Tenant-aware architecture and scaling decisions.
Diagnose crashes, fix service failures, recover from outages, and resolve common production issues.
In-depth reference guides covering OS compatibility, every platform module, and agent deployment.
Server and agent OS support matrix, hardware requirements, software prerequisites, database setup, firewall ports, user permissions, and satellite server requirements.
Step-by-step how-to for all 25+ modules: CMDB, Monitoring, Incidents, Changes, Problems, Service Requests, Auto-Healing, Capacity, Vulnerability & Patch, Alert-to-Incident, Automation, Directory & IAM, Knowledge Base, RCA & Forensics, User Sync, Explainable AI, Global Communications, Auto Ticket Assignment, Server Build & Provisioning, Feature Toggles, Status Page, Ticket Audit, KPI Dashboard, and People Communication.
Complete agent deployment for Linux (Ubuntu, RHEL, SUSE, Amazon), Windows (GUI and silent), and macOS. Includes registration, auto-healing permissions, verification, upgrades, and troubleshooting.
Consolidated security guide covering 4 service accounts, 6 application RBAC roles, database grants, OS-level user configuration, credential rotation, and compliance framework mapping for all 25+ modules.
MinusNow follows layered separation across experience, API orchestration, persistence, and telemetry ingestion. Each layer can scale independently while retaining a single source of truth for incidents, CMDB, and audit records.
Events enter via API actions and endpoint agents, then are normalized and enriched with source metadata.
Rules and scoring correlate incidents, assets, vulnerabilities, and patch obligations.
Workflows trigger tickets, notifications, AI-powered ownership assignment, explainable recommendations, and remediation traces with global communications delivery.
| Model | Best For | Core Components | Tradeoffs |
|---|---|---|---|
| Single Node Pilot | Fast proof-of-value and demos | App + DB + storage on one host | Limited resilience |
| Standard Production | SMB and mid-market operations | 2 app nodes, managed DB, reverse proxy | Moderate ops overhead |
| High Availability | Enterprise SLA-driven environments | Load balancer, multi-node app tier, HA DB | Higher design and run cost |
| Hybrid Deployment | Regulated segmented networks | On-prem control plane + cloud analytics | Complex network integration |
# 1) Download installer curl -fsSL /documentation/downloads/install-linux.sh -o install-linux.sh # 2) Install under /opt/MinusNow sudo bash install-linux.sh /opt/MinusNow MinusNow # 3) Install endpoint agent curl -fsSL /documentation/downloads/agent-install-linux.sh -o agent-install-linux.sh bash agent-install-linux.sh # 4) Validate API health curl http://localhost:5000/api/telemetry/health
# 1) Download installer Invoke-WebRequest -Uri /documentation/downloads/install-windows.ps1 -OutFile install-windows.ps1 # 2) Install service ./install-windows.ps1 -InstallDir "C:\MinusNow" -OpenFirewall -ServiceName "MinusNow" # 3) Install endpoint agent Invoke-WebRequest -Uri /documentation/downloads/agent-install-windows.ps1 -OutFile agent-install-windows.ps1 ./agent-install-windows.ps1 # 4) Validate service and health Get-Service MinusNow
| KPI | Formula | Target | Action Trigger |
|---|---|---|---|
| Critical MTTR | Sum resolution time / incident count | Under 60 minutes | Escalate on 2-day average breach |
| SLA Breach Rate | Breached tickets / total tickets | Under 3 percent | Review assignment and handoff policy |
| Patch Compliance | Patched assets / eligible assets | Above 95 percent | Open remediation campaign by unit |
| Alert Noise Ratio | Non-actionable alerts / total alerts | Under 30 percent | Tune thresholds and dedup rules |
| Agent Freshness | Agents reporting within 15m / total agents | Above 98 percent | Investigate endpoint connectivity |
Define a master system per entity (ticket, asset, user, vendor, vulnerability) and version each integration contract. This avoids data drift and conflicting ownership.
Email, chat, SIEM, and reporting integrations for visibility and routing.
Endpoint agents, infra telemetry, and patch execution channels.
Scheduled and event-based sync with dedup and conflict policy.
Retry queues, dead-letter review, and runbook ownership.
Check reverse proxy routing, certificate bindings, firewall policy, and upstream API health endpoint.
Validate endpoint service status, outbound connectivity, TLS trust chain, and registration token validity.
Verify SMTP host, port, auth mode, and relay restrictions, then run direct message diagnostics.
Inspect pre-check output, maintenance windows, reboot policy, and dependency order. Use phased rollout with canary groups.
Review query plans, index coverage, connection pools, and storage latency. Archive stale records if needed.
