Getscreen.me

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Point B Ltd · getscreen.me

Compare with RustDesk Server Pro → Report an error on this page Is this your product? →

Link to this page

Getscreen.me: AI-assisted analysis on whats-best.ai Getscreen.me: AI-assisted analysis on whats-best.ai (dark)

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.

Getscreen.me at a glance

Vendor
Point B Ltd
Headquarters
Incorporated in Cyprus source, captured 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 Getscreen.me 3/5, the mean of 6 judges. Getscreen.me is a remote desktop and remote support tool from Point B Ltd of Cyprus. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

Getscreen.me alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

Getscreen.me is a remote desktop and remote support tool from Point B Ltd of Cyprus. The bench's highest scores landed on unattended access, 7-8: permanent-access agents for Windows, macOS, Linux and Android, mass deployment by MSI or Group Policy, and terminal and file-manager access without taking the screen. Remote control, administration and API, and security and reliability clustered at 6-7, covering browser sessions with file transfer, chat and voice, per-device permissions with SAML single sign-on, a documented HTTP API, encryption named to protocol and cipher, and a status page showing 99.994 percent over ninety days. The weakest area was support workflow, 4-6: branding runs unusually deep — logo, title, subdomain, own domain, the agent's process name — but we found no public information on queues, routing, per-technician reports or sessions written back to tickets. Judges split on sovereignty, 6-8: the security officer credited a self-hosted edition documented to run without internet access; the small office owner weighed Enterprise-only, annual-billing-only, quote-based self-hosting with minimums of 10 technicians or 500 devices, and proxies documented outside the EU. Pricing transparency clustered at 6.

Report an error

Speaks for it

  • Unattended agents cover Windows, macOS, Linux and Android, with bulk deployment by MSI, Group Policy, RMM or MDM and a documented button to mass-remove agents across the fleet.
  • Attended sessions run from a browser with file transfer, chat and voice, multi-monitor switching, and reboot with automatic reconnect including Safe Mode.
  • Permissions reach individual device actions such as terminal mode and wake-on-LAN with group inheritance, alongside SAML 2.0 single sign-on and a documented HTTP API.
  • Encryption is named to protocol and cipher — DTLS/SRTP with AES-128 or AES-256, TLS with AES-GCM or ChaCha20 — with recording off by default and 99.994 percent uptime over ninety days on the public status page.
  • User data is hosted on Hetzner in Germany and Finland, and a self-hosted edition is documented to run without an internet connection.

Report an error

Held against it

  • We found no public information on session queues, routing, per-technician reports for billing, post-session surveys, or sessions written back to tickets.
  • We found no public information on SCIM, webhooks, or separate customer tenants for managed-service providers.
  • We found no public information on ISO 27001 or SOC 2 certification, a vulnerability disclosure policy, an SLA, or export of audit logs.
  • Proxy infrastructure is documented in the United States, India, Israel, Brazil, South Korea and Australia alongside Germany, without a stated safeguard.
  • The self-hosted edition is a custom quote on the Enterprise plan, annual billing only, with minimums of 10 technicians or 500 devices, and we found no public information on VAT treatment, renewal prices or minimum term.

Report an error

Best for

  • You run an internal support desk and need both attended sessions and permanent, unattended access to Windows, macOS, Linux and Android machines.
  • You push agents to a fleet through MSI, Group Policy, RMM or MDM and manage access with device groups that inherit permissions.
  • You need the whole chain on your own infrastructure and can meet the 500-device or 10-technician minimum, since the self-hosted edition is documented to run without internet access.
  • You hand branded invitations and agent files to clients and want your logo, title, subdomain, own domain by CNAME and even the agent's process name throughout.

Report an error

Avoid if

  • You require every hop of the connection chain to stay in the EU, since proxy infrastructure is documented in the United States, India, Israel, Brazil, South Korea and Australia, with user data on Hetzner in Germany and Finland.
  • You want self-hosting at a smaller scale, since it is a custom quote on the Enterprise plan, annual billing only, with minimums of 10 technicians or 500 devices.
  • Your service desk depends on queues, routing and per-technician billing reports, since the documented Jira Service Desk, LiveChat and Chrome extensions send session invites and we found no public information on the rest.
  • You need to control iPhones or iPads, since the listed supported systems are Windows, macOS, Linux and Android, with Android control tested on Google, Samsung, Xiaomi and Huawei.

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

