Supported
You can plan normal TvRMM use for these endpoints. Specific actions still follow your role, policy, billing limit, and the endpoint state.
Mixed-fleet support without pretending every platform works the same.
TvRMM shows what each platform is good for in customer terms: everyday endpoint management, host visibility, appliance guidance, or inventory-only awareness.
Support state labels.
Use these labels to decide whether a platform is ready for normal rollout, needs a fit check, or is visible for inventory only.
Beta / evidence
Useful for selected customers and scenarios, but best reviewed with support before making it a standard rollout target.
Install verified
TvRMM has real enrolled endpoints checking in for this platform family. Use the row notes to see which customer workflows are a good fit today.
Inventory-only
TvRMM can show the item for visibility, but direct patching, scripts, terminal, or remote desktop need a real agent inside that VM or container.
Guided fit
Contact TvRMM before production rollout so appliance update, storage, firewall, or permission boundaries are handled correctly.
Agent platforms and support states.
This matrix is written from the customer point of view: what you can use the platform for, when to involve support, and when an in-guest agent is needed.
| Platform | State | Best fit | What customers can expect |
|---|---|---|---|
| Windows x64 / ARM64 | Supported | Workstations and servers | Use for everyday endpoint management: enrollment, inventory, Windows update workflows where available, scripts, reboot controls, tray diagnostics, remote desktop helper, agent updates, and cleanup. |
| macOS Intel / Apple Silicon | Supported | Mac workstations | Use for Mac enrollment, inventory, audit, package-aware maintenance, tray diagnostics, agent updates, and cleanup. Remote desktop is available when the Mac has the required helper and local privacy permissions. |
| Generic Linux | Supported | Linux servers and desktops | Use for standard Linux enrollment, inventory, scripts, service-aware operations, reboot controls, agent updates, cleanup, and remote desktop on supported GUI systems. |
| Debian / Ubuntu / Raspberry Pi OS | Supported | Apt-based Linux fleets | Use for common server, desktop, and small-device fleets with inventory, scripts, reboot controls, patch scans and installs where repositories allow, agent updates, cleanup, and remote desktop helper support on GUI endpoints. |
| Proxmox VE | Supported | Virtualization hosts | Use on Proxmox hosts to see nodes, guests, storage, backups, HA, firewall, ZFS, network bridges, and recent task health. Install an agent inside important VMs or containers when you want direct in-guest management. |
| Unraid | Supported | Storage and lab hosts | Use on Unraid hosts to see array state, shares, disks, plugins, Docker containers, VMs, and supported host actions. Keep Unraid OS and plugin updates in the Unraid UI unless TvRMM shows a specific supported action. |
| FreeBSD amd64 | Beta / evidence | BSD systems | Use where you need enrolled FreeBSD identity, check-in, and inventory evidence. Review patching, service control, and cleanup expectations with support before broad rollout. |
| Fedora / RHEL / Rocky / AlmaLinux / CentOS | Install verified | RPM-family Linux | Use for RPM-family enrollment, visibility, scripts, cleanup, agent updates, and distribution-aware patch evaluation. Confirm repository and patch-install expectations before broad production rollout. |
| openSUSE Leap | Install verified | openSUSE systems | Use for openSUSE enrollment, inventory, scripts, cleanup, agent updates, and update visibility. Confirm patch-install policy during rollout planning. |
| SLES | Beta / evidence | SUSE enterprise systems | Use for SUSE-family environments after a fit check, especially where you need inventory and scripted operations. Confirm update and support expectations during onboarding. |
| Arch Linux | Install verified | Rolling Linux systems | Use for Arch enrollment, inventory, scripts, cleanup, and agent updates. Rolling OS updates are best managed through your normal maintenance policy unless TvRMM presents a supported action. |
| Manjaro | Beta / evidence | Rolling desktop Linux | Use for selected Manjaro endpoints after a fit check, especially for visibility and scripted operations. Confirm update expectations before relying on it for production maintenance. |
| Alpine Linux | Install verified | Lightweight Linux systems | Use for lightweight servers and appliance-style Linux systems that need enrollment, inventory, scripts, cleanup, and check-in visibility. Advanced workflows may need support review because Alpine systems are often minimal. |
| Amazon Linux / Linux Mint / DietPi | Install verified | Specialty Linux systems | Use for specialty Linux systems where standard enrollment and check-in are validated. Match patching and remote desktop expectations to the specific distribution during rollout planning. |
| OPNsense / pfSense | Guided fit | Firewall appliances | Contact TvRMM before production use. Firewall appliances need careful install, update, reboot, and safety boundaries so management visibility does not interfere with firewall-native operations. |
| Synology DSM | Install verified | NAS appliances | Use for Synology DSM visibility and agent check-in on NAS devices. Keep storage, package, and appliance administration in DSM unless TvRMM exposes a specific supported action. |
| TrueNAS SCALE | Guided fit | Storage appliances | Contact TvRMM before production use. TrueNAS is a storage appliance, so enrollment, persistence, updates, and reboot behavior need to respect the supported TrueNAS management model. |
| CasaOS / OpenMediaVault | Install verified | Home and small NAS systems | Use for Debian-based home, lab, and small NAS systems where enrollment and check-in are validated. TvRMM can help with visibility and normal Linux operations while app and storage settings remain in the appliance UI. |
| UniFi OS | Beta / evidence | Network appliances | Use as a guided-fit conversation for appliance visibility. Network configuration should remain in UniFi management tools unless TvRMM documents a specific supported workflow. |
| VMs, LXCs, Docker containers | Inventory-only | Host-reported workloads | Use host-reported rows to understand what is running on Proxmox or Unraid. Install a TvRMM agent inside a VM or container when you want direct patching, scripts, terminal, remote desktop, or billable endpoint management. |
Real endpoint validation.
TvRMM validates platform coverage with real enrolled endpoints that check in successfully. For customers, this means install, enrollment, heartbeat, and OS identification have been exercised on representative systems.
| Platform group | Validation context | Why it matters |
|---|---|---|
| Windows and macOS | Desktop operating systems | Windows and Mac endpoints are enrolled as real agents so mixed workstation fleets are part of the validation set. |
| Debian and Ubuntu family | Common server and lab Linux | Debian, Ubuntu, CasaOS, and OpenMediaVault-style systems are represented so the most common Linux server paths are exercised. |
| RPM-family Linux | Enterprise and community Linux | AlmaLinux, Rocky, Fedora, CentOS Stream, and Amazon Linux are represented for customers with RHEL-style fleets. |
| openSUSE, Arch, and Alpine | Less-common Linux families | openSUSE Leap, Arch, and Alpine are represented so validation is not limited to apt and RPM systems. |
| Specialty Linux | Small-device and desktop variants | Linux Mint and DietPi are represented for customers managing lightweight systems or nonstandard Linux desktops. |
| Homelab and NAS appliance agents | Real appliance-style hosts | Unraid and Synology DSM are represented because customers often need visibility into hosts that are not generic servers. |
| Host-observed guest inventory | VM and container visibility | Unraid Docker and VM rows show virtualized workloads without billing them as direct agents unless an in-guest agent is linked. |
What support means in daily work.
Platform support is easiest to understand by workflow: enrolling the endpoint, seeing useful facts, running actions, and knowing which tool owns sensitive appliance changes.
| Workflow | What customers can expect |
|---|---|
| Enrollment | Supported and install-verified platforms are meant to start from portal-provided install guidance. Some appliances may require a guided fit check before rollout. |
| Inventory and audit | Direct agents report endpoint facts such as OS, hardware, software, storage, and health. Homelab hosts add useful guest and storage context. |
| Patching | Patch controls appear where TvRMM can use the operating system or appliance-supported update path safely. Some appliances remain best managed in their native UI. |
| Scripts and terminal | Direct agents are the normal path for scripts and terminal sessions. Install an in-guest agent when a VM or container needs direct management. |
| Remote desktop | Supported direct agents can use TvRMM remote view/control through the authenticated relay when policy, helper, license, role, and relay checks pass. No customer-side VNC/RDP port should be required. |
| Billing | Only active real agents are billable. Guest inventory rows, archived endpoints, deleted endpoints, and 30-day-offline agents are excluded under the billing policy. |