Wazuh Multi-Tenant Client Dashboard

tools · $149.99

Give every client their own SOC dashboard from the Wazuh you already run

Running Wazuh for multiple clients? Then you know the dilemma: the built-in dashboard shows everything to everyone. So you either hand clients a login and pray they don't click around, or you screenshot panels into a monthly PDF nobody reads.

Neither feels like the managed security service they're paying you for.

This product sits on top of your existing Wazuh, read-only, no changes to your SIEM and gives each client an isolated, branded login:

  • True tenant isolation, enforced server-side. Every query is scoped by the signed session, not the browser. A client can't reach another client's data no matter what they send to the API.

  • White-label per client. Your product name on the login screen, each client's own name across their console. Company A signs in and sees their SOC not your tooling.

  • Zero-panel default. New clients start with no visualizations. You explicitly grant each of the 17+ panels, alert volume, MITRE ATT&CK, compliance coverage, vulnerabilities, geolocation map, and more. Least privilege, by design.

  • Onboarding in seconds, not cycles. Creating a client triggers an immediate ingest. By the time you've created their login, their panels are populated.

  • Honest by default. Freshness timestamps, per-source health pills, a stale badge after missed cycles, and labelled placeholders instead of broken charts when a module is off.

The NeetroX Wazuh SOC console on a seven day view: 119.5 thousand alerts, 0 critical with 12 high, 4 of 4 agents active, 625 vulnerabilities and 0.09 average events per second, above an alert volume chart, a severity donut reading 112,164 low and 7,365 medium, and a table of high and critical alerts by agent and rule

How it works (3 steps)

  1. Configure one .env file - your Wazuh Indexer and Manager credentials, your branding, your admin login. No hardcoded secrets.

  2. Run docker compose up - Postgres, ingest worker, API, and dashboard start as one self-contained stack.

  3. Create clients in the admin console - map each one to their Wazuh agent groups, tick the panels they get, add their login. Done.

Video Demo

Who This Is For

  • MSSPs running Wazuh for multiple clients who need scoped, branded dashboards without building the isolation layer themselves

  • Security engineers currently sharing one login across internal teams who know it's not really access control

  • Teams who want a self-hosted option with no per-seat or per-agent licensing

  • Anyone who's outgrown a shared Kibana/OpenSearch login for client-facing reporting

7-day guarantee

If it doesn't work as described, or it isn't what you needed, contact us within 7 days of purchase and we'll refund you in full. If you'd rather have it working, say so and we'll help you get it running. Your call. Full terms.

← Browse all products