Remote control & attended support sessions

panel disagrees Show 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.

Report an error

The IT Support Lead

A user can join from an email, link, code or a website widget, my technician connects from any browser or the desktop app, and the session carries chat, voice, multi-monitor switching, file transfer, clipboard sync and reboot with automatic reconnect even into Safe Mode — that is my daily bread on the service desk. Administrator privilege elevation is documented but subject to the remote user's approval, and Android control is proven on Google, Samsung, Xiaomi and Huawei devices; we found no public information on iOS support, annotation, or performance figures at low bandwidth. Six: a strong attended toolkit with the top-end items unverifiable. 2 16 17 3

Report an error

The MSP Technician

Attended sessions run from a browser or desktop dashboard with multi-monitor switching, file transfer, chat and voice calls, clipboard sync, reboot with automatic reconnection even into Safe Mode, and elevation on request; joint connections let several technicians work one client, and Android control from Google, Samsung, Xiaomi and Huawei with gestures is documented. I found no public information on iOS support, on-screen annotation, or quality and latency figures at low bandwidth, and the elevation text does not name UAC handling. 1 2 16 17

Report an error

The Software Support Lead

Sessions start by code, link, email or a website widget, the technician side runs in a browser or desktop dashboard, and Windows, macOS, Linux and Android are supported with multi-monitor switching, chat and voice calls, file transfer, clipboard sync, and reboot with automatic reconnect even in Safe Mode. Administrator elevation subject to user approval and multiple operators joining one session are documented, and Android control with gestures is proven on Google, Samsung, Xiaomi and Huawei devices. We found no public information on iOS support, screen annotation, or performance figures at low bandwidth. 1 2 3 16 17

Report an error

The Small Office Owner

For the evenings when a colleague's scanner stops working, the pages document everything I would reach for: sessions by code, link, email or a website widget; chat and voice during the session; file transfer, clipboard and keyboard sync, multi-monitor switching, reboot with automatic reconnect even into Safe Mode, and administrator elevation with the user's approval, with several operators able to join one client. Android control from a browser with gestures is documented and tested on Google, Samsung, Xiaomi and Huawei devices. We found no public information on iOS support, annotation, or published figures for image quality at low bandwidth. 1 2 16 17

Report an error

The Information Security Officer

Attended sessions start from a code, link, email or a website widget, run through a browser-based console, and cover Windows, macOS, Linux and Android with multi-monitor, file transfer, chat and voice, clipboard sync, reboot with automatic reconnect even in Safe Mode, and privilege elevation subject to user approval; several operators can join one session and Android control is documented with named makers. We found no public information on iOS screen sharing, annotation, or performance at low bandwidth; the stated minimum is 5 mbps. 1 2 3 16 17

Report an error

The Skeptic

Sessions start by code, link, email invite or a website widget from a browser or desktop console, with file transfer, chat and voice, clipboard and hotkey sync, multi-monitor, reboot with auto-reconnect including Safe Mode, elevation with user approval, and several technicians in one session — plus Android control tested on named makers with gestures. I found no public information on iOS support, an annotation tool, or performance at low bandwidth and high resolution, so it stops short of the top band. 1 2 16 17

Report an error

Unattended access & device deployment

panel disagrees Show 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.

Report an error

The IT Support Lead

Permanent Access agents run on Windows, macOS, Linux and Android and can be pushed at scale as MSI with register and config parameters, through Group Policy, RMM or MDM — MDM is named generically so I would confirm Intune specifically, but the MSI route is what Intune consumes anyway. Device groups with inheritance, search and filtering, wake-on-LAN, terminal mode and a file manager without taking the screen, RDP into servers and even mass agent removal are all documented. Seven, because tagging and access to headless machines are thin beside that. 3 18 19 4

Report an error

The MSP Technician

Permanent Access agents cover Windows, macOS, Linux and Android, with an MSI carrying registration and configuration parameters, a Group Policy bulk-install guide and RMM or MDM deployment paths; wake-on-LAN, terminal mode and file manager without a screen session, device groups with search and filters, and notifications on device status are all documented. That covers my overnight server access, though I found no public information on zero-touch enrolment with naming and grouping rules. 3 4 10 18 19

