Open dataset, version 2026-08-27

Remote Access Licensing Index

How 12 remote access, remote support and RMM products are licensed, in one structured table: the unit each licence counts, whether the bill follows your operator headcount or your device estate, whether attended and unattended access are both covered, and the one question worth settling before you sign. No prices are asserted, because packaging changes several times a year and a licensing model does not.

Creative Commons Attribution 4.0 International (CC BY 4.0). Compiled by 247connect Marketing Team. Last reviewed 27 August 2026.

Remote access products grouped by what their licence is counted on: operators, devices, both or neitherWHAT DOES THE LICENCE COUNT?OperatorsBill follows headcountAteraLogMeIn / GoToScreenConnectDevicesBill follows estate size247connectNinjaOneBothTwo meters to modelAnyDeskSplashtopTeamViewerZoho AssistNeitherFree or OS-includedChrome Remote DesktopMicrosoft RDPRustDesk

What the data shows

12

Products classified

3

Billed by operator headcount

2

Billed by device estate

4

Billed on both meters

How many products in the licensing index cover attended sessions, unattended access, or bothACCESS MODEL COVERAGE (12 PRODUCTS)Attended and unattended9 of 12Attended sessions only0 of 12Unattended access only3 of 12

The single most useful finding is that the market splits cleanly on what the meter counts. Products aimed at helpdesks tend to count operators, so the bill grows every time you hire. Products aimed at managing an estate count devices, so the bill grows every time you deploy. A handful count both, which is where renewal surprises live: headcount and estate size rarely grow at the same rate, and a quote modelled on one axis quietly breaks when the other moves.

9 of 12 products document both attended sessions and unattended access, but documenting a capability is not the same as including it in the edition you are quoted. That distinction is why every row carries an evaluation question rather than a verdict.

The index

One row per product, sorted alphabetically. Follow the reference link for the full write-up, including how each model behaves as a team grows.

Remote access licensing index: product, category, licensing meter, billing axis and access model coverage
ProductCategoryLicensing meterBill followsAttendedUnattendedReference
247connectRemote desktop and remote support softwareFixed subscription with unlimited operatorsDevicesYesYesFull write-up
AnyDeskRemote access and remote support toolNamed operator licences with session and device tiersBothYesYesFull write-up
AteraRMM platformPer technician, with unlimited devicesOperatorsNoYesFull write-up
Chrome Remote DesktopFree browser-based remote accessFree, tied to a Google accountNeitherYesYesFull write-up
LogMeIn / GoToRemote access and IT support suitePer-technician subscriptions with bundled modulesOperatorsYesYesFull write-up
Microsoft RDPBuilt into the operating systemIncluded with Windows licensingNeitherNoYesFull write-up
NinjaOneRMM platformPer managed endpointDevicesNoYesFull write-up
RustDeskOpen-source remote accessFree software, with optional paid self-hosted server licensingNeitherYesYesFull write-up
ScreenConnectRemote support tool with self-hosting optionsConcurrent technician licencesOperatorsYesYesFull write-up
SplashtopRemote access and remote support product familyPer-product-line subscriptions, metered by user or by deviceBothYesYesFull write-up
TeamViewerRemote support and remote access suiteNamed operator licences with concurrency limitsBothYesYesFull write-up
Zoho AssistRemote support toolPer technician, with separate unattended device packsBothYesYesFull write-up

Methodology

  • Every row is classified from the vendor's own public documentation and pricing pages, not from third-party summaries or resale listings.
  • No prices, tiers, seat counts or discount levels are recorded. Packaging in this market changes several times a year, so any number published here would be stale before it was useful. The licensing model is the durable part.
  • The scales_with column is derived mechanically from the wording of the licensing meter, so the classification cannot drift away from the description it comes from.
  • Attended and unattended coverage records whether the vendor documents the capability at all, not whether it is included in every edition. Edition gating is a question for evaluation, which is what key_evaluation_question is for.
  • 247connect is included as a row on identical terms, and is published by 247connect. Read the dataset knowing who compiled it.
  • Reviewed and re-checked on 2026-08-27. Corrections are welcome and applied on the next review.

Fields and citation

id
Stable row identifier.
product
Product name as the vendor styles it.
category
What kind of product it is.
licensing_meter
The unit the licence is counted on.
scales_with
Which axis the bill grows along: Operators, Devices, Both or Neither.
attended_access
One-time sessions with a person present.
unattended_access
Access to an enrolled device with nobody present.
platform_coverage
Platforms the vendor documents.
best_for
The team shape the model tends to suit.
key_evaluation_question
The thing to settle before signing.
reference_url
Full write-up on this site.

Cite as

Remote Access Licensing Index (2026-08-27), 247connect Knowledge Hub, https://rmm247connect.app/data/remote-access-licensing-index

Questions about the dataset

Why does the dataset contain no prices?

Because a published price would be wrong within months. Packaging, tier names and bundled modules in this market change several times a year, and vendors quote differently by region and volume. What stays stable is the licensing model: the unit being counted, and whether that unit grows with your headcount or with your device estate. That is also the part that decides your renewal, so it is the part worth recording.

How is the scales_with column decided?

It is derived from the wording of each product's licensing meter rather than typed by hand, so the classification cannot drift away from the description it comes from. Operators means the bill follows technician or user count, Devices means it follows the size of the estate, Both means there are two meters to model, and Neither covers free and operating-system-included options.

Can I reuse the data?

Yes. The dataset is published under Creative Commons Attribution 4.0 International (CC BY 4.0), so you may republish, chart or build on it in commercial work provided you attribute 247connect Knowledge Hub and link to this page. Machine-readable copies are available as CSV and JSON at stable URLs with permissive CORS headers, so they can be fetched directly from a notebook or a spreadsheet.

Is the dataset biased towards 247connect?

247connect publishes it, and 247connect appears as a row on identical terms with the same columns and the same kind of evaluation question against it. Nothing in the dataset claims a rival is worse, and no competitor prices or feature lists are asserted. Read it as a structured starting point for your own evaluation, and check every row against the vendor's current documentation before you sign anything.

How often is it reviewed?

The whole index is re-checked against vendor documentation on a rolling basis; the current version is 2026-08-27, last reviewed on 27 August 2026. Version identifiers are dates, so you can cite a specific state of the data.

Where 247connect sits in the index

247connect is the fixed-subscription row: unlimited operators, five concurrent connections per user, and a bill that follows the device estate rather than your headcount. That is the whole pitch, and it is the reason teams that hire helpdesk staff through the year tend to prefer it. Test it against your own numbers on a 14-day trial with two on-demand licences and ten managed devices, no card required.