Skip to main content

Roadmap

The product was built in eight phases (0–7). The detailed plans and checklists are in the repository (docs/rmm-implementation-plan.md, docs/plans/phase-*.md, docs/roadmap.md).

PhaseScopeStatus
0Scaffolding: monorepo, dev stack, codegen, CIDone
1Identity, tenants, RBAC, auditDone
2Agent, enrollment, inventory, devices, live updatesDone
3Site connector, AD sync, agent pushDone
4Packages and mass deploymentDone
5Scripts, remote actions, alerts, self-updateDone
6Hardening and production readinessDone in the lab; release 1.0 pending
7Entrosity Hub: sign-in and user management move to a separate service at hub.entrosity.com; users can belong to several organizations; Axis runs at hub.entrosity.com/axis and keeps no credentialsDone

Open for 1.0​

  • Tag v1.0.0 (the release workflow builds the images, signed MSIs and SBOMs). After tagging, move dev builds to the beta channel (Agent releases).
  • Maintainer sign-off of the security review.
  • Manual acceptance checks on real Windows machines and a domain: the MSI one-liner, connector push over WinRM, run-as-user scripts and installs, a self-update and a watchdog rollback.

Known limitations​

  • An organization removed on Entrosity Hub only suspends the tenant in Axis; purging a tenant's data is not implemented.
  • The device software filter is the slowest list query at 50,000 devices (p95 ≈ 540 ms).

Later​

Out of scope for 1.0; the design allows them:

  • OIDC / Entra ID sign-in (in Entrosity Hub)
  • Remote desktop and remote terminal
  • Windows patch management (WUA)
  • macOS and Linux agents
  • Ticketing / PSA integrations and billing