Report an error

The Software Support Lead

Permanent Access agents cover desktop and mobile, deployable by MSI with REGISTER and CONFIG parameters, Group Policy, or RMM and MDM tools, with ready-made console commands for Windows, macOS, Linux and Android. The device directory offers search, filters and table view, groups inherit access rights, Wake-on-LAN works with prior configuration, and terminal mode plus a file manager run without taking over the screen. Access for remote workers to their own computers is described; we found no public information on headless server access or tagging for very large fleets. 3 4 10 18 19

Report an error

The Small Office Owner

Permanent-access agents cover Windows, macOS, Linux and Android, with mass deployment by MSI with configurable parameters, Group Policy, RMM or MDM, ready console commands for each platform, wake-on-LAN, device groups with search and filters, and RDP connections to servers. A file manager and a terminal mode that works without taking over the screen are documented, which is exactly what I want for reaching the office PCs at night. We found no public information on headless machines, remote process or service management, or tagging across large device lists. 3 10 18 19

Report an error

The Information Security Officer

Permanent-access agents for desktop and mobile, an MSI with registration and configuration parameters, and bulk deployment through group policy or RMM and MDM systems are documented, with terminal-mode and RDP access to servers without taking the screen, wake-on-LAN, device groups with inheritance, search and filtering, and connection through existing firewall settings. We found no public information on background management of processes and services or on tagging as such. 3 4 10 18 19

Report an error

The Skeptic

Permanent-access agents cover Windows, macOS, Linux and Android, deployed by MSI with registration and configuration parameters, group policy, RMM or MDM, with device groups inheriting permissions, search and filtering, wake-on-lan, terminal mode and file manager without taking over the screen — and, rare to see published, a button to mass-remove agents across the fleet. I found no public information on access to headless machines, tagging, or background management of processes and services. 3 4 18 19

Report an error

Support desk workflow, branding & reporting

panel disagrees Show 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.

Report an error

The IT Support Lead

Invitations and the agent can carry our logo, title, icon and our own CNAME domain, an HTML widget starts a session from our website, and a Jira Service Desk extension sends an invitation right out of the ticket window — the workflow I want, though we found no public information on session data being written back to the ticket. Session recording with comments per session and a connection history exist; we found no public information on queues, routing to technician groups, post-session surveys or per-technician reports. Five: the branding is thorough, the service-desk machinery around it is not. 20 6 16 21

Report an error

The MSP Technician

Branding goes deep — logo, icon, process name, subdomain and own domain via CNAME, a branded invitation page and an embeddable website widget — and sessions carry notes, screenshots and video recording, with a Jira Service Desk extension to invite clients from the ticket window. I found no public information on session queues or routing, post-session surveys, per-technician reports for billing, or session data written back to the ticket, which is what I need for PSA-driven invoicing. 6 10 16 20 21

Report an error

The Software Support Lead

The branded support client is strong for us: agent title, custom icon, process name, own subdomain or CNAME domain, branded invitation pages and Windows and Linux distributives, with the agent configurable to connect without admin rights, a website widget that starts sessions, and a notification when the client is ready. The Jira Service Desk, LiveChat and Chrome extensions send session invites from the ticket or chat window, and sessions carry notes, screenshots and video recording. We found no public information on a queue routing callers to technicians, on session data written back to the ticket, on per-technician reports with fix duration, or on post-session surveys. 3 6 16 20 21

Report an error

The Small Office Owner

Branding runs deep — my logo, a title, a subdomain or my own domain, branded invitation pages and agent files moderated within two business days — and there is an embeddable website widget, connection history, per-session notes and screenshots, plus a Jira Service Desk and a LiveChat extension for sending session invites. But we found no public information on queues or routing of incoming requests, reports per technician, post-session surveys, sessions written back to the ticket, or AI assistance with a named provider. 6 16 20 21

Report an error

The Information Security Officer

Branding is documented in unusual depth — custom title, icon, subdomain and own domain by CNAME, branded invitation pages, a website widget and a branded agent — alongside connection history, per-session notes and video recording, and a Jira Service Desk extension that starts sessions from the ticket window. We found no public information on queues or routing to technician groups, post-session surveys, or per-technician and per-customer reports for billing. 6 9 16 20 21

