Entrosity Axis
Entrosity Axis is a multi-tenant remote monitoring and management platform for Windows fleets. One installation serves many customers (tenants). Each tenant's devices report their inventory and health, receive software and scripts, raise alerts, and can be synced from Active Directory.
Entrosity Axis was called Entrosity RMM before. Only the product name
changed. Technical names keep the old rmm prefix so that existing
installations, agents and scripts keep working: RMM_* settings,
rmm-agent.exe and rmm-connector.exe, the RMMAgent and RMMConnector
Windows services, the %ProgramData%\RMM and %ProgramData%\RMM Connector
folders, X-RMM-* headers, the rmm database and the image and service
names in the deployment files.
What it does
| Area | What you get |
|---|---|
| Inventory | Hardware, operating system, installed software (machine and per-user), Windows updates, services, local users and network adapters for every device, refreshed automatically. |
| Monitoring | Heartbeats every minute with CPU, memory and disk metrics; devices go offline after three missed heartbeats. |
| Alerts | Rules for offline devices, low disk, high CPU or memory, outdated agents, failed deployments, failed AD syncs and offline connectors, with e-mail notifications and digests. |
| Software deployment | MSI, EXE, winget and PowerShell packages with detection rules, deployed to device lists, filters or whole tenants, with schedules, maintenance windows, concurrency limits, retries and reboot policies. |
| Scripts | A versioned library of PowerShell, PowerShell 7 and cmd scripts with typed parameters and live output. |
| Device actions | Refresh inventory, reboot, shut down, uninstall software, wake-on-LAN, decommission and merge. |
| Active Directory | A site connector syncs AD computers over LDAP(S) and pushes the agent to them over WinRM or SMB. |
| Self-update | Agents and connectors update themselves from signed releases, with channels, rollout percentages and automatic rollback. |
| Security | Tenant isolation enforced twice (application and PostgreSQL row-level security), one sign-in with argon2id passwords and TOTP on Entrosity Hub, a full audit log, and agents that never accept inbound connections. |
How it fits together
- The portal is a web app for Entrosity staff (global admins) and for the people who look after each customer (tenant users). With Hub sign-in, users sign in on Entrosity Hub, the sign-in portal for all Entrosity products, and open Axis from there.
- The backend is a single Go service: API, WebSocket hub, event streams and background workers. It stores everything in PostgreSQL and files in S3-compatible object storage.
- The agent is a Windows service on every managed PC.
- The site connector is a Windows service on one domain-joined server per customer site. It does everything that has to happen inside the customer network (LDAP, agent push, wake-on-LAN).
Agents and connectors only make outbound HTTPS/WebSocket connections. Nothing on the customer network has to be reachable from the Internet.
Who this documentation is for
| You are… | Start with |
|---|---|
| A technician or tenant administrator using the portal | Concepts, then the User guide |
| A global administrator (Entrosity staff) | Administration |
| Running the server | Operations |
| Integrating with the API | Portal API and the API reference |
| Working on the code | Development setup and the Reference section |
| Using Entrosity Edge (physical access control) | Entrosity Edge |
| Using Entrosity Sphere (video management for NVRs) | Entrosity Sphere |
| Using Entrosity Matrix (computer-room internet control on FortiGate) | Entrosity Matrix |
| Using Entrosity Vertex (Active Directory management) | Entrosity Vertex |
Production installation
Entrosity's production installation runs at
https://hub.entrosity.com/axis/ (users sign in on Entrosity Hub at
https://hub.entrosity.com), and this documentation at
https://hub.entrosity.com/docs/. Every push to main deploys both
automatically (see Continuous deployment).