TSplus Remote Support
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by TSplus · tsplus.net
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
TSplus Remote Support at a glance
- Vendor
- TSplus
- Headquarters
- Not stated on the vendor’s pages as of 6 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 6 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 6 Nov 2026
- Panel verdict
- The AI panel rates TSplus Remote Support 2.5/5, the mean of 6 judges. TSplus Remote Support is a remote desktop and support tool from a vendor that presents itself as a privately held company with headquarters in France. how scores are made
- As of
- Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
TSplus Remote Support is a remote desktop and support tool from a vendor that presents itself as a privately held company with headquarters in France. The bench finds it strongest at remote control, where scores sit at 6: a no-install executable joined by a numeric ID and password, with chat, file transfer, multi-monitor switching and several agents in one session. Security and reliability also scores 6, resting on a self-hosted option documented in engineering detail — relay and centralized API as Docker containers on Ubuntu 24.04 LTS, with all session traffic passing exclusively through the customer's relay. Administration and API is its weakest criterion, at 4 to 5, with no public information on single sign-on, directory sync, a REST API or multi-tenant separation. The judges genuinely split on sovereignty, from 4 to 7: the MSP technician's 7 rests on self-hosting the relay, API and MySQL database on one's own servers; the skeptic's and IT support lead's 4s point to terms naming no legal entity and a worldwide cloud relay network with no stated locations, subprocessors or data processing agreement.
Speaks for it
- Attended sessions start from a no-install executable joined by a numeric ID and password, with chat, file transfer, clipboard synchronization, multi-monitor switching and several agents in one session.
- Self-hosting is documented in engineering detail — relay and centralized API as Docker containers on Ubuntu 24.04 LTS, all session traffic passing exclusively through the customer's relay, data in a MySQL database.
- Licensing counts concurrent connections with unlimited users and unlimited devices, quoted as "5€ / month / concurrent connection" and "300€ billed yearly for 5 concurrent connections".
- Webhooks are signed with HMAC-SHA256, retried on a published schedule with idempotency and test events, covering sessions, participants, file transfers and unattended devices.
- The Freshdesk integration auto-links sessions to open tickets and writes the chat log, downloaded files and remote system information back as a private note.
Held against it
- We found no public information on single sign-on, directory sync, a REST API over users, devices and sessions, or multi-tenant separation — administration and API scores run 4 to 5.
- We found no public information on deployment by MSI, group policy or MDM, on access at the login screen after a reboot, or on Linux agents, leaving command-line activation the only scripted route described.
- We found no public information on session queues or routing to technician groups, and Freshdesk is the only helpdesk integration documented.
- The captured pages give different figures for the entry price — "5€ / month / concurrent connection", "$14.50/month for one user", "18€ /month", and one-time editions at 170€ and 280€ per server — and we found no public information on renewal prices, minimum term, VAT treatment or the price of the self-hosted edition.
- The terms and privacy policy name no legal entity, and we found no public information on cloud relay locations, subprocessors or a published data processing agreement.
Best for
- You run an internal support desk and want a branded client on your own domain, session comments and CSV-exportable reports naming technician, machine and duration.
- You must keep remote sessions on infrastructure you control — the documented self-hosting runs the relay, centralized API and MySQL database on your own Ubuntu server.
- You have many occasional agents and few simultaneous sessions — unlimited users and devices under the concurrent-connection licence fit that shape.
- You already use Freshdesk and want support sessions auto-linked to open tickets with the chat log written back as a private note.
Avoid if
- You plan to enrol hundreds of endpoints — command-line activation is the only scripted route described, and we found no public information on deployment by MSI, group policy or MDM.
- Your team depends on single sign-on and directory sync — the administration console describes manually added members and teams, and we found no public information on SSO or SCIM.
- You need the default cloud service with documented data locations — the pages describe a worldwide relay network with nearest-server routing, and we found no public information on its locations, subprocessors or a data processing agreement.
- You must fix your second-year cost before buying — the captured pages give different figures for the entry price, and we found no public information on renewal prices, minimum term or VAT treatment.
The scores
| Criterion | Panel median |
|---|---|
| Remote control & attended support sessions | 3 of 5 |
| Unattended access & device deployment | 3 of 5 |
| Support desk workflow, branding & reporting | 3 of 5 |
| Administration, identity & API | 2 of 5 |
| Session security, audit & reliability | 3 of 5 |
| European sovereignty | 2.5 of 5 |
| Pricing transparency | 2.5 of 5 |
Remote control & attended support sessions
Show reasoningHide reasoning
How this is scored
What a technician can do in a session with a user who is present: starting a session from a code, link or small support client without admin rights, viewing and controlling the screen with good image quality at low bandwidth, multi-monitor switching, file transfer, clipboard, chat and voice, remote reboot with automatic reconnect, running as administrator and crossing UAC or elevation prompts, session handover to a colleague, whiteboard or annotation, screen sharing in the other direction, and which operating systems can be supported (Windows, macOS, Linux, iOS and Android, including control rather than only viewing of mobile devices).
0 — No remote control of another device; a meeting or chat tool with screen sharing only.
3 — Screen viewing and control of Windows or macOS with a session code; file transfer, reboot and reconnect, elevation and mobile support are basic or not described.
5 — Attended sessions by code or link with a support client that needs no installation, Windows, macOS and Linux supported, multi-monitor, file transfer, chat, clipboard sync, reboot and reconnect, running with admin rights, and viewing or controlling Android or iOS devices described.
8 — Elevation across UAC documented, session handover and invitation of a second technician, annotation and voice, control of Android devices from named makers and iOS screen sharing, performance at low bandwidth and high resolution documented, and browser-based technician and user sides.
10 — A session that handles everything a help desk meets: every major platform including headless Linux, mobile and rugged devices, every session feature documented per platform with its limits, accessibility of the technician console, and quality and latency figures published.
The IT Support Lead
A no-install executable joined by numeric ID and password, with documented screen control, chat, clipboard sync, file transfer, multi-monitor switching, blocked user inputs and multiple agents in one session — and the elevation guide is genuinely useful for us, with three documented routes across UAC prompts provided the remote client runs as administrator. The pages cover Windows, macOS and Android plus an iOS technician app, but I found no public information on Linux devices, voice, annotation, or letting a user join from a simple link. 2 5 9 10
The MSP Technician
Attended sessions run from a small no-install executable with an ID and password, with file transfer, chat, clipboard sync, multi-monitor and blocked user input included, and UAC capture documented down to the "restart as Administrator" button. The client side covers Windows, macOS and Android, and a colleague can drive a machine from an iOS tablet with two touch modes, monitor switching and shortcuts like Ctrl+Alt+Del. We found no public information on Linux support, voice, annotation or formal session handover, so the feature set sits a notch below the top. 2 5 9 10 18
The Software Support Lead
The no-install support client is exactly what my team needs: end-users download a small executable with no installation or reboot and an "admin-free setup", then share a numeric ID and password. Multi-monitor, file transfer, chat, clipboard synchronization, several agents in one session and documented options for capturing UAC screens after an administrator restart are all there, and technicians can drive a session from an iOS or Android console. We found no public information on Linux endpoints, voice or annotation, and a remote reboot with automatic reconnect is not described. 2 5 9 10 18
The Small Office Owner
The core attended flow is documented: the end user runs a small executable with no installation and shares a numeric ID, the agent gets mouse and keyboard control of Windows or macOS, and multi-monitor switching, chat, file transfer, clipboard synchronisation and blocking of the user's inputs are all listed. UAC screens can be captured when the client runs as administrator, several agents can join one session, and an iOS app with two touch modes and keyboard shortcuts lets me drive an office PC from a tablet. I found no public information on Linux endpoints, voice, or annotation. 2 5 9 10 18
The Information Security Officer
The attended flow is well documented: a no-install executable joined by ID and password, chat, file transfer, clipboard sync, multi-monitor switching, and documented handling of UAC prompts when the remote client runs as Administrator, with iOS and Android apps letting a technician drive a session from a tablet. We found no public information on Linux endpoints, reboot with automatic reconnect, annotation or voice, so I cannot place it higher. 2 5 9 10 18
The Skeptic
Sessions start from a no-install executable and a numeric ID and password, with chat, file transfer, clipboard sync and multi-monitor support included; UAC capture is documented together with its condition — the remote client must run as Administrator — and several agents can join one session. Windows, macOS and Android are the documented platforms, with an iOS console offering touch modes, shortcut keys and monitor switching. We found no public information on Linux endpoints, reboot-and-reconnect, annotation, voice, or performance at low bandwidth. 2 5 9 10 18
Unattended access & device deployment
Show reasoningHide reasoning
How this is scored
How machines are reached when nobody sits at them: unattended agents for workstations and servers, mass deployment through MSI packages, group policy, Intune or other management tools, device lists and groups with search, tagging and an address book, wake-on-LAN, access to the login screen and after reboot, access to headless or terminal-only machines, remote command line and file manager without taking over the screen, connecting through proxies and restrictive firewalls, and a desktop or browser client for the person connecting, including remote work access to one's own office PC.
0 — No unattended access; every session needs a person at the remote device to accept it.
3 — An agent can be installed for unattended access with a password; deployment, groups, wake-on-LAN and access to servers are basic or not described.
5 — Unattended agents for Windows, macOS and Linux, deployment by MSI or a custom installer, device groups and an address book shared within the team, wake-on-LAN, access at the login screen and after reboot, and connection through proxies described.
8 — Mass deployment through group policy or an MDM documented with assignment to groups, background tools (command line, file manager, processes, services) without disturbing the user, access to headless servers, tagging and search over large device lists, and access for remote workers to their own office PC with its own policy.
10 — A fleet of thousands reachable and organised: zero-touch enrolment with naming and grouping rules, every background tool documented per platform, connection quality and device status visible across the fleet, and agent updates managed centrally with their rollout documented.
The IT Support Lead
Attended and unattended modes, pre-authorized machines with unlimited managed devices, wake-on-LAN and remote power-on, headless sessions, a remote command shell without taking the screen, and folders, teams and search over the machine list are all documented. For my estate, though, I found no public information on mass deployment through Intune, group policy or MSI — activation by command line is the only scripted route described — nor on access at the login screen or a background file manager. 2 5 11 12 15
The MSP Technician
Unattended access is real and scriptable: a pre-authorized machine list reachable around the clock, activation by command line, wake-on-LAN with remote power-on of disconnected PCs, and a remote command prompt without taking over the screen. Machines sit in folders with inherited permissions shared per team, with search and filtering for larger fleets, and headless sessions are named. We found no public information on MSI or group-policy mass deployment, Linux agents, or a background file manager, which is what I would want for rolling out to hundreds of endpoints. 2 5 11 12 15
The Software Support Lead
Unattended access works from a pre-authorized machine list with unlimited managed devices, wake-on-LAN and remote power-on for disconnected PCs, plus a remote command shell and mid-session switching to command-line mode for scripting without a full takeover. Computers sit in a folder tree with team permissions, inheritance, search and drag-and-drop under a centralized administration console, and unattended activation can be scripted from the command line. We found no public information on mass deployment by MSI, group policy or MDM, on reaching the login screen or reconnecting after a reboot, or on Linux servers. 2 5 11 12 15
The Small Office Owner
Unattended machines are reachable at any time from a pre-authorized list, with a remote command shell that skips the screen takeover, wake-on-LAN and remote power-on, and device grouping with filtering and search; the administration console organises computers into folders with inherited permissions shared by team. Enabling unattended mode is scriptable from the command line, which suffices for my eleven office PCs even without a packaging story. I found no public information on MSI or group-policy deployment, a background file manager, or reaching the login screen after a reboot. 2 5 11 12 15
The Information Security Officer
Unattended mode is real and organised: pre-authorized machines reachable 24/7, wake-on-LAN with remote power-on, a remote command shell without a GUI session, and an administration console with folders, teams and inherited permissions over the fleet. We found no public information on mass deployment through group policy or an MDM, access at the login screen after reboot, or agents for Linux, which is what I would need for a server estate. 2 5 11 12 15
The Skeptic
Unattended access is pre-authorized with unlimited managed devices under the concurrent-session licence, plus Wake-on-LAN, remote power-on, headless sessions, a remote command shell with mid-session switching, and command-line activation of unattended mode. Computers sit in folders with inherited permissions, filtering and search. We found no public information on deployment by MSI, group policy or MDM, on access at the login screen or after reboot, or on agents for Linux — so how four hundred machines get enrolled is left undescribed. 2 5 11 12 15
Support desk workflow, branding & reporting
Show reasoningHide reasoning
How this is scored
How a support team runs remote sessions as a service: session queues and routing to technicians or groups, a support request button or chat on the vendor's website, a support client and portal in the customer's own branding with its own domain, post-session surveys, session notes and summaries, integrations with helpdesk and ITSM tools (ServiceNow, Jira Service Management, Zendesk, Freshservice, HubSpot) that start sessions from a ticket and write the session back, reports per technician and customer, session duration for billing, and any AI assistance in sessions with its provider named.
0 — No way to organise sessions across technicians; each session is a one-off between two people.
3 — A session history and one or two integrations; queues, branding, surveys and reports are basic or not described.
5 — A custom-branded support client or portal, session history and reports per technician, session notes, one-click sessions from common helpdesk tools, and a way to queue or assign incoming support requests.
8 — Queues with routing to technician groups, a support button or chat for the vendor's own website, the support client under the customer's domain, post-session surveys, session data written back to the ticket, exportable reports for billing, and AI assistance with its model provider named.
10 — A support operation that needs no separate session tool: routing by skill and language, full white-label of every client and email, service-level reporting per customer, every integration documented with the data it writes, and AI features documented with data handling and an opt-out.
The IT Support Lead
A branded client downloadable from our own domain, session comments, CSV-exportable reports with technician, start and end times and machine ID, and a Freshdesk integration that links a session to the open ticket and writes the chat log and system information back as a private note cover most of a working desk. I found no public information on queues or routing to technician groups, post-session surveys or AI assistance, and Freshdesk is the one helpdesk integration documented in detail. 2 13 14 16
The MSP Technician
The branded support client can even be downloaded from our own domain, and sessions are logged with comments and CSV-exportable reports showing who, which machine and how long — enough for billing. The Freshdesk integration auto-links sessions to open tickets and writes the chat log, downloaded files and system information back as a private note. We found no public information on session queues, routing or post-session surveys, and Freshdesk is the only helpdesk integration documented, so this is not yet a full service-desk operation on its own. 2 5 13 14
The Software Support Lead
This covers most of my wishlist: a branded client with our logo and colors served from our own domain, session comments, and per-session logs naming the connected agents with start, end and total duration, exportable to CSV so I can see how long a fix takes. The Freshdesk integration auto-links a session to an open ticket and writes a private note back with the chat log, transferred files and system information, and webhooks can push the same data, including the full chat transcript, into any ticketing or SIEM system. We found no public information on queues or routing to technician groups, a support button for our website, or post-session surveys, and Freshdesk is the only helpdesk named. 2 5 13 14 16 18
The Small Office Owner
Our logo on the support client, the client download hosted on our own domain, per-session comments, and reports with start, end, duration, machine and connected users exportable to CSV cover the bookkeeping side of a session. The Freshdesk integration automatically links sessions to tickets and writes the chat log and remote system information back as a private note. I found no public information on queues or routing of incoming requests, post-session surveys, or AI assistance during sessions. 2 13 14 16 18
The Information Security Officer
The service layer exists: a branded support client served from the customer's own domain, session comments, CSV-exportable reports with technician, machine, start, end and duration, and a Freshdesk integration that writes the chat log and system information back to the ticket. We found no public information on session queues or routing to technician groups, and Freshdesk is the only helpdesk integration documented. 2 5 13 14
The Skeptic
The support client is branded and can be hosted on the customer's own domain; sessions carry comments, and reporting lists the technician, start and end times, machine and duration with CSV export, plus recording as video files. Freshdesk sessions are linked to tickets automatically and the chat log, downloaded files and system information are written back as a private note, with signed webhooks for session events. We found no public information on queues or routing to technicians, post-session surveys, or AI assistance in sessions. 2 5 13 14 16 18
Administration, identity & API
Show reasoningHide reasoning
How this is scored
How the tool fits the company or the MSP: user and technician management with roles and granular permissions per device group, single sign-on (SAML or OpenID Connect) with Entra ID or Google, SCIM or directory sync, enforced two-factor authentication, central policies for agents (who may connect, when, with which features), multi-tenant customer separation for MSPs, a documented REST API and webhooks for users, devices and sessions, integrations with RMM, PSA and endpoint management tools, and licence management across seats, endpoints and concurrent sessions.
0 — No administration beyond a single login per technician.
3 — A web console to add technicians and see devices; roles, SSO, policies and the API are basic or not described.
5 — Technician roles and permissions per device group, two-factor authentication that can be enforced, single sign-on, central policies for agent settings, a documented API, and an integration with at least one RMM, PSA or endpoint management tool.
8 — SAML or OIDC single sign-on with SCIM or directory sync, conditional permissions by group and time, policies pushed to agents with lock-down of local settings, separate customer tenants for MSPs, an API covering users, devices, sessions and reports with webhooks, and integrations with named RMM, PSA and MDM products.
10 — Administration that scales across many companies: every setting reachable by API with parity stated, delegated administration per tenant, SSO and SCIM enforced across tenants, and the audit trail of every administrative change exportable to a SIEM.
The IT Support Lead
The administration console gives me users and teams, folder permissions with inheritance, centralized machine management, restriction of computers to the same subscription and two-factor authentication, and the webhooks are properly engineered with HMAC-SHA256 signatures, retries and a test event. But I found no public information on single sign-on with Entra ID or SAML, SCIM or directory sync, a REST API over users, devices and sessions, or multi-tenant separation for service providers. 5 15 16
The MSP Technician
The Administration Console gives me what matters most for keeping clients apart: folders of computers with permissions inherited by sub-folders, shared with specific teams, plus member and team management and a two-factor option. Webhooks are unusually well documented — signed with HMAC-SHA256, retried on a published schedule, covering sessions, participants, unattended computers and file transfers, aimed at ticketing, CRM and SIEM. We found no public information on single sign-on, directory sync, a documented REST API, or integrations with named RMM or PSA tools, which is exactly where my toolchain would have to plug in. 3 15 16
The Software Support Lead
The web Administration Console adds members, assigns them to teams, shares folder permissions over the computer tree with inheritance, and can restrict computer access to subscription users, with two-factor authentication available; webhooks are documented in real depth, HMAC-SHA256-signed with retries and an idempotency header for session, participant, file-transfer and unattended events. We found no public information on single sign-on, SCIM or directory sync, a REST API covering users and devices, multi-tenant separation for MSPs, or integrations with named RMM or endpoint management products. 3 15 16
The Small Office Owner
The web administration console handles members, teams and administrator promotion, shares computer folders with permission inheritance, and can restrict connections to members of the subscription, with two-factor authentication offered. The webhook documentation is thorough — HMAC-SHA256-signed deliveries with a retry schedule and events for sessions, participants and unattended devices — but I found no public information on single sign-on, directory sync, a REST API, or per-customer separation for managed-service use. 3 13 15 16
The Information Security Officer
There is a real administration console — members, teams, folder-level permissions with inheritance, and computer access restricted to the subscription — plus well-documented webhooks signed with HMAC-SHA256 that I could feed to a SIEM. We found no public information on single sign-on, directory sync, central agent policies or a REST API, and the two-factor authentication described is not shown as an enforceable requirement. 13 15 16
The Skeptic
An administration console adds members, forms teams, and shares folders of computers with inherited permissions, and two-factor authentication is described. The webhooks are properly engineered — HMAC-SHA256 signed, with retries, idempotency headers and a test event — but they only report events; we found no public information on single sign-on, directory sync, a REST API over users, devices and sessions, central agent policies, or customer tenants for MSPs. Every technician looks like a manually created account. 3 15 16
Session security, audit & reliability
Show reasoningHide reasoning
How this is scored
Whether remote access is a door only the right people can open: end-to-end or transport encryption with the protocol and key length named, two-factor authentication, the user's consent prompt and the option to block input or blank the screen, device and IP allow-lists, trusted-device approval, brute-force protection, session recording and an audit log of who connected to what and when, protection against support scams and misuse of free accounts, a published vulnerability disclosure process and security advisories, independent certifications (ISO 27001, SOC 2), the location and redundancy of relay servers, a public status page, an SLA, and an on-premise or self-hosted server for organisations that keep the relay in their own network.
0 — Nothing on encryption, authentication or how sessions are logged.
3 — A claim of encryption and a password per session; two-factor authentication, audit logs, certifications and the status page are basic or not described.
5 — Encryption with the protocol named, two-factor authentication, a consent prompt for attended sessions, session logs with technician, device and time, session recording offered, a public status page, and a security page describing how access is protected.
8 — End-to-end encryption documented, device or IP allow-lists and trusted-device approval, audit logs exportable, recording rules per group, measures against support scams described, ISO 27001 or SOC 2 with its scope, a vulnerability disclosure policy with published advisories, an SLA, and an on-premise or self-hosted relay option.
10 — Security evidenced, not claimed: independent penetration tests or audit reports available, security advisories with fixed versions and timelines, a self-hosted deployment with no dependency on the vendor's cloud, and failover of the relay infrastructure documented.
The IT Support Lead
End-to-end TLS encryption, ID and password access controls with the user allowing the connection, two-factor authentication, session logs with technician, machine and times, session recording to video files, and a documented self-hosted relay and API on our own Docker hosts add up to a workable picture for us. I found no public information on ISO 27001 or SOC 2 certifications, a vulnerability disclosure policy, a public status page, an SLA, or export of an audit trail beyond the session report. 2 14 15 17 18
The MSP Technician
Sessions are protected by what the vendor calls end-to-end TLS encryption, the end user must allow the connection, user input can be blocked, two-factor is available, and session logs and video recording exist. For my law-firm and dental clients the self-hosted option counts: the relay and centralized API run as Docker containers on our own Ubuntu server with a MySQL database and our own certificate, so session traffic stays in our network. We found no public information on ISO 27001 or SOC 2 certification, a vulnerability disclosure policy, an SLA, or a public status page. 2 14 15 17 18
The Software Support Lead
Attended sessions need the end-user's approval, inputs can be blocked, sessions are encrypted with TLS, recorded as video files and logged with technician, machine and times exportable to CSV — enough for me to answer who touched what. The self-hosted option is the serious part: a centralized API and relay as Docker containers on Ubuntu, with all communication passing exclusively through the customer's own relay and data in its MySQL database. We found no public information on ISO 27001 or SOC 2, a vulnerability disclosure policy, a public status page, an SLA, or device and IP allow-lists. 2 5 14 17 18
The Small Office Owner
All sessions are stated to use end-to-end TLS, two-factor authentication exists, the user must allow the connection, inputs can be blocked, and sessions are logged with user, machine and times, plus recording to video files. Being able to run the relay and the central API myself on Ubuntu with my own certificate is the kind of control that reassures an accounting office. I found no public information on a public status page, an SLA, ISO or SOC certification, or a vulnerability disclosure process. 2 5 14 15 17 18
The Information Security Officer
The strongest area for a critical-infrastructure buyer: a self-hosted deployment documented in engineering detail — relay and API as Docker containers on Ubuntu, sized per session, with all session traffic passing exclusively through our own relay — alongside two-factor authentication, session recording to video, and session logs with technician, machine and timestamps exportable to CSV. Sessions are described as end-to-end TLS encrypted while the deployment documentation states all communication transits the relay, and we found no public information on independent certifications, a vulnerability disclosure process with published advisories, an SLA or a status page, which keeps my score moderate. 2 14 15 17 18
The Skeptic
TLS is named for session encryption, attended sessions begin with the user allowing the connection, inputs can be blocked, and sessions are recorded as video and logged with technician, machine and timestamps exportable to CSV or pushable to a SIEM by webhook. The self-hosted option is documented in useful detail — the customer runs the API and relay on Ubuntu with their own certificate, and all session traffic runs exclusively through that relay. But we found no public information on ISO or SOC certifications, a vulnerability disclosure policy, a status page, an SLA, device or IP allow-lists for sessions, and the encryption claim stops at naming TLS. 2 5 14 15 16 17 18
European sovereignty
panel opinion
panel disagrees
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where account data, device lists, session logs, recordings, chat transcripts and file transfers are stored and processed, where the relay and brokering servers that carry session traffic stand, and who the subprocessors are (hosting, relay networks, email delivery, support and payment tools, AI models). Independently sourced by the sovereignty pipeline. A self-hosted or on-premise server the customer runs on its own European infrastructure counts as the customer's chain, whatever the vendor's seat, as long as it does not call home for more than licensing.
0 — Non-EU vendor and contracting entity, hosting and relay locations unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting and relay locations are unstated or non-EU and the subprocessors are not listed.
5 — EU hosting or EU relay servers available and an EU contracting entity or EU representative, but parts of the chain (session brokering, support, payment, AI) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications stated — or a self-hosted server documented that keeps sessions, logs and recordings on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting, relays and every subprocessor including any AI model, or a self-hosted edition with no call home beyond licensing, data export and deletion documented, and certifications published with their scope rather than implied.
The IT Support Lead
TSplus presents itself as a privately held French company under a Made-in-France banner and declares itself the GDPR controller with a Data Protection Officer contact, and the self-hosted option — our own API, relay and MySQL database in Docker — is documented down to RAM and bandwidth per session. But the terms name no legal entity, and I found no public information on where the cloud service and its worldwide relay network store data, on subprocessors, or on a published data processing agreement. 2 6 8 17
The MSP Technician
TSplus presents itself as a privately held company with headquarters in France and declares itself the GDPR controller with a contactable Data Protection Officer. Decisive for us is the documented self-hosting: relay and centralized API on our own servers, all computer, user and session information in our own MySQL database, and traffic flowing exclusively through our relay. For the cloud offering we found no public information on where hosting or relay servers stand or which subprocessors are used, and we found no published data processing agreement. 2 6 8 17
The Software Support Lead
The vendor presents itself as a French company headquartered in France, declares itself the Data Controller under GDPR with a contactable Data Protection Officer, and the documented self-hosted edition would keep the relay, sessions and database on infrastructure we run ourselves. The default cloud, though, routes through a "worldwide network of relay servers" with no stated locations, subprocessors are not listed, the terms name no legal entity, and the company describes itself as an "international cluster of companies operating all over the World". We found no public information on a data processing agreement or on EU locations for the cloud relay chain. 2 6 8 12 17
The Small Office Owner
The vendor states it is privately held with headquarters in France and declares itself the GDPR controller with a contactable Data Protection Officer, and self-hosting the relay and API on my own Ubuntu server keeps session traffic on infrastructure I choose. Against that, the default cloud relay is described only as a worldwide network with no locations given, no legal entity is named in the terms, and I found no public information on subprocessors or a published data processing agreement. 2 6 8 17
The Information Security Officer
The vendor presents itself as privately held with headquarters in France, and the self-hosted option lets a utility keep the relay, the MySQL store and all session data on its own European servers. Against that, the terms and privacy policy name no legal entity, the default cloud relays form a worldwide network with no stated locations, and we found no public information on subprocessors, a data processing agreement or data residency for the cloud service. 2 6 8 17
The Skeptic
The vendor is privately held with headquarters in France, declares itself the GDPR controller with a Data Protection Officer contact, and offers a documented self-hosted deployment that keeps the relay, API and MySQL data on the customer's own servers. But the terms and privacy policy name no legal entity, the cloud relays are described only as a worldwide network with nearest-server routing, and we found no public information on hosting locations, subprocessors, a data processing agreement, or what the self-hosted edition calls home for. 2 6 8 17
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per plan and what the licence counts (technicians or seats, concurrent sessions, managed or unattended endpoints), what extra technicians, endpoints and sessions cost, which features (mobile device support, branding, SSO, session recording, integrations, on-premise server) cost extra, monthly versus annual billing, renewal prices, the terms for commercial use of a free version, minimum term, and VAT.
0 — No public prices at all; every customer is a sales call or a partner quote.
3 — A starting price exists, but what it counts and what extra technicians, endpoints and add-ons cost is unclear.
5 — Plans are public with their price and what the licence counts, but at least one commonly needed piece (extra technicians, more endpoints, mobile support, SSO, on-premise) is unpriced or "on request".
8 — Every plan priced publicly with its scaling rule for technicians, sessions and endpoints, add-ons priced, monthly and annual prices shown, renewal terms, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given number of technicians, concurrent sessions and endpoints, with every add-on, the on-premise licence and support fees, renewal increases and cancellation terms published.
The IT Support Lead
The concurrent-connection model is clear and computable — "5€ / month / concurrent connection", "300€ billed yearly for 5 concurrent connections", unlimited users and unattended devices, with the feature list marked included and a downloadable PDF price list. The captured pages give different figures for the entry price — "18€ /month" on one page and "$14.50/month for one user" on another — and I found no public information on VAT treatment, minimum term, renewal increases or the price of the self-hosted edition. 2 4 5 17 18
The MSP Technician
The pricing page is clear about what a licence counts — concurrent connections with unlimited users and unlimited devices, quoted as "5€ / month / concurrent connection" and "300€ billed yearly for 5 concurrent connections" — and it lists what is included, from wake-on-LAN to custom branding. The captured pages give different figures elsewhere: "$14.50/month for one user" in a product announcement and one-time server editions at 170€ and 280€ on another page. We found no public information on renewal prices, minimum term, VAT treatment, or what the self-hosted edition costs. 2 4 5 17 18
The Software Support Lead
The pricing page is unusually clear on what a licence counts: "5€ / month / concurrent connection", "300€ billed yearly for 5 concurrent connections", with unlimited agents and devices up to that limit, and a downloadable PDF price list. The captured pages give different figures for the entry point — 5€ per month per concurrent connection, "$14.50/month for one user", and a 170€ starting figure elsewhere. We found no public information on renewal prices, minimum term, VAT treatment, or what the self-hosted edition costs, for which no trial is offered. 2 4 5 17 18
The Small Office Owner
The licence counting is refreshingly plain: '5€ / month / concurrent connection' and '300€ billed yearly for 5 concurrent connections', with unlimited users and unlimited devices up to that limit and a fifteen-day trial without a credit card. The captured pages give different figures for the entry price — the five-euro figure, '$14.50/month for one user', and one-time editions at 170€ and 280€ including one year of updates — and I found no public information on what the second year costs, on VAT, or on the price of the self-hosted edition. 2 4 5 17 18
The Information Security Officer
The licence model is unusually computable — concurrent connections with unlimited users and devices, shown as "5€ / month / concurrent connection" and "300€ billed yearly for 5 concurrent connections", with a downloadable PDF price list. The captured pages give different figures for the entry price ("170€ (or 18€ /month)" on one page, "$14.50/month for one user" on another), and we found no public information on renewal terms, minimum term, VAT or the price of the self-hosted deployment. 2 4 5 17 18
The Skeptic
The pricing page shows what the licence counts — concurrent connections, with unlimited users and devices — at "5€ / month / concurrent connection" and "300€ billed yearly for 5 concurrent connections", with a downloadable price list and a 15-day trial without credit card. But renewal prices, minimum term and VAT treatment are not stated, and the self-hosted edition is unpriced with no trial. The captured pages also give different figures — "170€ (or 18€ /month)", "170€ / server" and "280€ / server" one-time editions, and "$14.50/month for one user" — so the real annual and second-year cost is not computable from these pages alone. 2 4 5 17 18
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about TSplus Remote Support
Is TSplus Remote Support European?
Yes. whats-best.ai classifies TSplus Remote Support as EU-Made.
Where does TSplus Remote Support store data?
Not stated on the vendor’s pages as of 6 Nov 2026.
Does TSplus Remote Support have a free plan?
Not stated on the vendor’s pages as of 6 Nov 2026.
What are the best alternatives to TSplus Remote Support?
As of 18 Nov 2026, the panel rates Splashtop (3.5/5), RustDesk Server Pro (3/5) and TeamViewer Remote (3/5) highest among the other 16 Remote Desktop & Remote Support products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is TeamViewer Remote (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: TSplus Remote Support alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 6 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting options. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 34 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 17 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (18)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage (product page) tsplus.net Checked 6 Nov 2026 Details →
- 2 Features page tsplus.net Checked 6 Nov 2026 Details →
- 3 Documentation docs.tsplus.net Checked 6 Nov 2026 Details →
- 4 Security / trust page (Advanced Security add-on) tsplus.net Checked 6 Nov 2026 Details →
- 5 Pricing page tsplus.net Checked 6 Nov 2026 Details →
- 6 About page tsplus.net Checked 6 Nov 2026 Details →
- 7 Terms of service tsplus.net Checked 6 Nov 2026 Details →
- 8 Privacy policy tsplus.net Checked 6 Nov 2026 Details →
- 9 Remote control & attended support sessions — found from sitemap docs.tsplus.net Checked 6 Nov 2026 Details →
- 10 Remote control & attended support sessions — found from sitemap docs.tsplus.net Checked 6 Nov 2026 Details →
- 11 Unattended access & device deployment — found from sitemap tsplus.net Checked 6 Nov 2026 Details →
- 12 Unattended access & device deployment — found from sitemap tsplus.net Checked 6 Nov 2026 Details →
- 13 Support desk workflow, branding & reporting — found from sitemap docs.tsplus.net Checked 6 Nov 2026 Details →
- 14 Support desk workflow, branding & reporting — found from sitemap docs.tsplus.net Checked 6 Nov 2026 Details →
- 15 Administration, identity & API — found from sitemap docs.tsplus.net Checked 6 Nov 2026 Details →
- 16 Administration, identity & API — found from sitemap docs.tsplus.net Checked 6 Nov 2026 Details →
- 17 Session security, audit & reliability — found from sitemap docs.tsplus.net Checked 6 Nov 2026 Details →
- 18 Session security, audit & reliability — found from sitemap tsplus.net Checked 6 Nov 2026 Details →