Report an error

The Skeptic

Branding goes deep — logo, title up to 30 characters, icon, subdomain, own domain by CNAME, even the agent's process name — alongside a website widget, branded invitation pages, per-session notes, chat history and extensions for Jira Service Desk, LiveChat and Telegram. I found no public information on session queues or routing to technicians, post-session surveys, exportable per-technician reports for billing, or AI assistance; the Jira extension sends invites, and nothing documents sessions written back to the ticket. 6 16 20 21

Report an error

Administration, identity & API

panel disagrees Show 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.

Report an error

The IT Support Lead

Roles are genuinely granular — screen view versus control, file manager, terminal, wake-on-LAN, reboot and lock, assigned per device or group with inheritance — and two-factor, password expiry, IP allow-lists and certificate sign-in are applied at technician level, which is how I run a six-person desk. SAML 2.0 single sign-on with an ADFS setup guide gives me the Entra ID login even though Entra is never named, and the HTTP API documents invitation, device, team and connection-history methods with rate limits. We found no public information on webhooks, SCIM or multi-tenant separation, so seven. 4 13 8 7

Report an error

The MSP Technician

Roles with permissions down to individual devices and groups with inheritance, SAML 2.0 single sign-on with Active Directory and LDAP, enforced two-factor and password policies, and a built-in group policy that centrally enforces agent settings are documented, alongside a REST API covering invitations, devices, teams and connection history. I found no public information on SCIM, webhooks, named RMM or PSA integrations, or separate customer tenants — as a service provider keeping sixty clients apart, that last gap matters most to me. 4 7 8 13

Report an error

The Software Support Lead

Technicians get individual accounts with predefined or custom roles and permissions down to screen view, terminal mode, reboot and file manager, with device-level and group-based inheritance, and a built-in group policy enforces agent settings across device groups. SAML 2.0 single sign-on with ADFS setup, LDAP and Active Directory import, enforced two-factor and IP allowlists are documented, and the RESTful HTTP API exposes invitations, devices, technician roles and connection history. We found no public information on SCIM, webhooks, or separate customer tenants for MSPs. 4 7 8 13

Report an error

The Small Office Owner

Roles and permissions are documented to a detail I could set per person and per device group, single sign-on runs over SAML with ADFS and LDAP, users can be imported from and synchronized with Active Directory, two-factor and password policies are enforceable, IP allowlists and certificate sign-in exist, and agent settings are centrally enforced across device groups. The HTTP API is documented with method groups for invitations, devices, technicians and roles, and connection history. We found no public information on SCIM, webhooks, or multi-tenant separation for managed-service providers. 4 7 8 13

Report an error

The Information Security Officer

Role-based permissions reach individual device actions (screen view, control, file manager, terminal, wake, reboot, lock), SAML 2.0 single sign-on with ADFS and Active Directory import are documented, and the HTTP API covers invitations, devices, roles and connection history. Two-factor authentication, IP allow-lists and password policies sit at team level as enforceable settings; we found no public information on SCIM, webhooks, or integrations with named RMM, PSA or MDM products. 4 7 8 13 19

Report an error

The Skeptic

Role-based access goes down to per-device permissions like terminal access and wake-on-lan, SAML single sign-on via ADFS plus LDAP and Active Directory synchronisation are documented, two-factor and IP allow-lists are configured at team level, and a documented HTTPS API covers invitations, devices, technician accounts and connection history with rate limits per plan. I found no public information on SCIM, webhooks, or separate customer tenants for MSPs, which is what I'd ask about before rolling it across clients. 4 7 13 8

Report an error

Session security, audit & reliability

panel disagrees Show 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.

Report an error

The IT Support Lead

Encryption is stated by protocol and algorithm — WebRTC over DTLS/SRTP with AES-128 or 256, WebSocket with AES-GCM or ChaCha20 — plus two-factor via email, authenticator app or Telegram, consent prompts with black screen and input lock, IP allow-lists, brute-force protection, audit logs, and recording off by default. A public status page publishes 90-day uptime per component and a self-hosted edition can keep the relay inside my own network. We found no public information on end-to-end encryption, ISO or SOC certifications, a vulnerability disclosure process or an SLA, so six. 12 13 14 5

