I'm reviewing alternatives after eight years with a self-hosted support tool. There are about 600 endpoints across Windows, Linux and Mac, including some headless Linux servers.
I'd prefer technician-based pricing over a full remote management suite billed per endpoint. A hosted service is appealing because I want to reduce the burden of maintaining an internet-facing server. What would you look at?
ISL Online is worth a look if remote access is the main job and you don't want to buy a whole management platform. Put it through a trial with your actual mix of machines, especially the headless Linux servers, and check how technician licensing works at your size.
Splashtop is another option for the Windows and Mac side, though headless Linux support may leave a gap. A separate network access tool for those servers could be simpler than making the entire purchase depend on a relatively small group of machines.
Hosted ScreenConnect is another candidate, particularly if you need users to join support sessions. Test the Linux shell workflow before committing, though. Remote screen control and useful terminal access on a headless server are not necessarily the same thing.
Also check the current MFA options, contract terms and renewal costs for the plan you are considering. Those details matter as much as the demo when you're moving hundreds of endpoints.
mostly_crochet:
For Macs, include unattended access and permission changes after macOS updates in the trial. Screen recording permissions can still require user action even when an MDM is involved.
If you decide to keep something self-hosted, MeshCentral is an option to investigate behind a reverse proxy or tunnel. RustDesk paired with a private mesh network such as NetBird is another route.
Neither removes the responsibility to patch and secure your own infrastructure. The mesh approach may also mean deploying and managing an additional client across the fleet, so weigh that work against the control you gain.
~safely!out+of_range:
Check compatibility before putting any existing remote support server behind a tunnel or reverse proxy. Not every product supports that setup.
NinjaOne or Tactical RMM could cover more than remote support, including management tasks you might eventually want. The tradeoff is buying and operating a broader tool than you asked for. Check endpoint pricing and whether the Linux terminal features actually fit before spending much time on either.
Reducing public exposure is a good reason to consider hosted access, but it doesn't make the remote access account risk disappear. Look closely at MFA, technician permissions and how quickly you can disable access during an incident. Test those controls alongside the connection features.
Answers are reviewed before publication.
+loosely~speaking!yes:
A separate tool for the Linux servers could work, though a single console would be preferable. I'll check both against those machines first.