Rainbow RMS

Server foundation is online.

Laravel is running on Apache with MySQL-backed sessions, cache, and queues. This starter page is intentionally plain Blade, CSS, and CDN JavaScript friendly.

Apache Serving Laravel from the public directory.

MySQL Application database migrations are ready.

Jobs Queue and scheduler hooks are prepared.

Integrations

Rainbow RMS is the Laravel control plane that ties together the monitoring, logging, config history, and backup systems that do the specialized work.

LibreNMS + Oxidized Network device health, interface visibility, alerts, and Git-backed router/switch/firewall configuration history.

Zabbix Windows, Linux, VMware, database, DHCP, DNS, and service monitoring with templates and problem tracking.

Wazuh Windows Event Logs, Linux security events, file integrity monitoring, failed logons, and security alerting.

Syslog + Loki Centralized logs from network devices, servers, VMware, and appliances with searchable operational history.

Grafana Detailed dashboards and visualizations embedded or linked from the Laravel single pane of glass.

Config Manager Rainbow-managed Linux and Windows configuration snapshots, diffs, drift detection, and restore workflows.

How it Works

One Laravel app owns the inventory and workflow. The backend tools keep running independently, while Rainbow RMS pulls their status into a single operational view.

1. Inventory first Admins add devices, servers, databases, and services once, then tag them for roles like DHCP, DNS, Linux, Windows, or network.

2. Connect tools Monitoring sources store API endpoints and credentials for LibreNMS, Zabbix, Wazuh, Loki, Grafana, Oxidized, and backup status checks.

3. Aggregate alerts Laravel workers sync health, problems, events, logs, and backup freshness into one dashboard and alert inbox.

4. Track changes Oxidized and Rainbow Config Manager keep Git-backed config history so teams can review what changed and when.

5. Govern actions Roles, audit logs, notes, and restore requests keep operational actions visible and permission-aware.

6. Enable MCP safely Read-only AI tools can query status, alerts, logs, and config diffs before any higher-risk automation is added.