Report an error

The MSP Technician

The security statement names the transport encryption per channel (DTLS/SRTP with AES-128 and AES-256, TLS for WebSocket), two-factor with enforced team policies, IP allow-lists, certificate sign-in, brute-force protection, black screen and input lock, connection history with team audit logs, a public status page with published uptime, and code-signed agents; a self-hosted deployment running without internet access is also documented. I found no public information on end-to-end encryption, ISO 27001 or SOC 2 certification, a vulnerability disclosure process, an SLA, or exportable audit logs. 5 12 13 14

Report an error

The Software Support Lead

Encryption is named concretely — 128-bit AES in WebRTC and SSL, DTLS/SRTP with AES-128/256, WebSocket cipher suites — alongside two-factor via email, Telegram and authenticator apps, IP allowlists, brute-force protection, audit logs, connection history, and recording off by default. A public status page shows 90-day uptime around 99.99 percent, and a self-hosted edition runs on the customer's own infrastructure. We found no public information on ISO 27001 or SOC 2 certifications, a vulnerability disclosure policy, an SLA, or exportable audit logs. 4 5 12 13 14

Report an error

The Small Office Owner

The security statement names its protocols and ciphers — DTLS/SRTP with AES-128 or AES-256, TLS with AES-GCM or ChaCha20 — and documents two-factor by email, Telegram or authenticator app, connection confirmation, black screen and input lock, IP allowlists, brute-force protection, audit logs, recordings off by default, code signing for Windows and macOS, and VirusTotal checks of each agent version. A public status page shows uptime figures with all components operational, and a self-hosted deployment on my own infrastructure is documented. We found no public information on ISO 27001 or SOC 2 certification, a vulnerability disclosure policy, an SLA, or export of audit logs. 5 12 13 14

Report an error

The Information Security Officer

Encryption is named to protocol and cipher (DTLS/SRTP with AES-128 or AES-256, TLS with AES-GCM or ChaCha20), two-factor works by authenticator, email or Telegram, black-screen and input-lock protect the user, recording is off by default, audit logs and connection history carry stated retention, brute-force and anonymous-connection protections exist, a status page shows 90-day uptime of 99.994%, and a self-hosted edition can run the relay on our own infrastructure without internet access. We found no public information on ISO 27001 or SOC 2 certification, a vulnerability disclosure policy or published advisories with fixed versions, an SLA, or export of audit logs to a SIEM — gaps that matter to a critical-infrastructure operator. 5 11 12 13 14

Report an error

The Skeptic

The security statement names protocols and cipher suites that stay encrypted even through a TURN relay, two-factor methods, IP allow-lists, brute-force protection, audit logs of technician actions, VirusTotal checks and code signing on both platforms, and the status page shows 99.994 percent over ninety days; a self-hosted edition is documented to run with no internet connection at all. But I found no public information on a vulnerability disclosure policy or advisories, ISO 27001 or SOC 2, an SLA, or export of the audit log — and how fast the last hole was fixed is exactly what I want in writing. 5 12 13 14

Report an error

European sovereignty panel opinion

panel disagrees Show 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.

Report an error

The IT Support Lead

The contracting entity is Point B Ltd in Cyprus — an EU seat — user data is hosted in Germany and Finland on Hetzner, and the hosting and relay providers are listed by country and name; the proxy network also stands in the United States, India, Israel, Brazil and other non-EU countries. A self-hosted edition is documented to run entirely in our own network without internet access, which would put sessions, logs and recordings on our chain, but it starts from 500 devices or 10 technicians on the Enterprise plan with a custom quote. We found no public information on a data processing agreement or certifications, so seven with reservations. 9 13 15 5 11

Report an error

The MSP Technician

The captured pages show Point B Ltd of Limassol, Cyprus as the contracting entity, user data hosted on named infrastructure in Germany and Finland, and a self-hosted edition documented to run on your own servers without an internet connection, which would keep sessions and recordings in our own chain. On the cloud side the proxy infrastructure also stands in the United States, India, Israel and other non-EU countries without a stated safeguard, and I found no public information on a published data processing agreement or on subprocessors beyond the named hosting providers. 5 9 11 13 15

Report an error

The Software Support Lead

The contracting entity is Point B Ltd in Limassol, Cyprus with VAT CY10430957Q, and user data is hosted in Germany and Finland on Hetzner infrastructure, with backups kept in the same region. Proxy infrastructure is also documented in the United States, India, Israel, Brazil, South Korea and Australia, so parts of the session chain leave the EU without a stated safeguard, though a self-hosted edition that runs without an internet connection is documented. We found no public information on a data processing agreement or independent security certifications. 5 9 11 13

Report an error

The Small Office Owner

The contracting entity is Point B Ltd of Limassol, Cyprus, with a VAT number, and user data is documented as hosted in Germany and Finland on Hetzner — that part comforts me for client files. However, proxy infrastructure is documented in the United States, India, Australia, Israel, Brazil and South Korea alongside Germany, and the self-hosted edition that would keep everything on my own servers is available only on the Enterprise plan, annual billing only, by custom quote, with minimums such as 500 devices or 10 technicians. We found no public information on a data processing agreement or a full subprocessor list. 5 9 11 13 15

Report an error

The Information Security Officer

The contracting entity is Point B Ltd in Cyprus, user data is hosted on Hetzner in Germany and Finland, and a self-hosted edition is documented to run entirely on the customer's own infrastructure without cloud services or an internet connection, which is the chain we need for our own networks. In the cloud edition the proxy infrastructure also stands in the United States, India, Israel, Brazil, South Korea and Australia without a stated safeguard, and we found no public information on a data processing agreement, security certifications, or subprocessors beyond the named hosting providers. 5 9 11 13 15

Report an error

The Skeptic

The contracting entity is Point B Ltd of Limassol, Cyprus with a VAT and registration number, and user data sits on named EU infrastructure — Hetzner in Germany and Finland, with backups in the same region and provider — but the proxy network that carries sessions when peer-to-peer fails spans the United States, Israel, India, South Korea and more with no stated safeguard, and I found no public information on a published data processing agreement or certifications. A self-hosted edition documented to operate without internet moves the whole chain onto the customer's own servers, which lifts it above the middle band. 9 13 15 5

Report an error

Pricing transparency

panel disagrees Show 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.

Report an error

The IT Support Lead

The plan maths is public: 4.17, 6.67 and 8.33 EUR per technician per month across the three plans, 0.08, 0.13 and 0.17 EUR per device per month, with 16% off annual payment, and the options page defines what the team, device and one-time-connection limits count. We found no public information on what the option bundles cost, VAT treatment, renewal prices or minimum terms, and the self-hosted edition is a custom quote gated at 500 devices or 10 technicians. Six: I can budget the SaaS side but not the whole picture. 9 10 11

Report an error

The MSP Technician

The three plans publish per-technician and per-device monthly prices, state what each limit counts, list the file-transfer, recording-storage and API-rate differences between plans, and offer 16% off for annual payments. The self-hosted edition is quote-based, Enterprise plan only with annual billing and minimums of 10 technicians or 500+ devices, and I found no public information on VAT treatment, renewal terms, minimum term, or the individual price of the option bundles. 9 10 11

Report an error

The Software Support Lead

All three plans publish per-technician and per-device monthly prices — 4.17 EUR, 6.67 EUR and 8.33 EUR per technician, 0.08 EUR, 0.13 EUR and 0.17 EUR per device — with the licence counted by user accounts, permanent-access devices and one-time connections, a 16 percent annual discount, per-plan storage and file-size limits, and a 14-day trial with no card required. The self-hosted edition is quote-based with minimums of 500 devices or 10 technicians on the Enterprise plan with annual billing only. We found no public information on VAT treatment, renewal prices or minimum term. 9 10 11

Report an error

The Small Office Owner

Plan prices are public with what they count — 4.17 EUR / month per technician and 0.08 EUR / month per device at Standard, 6.67 and 0.13 at Advanced, 8.33 and 0.17 at Enterprise — with the limits explained as user accounts, devices and one-time connections, unlimited client invitations, a 14-day full-access trial with no card required, and 16% off annual payments. But the self-hosted edition is a custom quote available only to business customers on Enterprise, and we found no public information on renewal prices, minimum term, VAT treatment or the commercial terms of a free plan — so the price of the second year is still invisible before I pay for the first. 4 9 10 11

Report an error

The Information Security Officer

Prices are published per plan with their scaling rule — "4.17 EUR / month per technician" and "0.08 EUR / month per device" on Standard, "6.67 EUR / month per technician" and "0.13 EUR / month per device" on Advanced, "8.33 EUR / month per technician" and "0.17 EUR / month per device" on Enterprise, with "Annual Payments 16% OFF" — and the licence counts for team seats, permanent-access devices and one-time connections are explained along with recording storage and file-size limits. The self-hosted edition is a custom quote with a 500-device or 10-technician minimum on the Enterprise plan, and we found no public information on VAT treatment, renewal terms or a minimum term. 9 10 11

Report an error

The Skeptic

Every plan publishes per-unit monthly prices — 4.17 EUR / month per technician and 0.08 EUR / month per device at Standard, rising to 8.33 EUR and 0.17 EUR at Enterprise — with what each limit counts, video storage quotas, file-size caps, a 16 percent annual discount and a 14-day no-card trial. The self-hosted edition is quote-only with a 10-technician or 500-device minimum, and I found no public information on VAT treatment, renewal terms, or what the second year costs — the number that always differs from year one. 9 10 11

Report an error

European sovereignty — proven facts

2 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined — uncited Report an error
Hosting options Self-hostable unverified
Why unverified?

Self-hosted is available only to business customers on the Enterprise plan with annual billing and minimum device or technician thresholds.

1/1 pts 5 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 Getscreen.me

Is Getscreen.me European?

Yes. whats-best.ai classifies Getscreen.me as EU-Made. Its vendor, Point B Ltd, is incorporated in Cyprus, per the vendor’s page captured 6 Nov 2026.

Where does Getscreen.me store data?

Not stated on the vendor’s pages as of 6 Nov 2026.

Does Getscreen.me have a free plan?

Not stated on the vendor’s pages as of 6 Nov 2026.

What are the best alternatives to Getscreen.me?

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: Getscreen.me alternatives.

Where this could be wrong

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.

Sources (21)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage getscreen.me Checked 6 Nov 2026 Details →
  2. 2 Features page (remote support) getscreen.me Checked 6 Nov 2026 Details →
  3. 3 Features page (unattended access) getscreen.me Checked 6 Nov 2026 Details →
  4. 4 Features page (team access) getscreen.me Checked 6 Nov 2026 Details →
  5. 5 Features page (self-hosted) getscreen.me Checked 6 Nov 2026 Details →
  6. 6 Integrations page getscreen.me Checked 6 Nov 2026 Details →
  7. 7 API documentation docs.getscreen.me Checked 6 Nov 2026 Details →
  8. 8 Documentation (SAML single sign-on) docs.getscreen.me Checked 6 Nov 2026 Details →
  9. 9 Pricing page getscreen.me Checked 6 Nov 2026 Details →
  10. 10 Pricing page (options) getscreen.me Checked 6 Nov 2026 Details →
  11. 11 Pricing page (self-hosted) getscreen.me Checked 6 Nov 2026 Details →
  12. 12 Security / trust page getscreen.me Checked 6 Nov 2026 Details →
  13. 13 Security statement docs.getscreen.me Checked 6 Nov 2026 Details →
  14. 14 Public status page status.getscreen.me Checked 6 Nov 2026 Details →
  15. 15 About page (names the operating company) getscreen.me Checked 6 Nov 2026 Details →
  16. 16 Remote control & attended support sessions — found from sitemap getscreen.me Checked 6 Nov 2026 Details →
  17. 17 Remote control & attended support sessions — found from sitemap getscreen.me Checked 6 Nov 2026 Details →
  18. 18 Unattended access & device deployment — found from sitemap docs.getscreen.me Checked 6 Nov 2026 Details →
  19. 19 Unattended access & device deployment — found from sitemap docs.getscreen.me Checked 6 Nov 2026 Details →
  20. 20 Support desk workflow, branding & reporting — found from sitemap getscreen.me Checked 6 Nov 2026 Details →
  21. 21 Support desk workflow, branding & reporting — found from sitemap docs.getscreen.me Checked 6 Nov 2026 Details →