Frequently asked questions

There are four ways to buy, all through secure Stripe checkout in USD:

1. Self-host — one-time $399 per deployment. You run the control server on your own box, VM, or cloud (Windows IIS or Linux). One server instance, unlimited machines, and Year 1 of updates included.
2. Hosted (we run it) — the same $399 license plus a monthly managed-service fee. We provision, patch, back up, and support your server. Starts with a 7-day free trial.
3. No-upfront (monthly, rent-to-own) — $0 down, cancel anytime. The $399 license is paid off over 36 months, then it's yours. Same 7-day free trial.
4. On-Prem / air-gapped — one-time $799. Runs fully offline with its own internal-CA HTTPS and offline signed updates; the license and offline kit are delivered by hand within one business day.

You can convert a self-hosted license to hosted anytime (keep the license, pay a service-only fee), or move a hosted deployment back to self-hosting anytime (keep your license and your data).

A single MyRemoting license covers one control-server instance with unlimited machines connected to it — your hardware is the only limit. It includes every feature (remote control, file manager, console, fleet automation, monitoring, inventory, alerting, collaboration, session audit/recording, and the security controls) with no per-feature add-ons. Year 1 of software updates is included; updates are optional after that and the software keeps working without them. The On-Prem/air-gapped edition ($799) adds fully offline operation: internal-CA HTTPS, an offline license, and signed offline updates.

Yes. You always own your license and can move to self-hosting at any time. With self-host and On-Prem you own the license outright on purchase; with the no-upfront plan you own it after the 36 monthly payments; hosted uses the same owned $399 license. You also own your data. If you self-host, your data stays inside your own walls — the vendor receives only license-heartbeat metadata. If we host it for you, we process your data strictly as a data processor under a Data Processing Addendum (published at myremoting.iownsoftware.com/legal/). Because licensing is offline-verified, a self-hosted server keeps working through brief license-service outages.

Unlimited. One license covers one control-server instance and as many machines as you want to enroll — there's no per-seat or per-endpoint fee. In practice the only ceiling is the capacity of the server you run it on. You add machines from your server's dashboard, which hands you a pre-configured installer or a shareable install link for Windows, macOS, or Linux that drops each machine straight into a group.

The hosted and no-upfront plans start with a 7-day free trial. Checkout verifies a card but charges nothing during the trial. If you cancel before the 7 days are up, you're never charged. If you keep going, billing begins when the trial ends — the monthly managed-service fee for hosted, or the first monthly rent-to-own payment for the no-upfront plan. It's the risk-free way to stand up a server and try the full product before committing.

Every purchase includes Year 1 of updates. After that, updates are optional — your software keeps working indefinitely without them, so you're never forced onto a subscription just to stay running. Self-hosted servers apply a published update when an admin clicks Install on the Server page, so you pick a low-downtime moment; on managed hosting we do that step for you. The On-Prem/air-gapped edition receives signed offline updates you can import by hand, so an isolated network never needs internet access to stay current.

The monthly no-upfront plan can be cancelled anytime, and the hosted plan's 7-day trial can be cancelled before it ends with no charge at all — that trial is the intended way to evaluate risk-free before any money changes hands. Hosted service is billed monthly, so you stop the recurring fee whenever you cancel (your owned license stays yours, and you can move the deployment to self-hosting keeping your license and data). For the specific refund terms that apply to a one-time license purchase, see the Usage & License Agreement at myremoting.iownsoftware.com/legal/.

There's no per-seat fee. A license covers one control-server instance with the operators you need — you create per-user logins from the dashboard, each with mandatory two-factor authentication, and scope them to features and machine groups with roles (including scoped admins). Like machines, you're really limited only by the server you run it on, not by a seat count.

The intended way to try MyRemoting risk-free is the 7-day free trial on the hosted and no-upfront plans: checkout verifies a card but charges nothing, so if you cancel before the trial ends you're never billed — that's your chance to stand up a real server and use the full product before any money changes hands. Monthly plans (the hosted managed-service fee and the no-upfront rent-to-own) can be cancelled anytime, which stops the recurring charge going forward, and your owned license and your data stay yours. For a one-time license purchase (self-host or On-Prem/air-gapped), the specific refund terms are set out in the Usage & License Agreement at myremoting.iownsoftware.com/legal/ — review those terms before you buy, or start with the free trial so you can evaluate everything first.

Both run the exact same product; the only difference is who operates the control server.

- Self-host: you buy the license once (one-time $399 per deployment) and run the control server yourself on your own box, VM, or cloud (Windows IIS or Linux). One server instance, unlimited machines (your hardware is the limit). Year 1 of updates is included; updates are optional after that, and the software keeps working without them.

- Hosted: same $399 license plus a monthly managed-service fee, and we run the server for you. It starts with a 7-day free trial that verifies a card but charges nothing until the trial ends (cancel before then and you're not charged).

There's also a no-upfront option: $0 down, cancel anytime, and the license pays off over 36 months (then it's yours), with the same 7-day card-verified trial. Either way you own your license and can move to self-hosting whenever you want. Checkout is handled by Stripe, in USD.

Self-hosted: your data stays inside your walls. The control server runs on your infrastructure, and the vendor receives only license-heartbeat metadata. Licensing is offline-verified, so your server keeps working across brief license-service outages.

Hosted: the vendor runs the server for you and processes your data as a data processor under a Data Processing Addendum (DPA). The legal terms that govern this are published at myremoting.iownsoftware.com/legal/ (Usage & License Agreement, Privacy Policy, Data Processing Addendum, Sub-processors, and Third-Party Notices).

You can switch either direction, and you always own your license and your data.

- Self-hosted to hosted: convert anytime. You keep your license and just pay the service-only fee for us to run it.

- Hosted to self-hosted: move back anytime and keep both your license and your data.

Because the license is yours regardless of who operates the server, there's no lock-in to a hosting arrangement.

With hosting, we run the control server so you don't have to. That covers provisioning (standing the server up for you), patching it, backing it up, and supporting it. You get the same full product and feature set as self-hosting.

Pricing is the one-time $399 license plus a monthly managed-service fee, and it starts with a 7-day free trial that verifies a card but charges nothing until the trial ends. Cancel before the trial is up and there's no charge.

You need a machine to run the control server (your own box, a VM, or any cloud) on either Windows (IIS) or Linux, plus a domain name and a TLS certificate. That single server can manage unlimited machines.

Getting started is three steps:

1. Stand up the control server on your box, VM, or cloud. A built-in readiness check confirms your domain, ports, and certificate are correct.
2. From the server dashboard, choose Add a machine. It hands you a pre-configured installer or a shareable install link for Windows, macOS, or Linux that drops machines straight into a group.
3. Sign in from any modern browser or the iPad app and control your fleet.

On Linux, the server can obtain HTTPS automatically; on Windows you run it under IIS with your certificate.

The On-Prem / air-gapped edition is for environments that never touch the internet. It's a one-time $799 license and runs fully offline: it uses its own internal-CA HTTPS, an offline license, and signed offline updates you import by hand, so there's no egress required at any point.

Because it's delivered for a no-internet environment, the license and offline kit are handed over directly within one business day rather than provisioned online. Everything else is the same self-hostable product; it's essentially a strict, no-egress superset of the standard self-hosted deployment.

If you self-host, keeping backups is your responsibility — only a hosted deployment is backed up for you by the vendor. Backup, restore, and migration are all built into the Server page.

1. To back up, open the Server page and download a backup — a single archive of your server's state, including its configuration, users, enrollment tokens, and certificates. Save it somewhere safe and repeat on your own schedule.
2. There's also an offline option: with the server stopped, run the server binary with its backup/restore flag from the command line.
3. To restore, go to the Server page and upload a backup; it's staged and then applied automatically the next time the server starts.
4. To migrate to a new server, stand up a fresh control server, restore your backup onto it, then re-point your domain/DNS at the new server.
5. Your agents reconnect on their own using their saved tokens, so there's no need to re-enroll any machine.

If you'd rather not manage backups yourself, you can convert to managed hosting at any time — the vendor then backs up the server for you, and the move seeds the managed server from your backup so there's no data loss (and you can move back to self-hosting later, keeping your license and data).

The control server is deliberately lightweight. It runs on either Windows (under IIS) or Linux, and the control plane is light enough that a modest small VM — on the order of one CPU and about 1 GB of RAM — runs it comfortably. You size up mainly for your fleet size and relay bandwidth, not for the raw number of machines. You'll also need a domain name and an HTTPS certificate: on Linux the server can obtain and renew one automatically from Let's Encrypt for your domain; on Windows you run it under IIS with your own certificate. A built-in readiness check then confirms your domain resolves, the port is open, and the certificate is valid — and that the server is reachable from outside. On the endpoint side, agents run on Windows (10, 11, and Windows Server), macOS, and Linux, and operators connect from any modern browser on desktop or mobile, plus the installable iPad/desktop app.

The agent runs on Windows, macOS, and Linux. Windows and macOS get full desktop control — live screen with real hardware keyboard/mouse/scroll, special keys, and cursor, multi-monitor, plus file manager, terminal, processes, and power controls. On Linux you get the terminal, file manager, process management, and power controls (no desktop screen sharing). One lightweight agent covers everything, and a single control server manages an unlimited number of machines across all three platforms.

From your server dashboard, open the machine list and choose to add a machine. MyRemoting hands you either a pre-configured installer or a shareable install link for Windows, macOS, or Linux. Run the installer on the target machine (or send the link to whoever is at it), and the machine drops straight into the group you picked, inheriting that group's access rules. There's no per-machine configuration to type in — the installer carries the server address and enrollment details for you.

For unattended fleet machines, no — once the agent is installed it stays enrolled and you manage it from the dashboard. The person at the machine does keep control through a tray/menu-bar icon: they can confirm the agent, pause remote control, set a session time limit, or change the access code, and by policy a controlled session shows a clear "you're being controlled" banner. For one-off attended help, they do participate — you send a code-and-link, they open it and enter the code to run a one-time helper that installs nothing permanent and self-removes afterward. Controlling any machine also requires that machine's local login or access code on top of your console sign-in (the per-machine credential gate).

No special client. Operators sign in from any modern web browser and control the full fleet from there — screen, terminal, files, and every management tool run in the browser. On iPad (and desktop) you can install MyRemoting as an app from the browser and add it to your home screen; touch sessions support pinch-zoom and the usual gestures. That's it: no viewer download, no per-machine software on the operator side.

Yes. Machines connect over a private WireGuard mesh overlay, so they reach each other even across NAT and typical firewalls without you opening inbound ports on every endpoint. When a network won't cooperate with the overlay (strict NAT or UDP blocked), MyRemoting automatically falls back to a secure relay so the session still connects. Inside a browser session a secure loopback proxy provides the trusted origin the viewer needs for clipboard and other features. The result is that machines behind home routers, office firewalls, or cloud VPCs all become reachable from your dashboard without manual port forwarding.

Any device with a modern web browser works — Android phones and tablets included, not just iPad. Operators sign in from the browser and get the full fleet from there: screen, terminal, files, and every management tool, with touch sessions supporting pinch-zoom and the usual gestures. There's no operator-side client to install and nothing that's Apple-only. The installable app is highlighted on iPad and desktop, where you can add MyRemoting to your home screen or dock from the browser for a one-tap, app-like launch; on an Android or other phone you simply use the browser. Note that live screen control needs a Windows or macOS machine on the other end (on Linux you get terminal, files, processes, and power) — but that's about the target machine, not the phone or tablet you're connecting from.

Access is protected in two independent layers, so a single stolen password is never enough.

First, the operator console. Every user has their own login with mandatory TOTP two-factor authentication and email-based recovery. You can also register passkeys (Face ID, Touch ID, or Windows Hello via WebAuthn) for phishing-resistant sign-in, and repeated bad logins trigger a brute-force lockout. Roles and groups scope each operator to specific features and machine groups, and scoped admins let a group lead manage users only within their own machines.

Second, a per-machine credential gate. Even after you're signed in to the console, actually controlling a given machine requires that machine's local login or an access code on top of your console session. So console access and machine access are separate keys, and losing one doesn't hand over the other.

The agent puts a tray icon (menu-bar icon on macOS) in front of the person physically at the machine, and it gives them real authority over the session. From it they can confirm the agent, pause remote control at any moment, set a time limit on the session, or change the access code.

During a session the operator can also blank the remote screen so onlookers near the machine can't see what's happening, lock remote input, and lock the workstation automatically on disconnect. These privacy toggles auto-revert so nothing is left in a locked-down state by accident. For attended sessions, the person at the machine sees an explicit consent prompt and a clear "you're being controlled" banner for the duration.

No. MyRemoting's attended support is deliberately install-free and temporary.

With code-and-link support, the person you're helping opens a link and enters a code, which runs a one-time helper. Nothing permanent is installed: the helper survives a reboot so a support session isn't broken by a restart, and it self-removes when you're done. There's also a browser-only, view-only support mode that requires zero install at all. And any machine's screen (view-only or full-control) or a single file can be handed off as a time-limited instant share link, minted either from the dashboard or by the person at the machine.

You get policy controls up front and a full record after the fact.

Unattended-access policy is set per operator and per machine group: you can require access to fall within business hours, require MFA, and require a typed reason before a session starts, with a consent banner shown on the endpoint. To keep the operator console itself locked down, access allow/block lists restrict it to known source IPs (machines and agents are always exempt, with fail-safes so you can't lock yourself out).

For accountability, an append-only session audit log records who accessed what and when, exportable to CSV. You can also enable session recording with in-browser playback, kept on rotation locally or shipped to S3-compatible storage.

Yes. Credentials you save for a machine are encrypted by the agent, per operator, so what the server stores is ciphertext it cannot read. The control server never holds a key that would let it (or anyone with access to it) recover your saved passwords.

Credentials used by the fleet script runner are handled even more strictly: they're used for the run and never stored at all. Combined with the per-machine credential gate, this means machine secrets stay scoped to the operator who owns them rather than pooling on the server.

It depends on how you deploy.

If you self-host, your data stays inside your own walls. The vendor receives only license-heartbeat metadata, and because licensing is verified offline, your server keeps working across brief license-service outages. If we host it for you, the vendor processes your data strictly as a data processor under a Data Processing Addendum.

Either way, you own your license and your data, and you can move a hosted deployment back to self-hosting at any time. All the legal documents are published at myremoting.iownsoftware.com/legal/, including the Usage & License Agreement, Privacy Policy, Data Processing Addendum, Sub-processors list, and Third-Party Notices.

Checkout runs through Stripe and all prices are in USD. What you pay depends on how you run MyRemoting: self-hosting is a one-time $399 per deployment (Year 1 of updates included); hosted is that same $399 license plus a monthly managed-service fee; the no-upfront plan is $0 down and pays the license off over 36 months (then it's yours); and On-Prem/air-gapped is a one-time $799. The hosted and no-upfront plans start with a 7-day free trial that verifies your card but charges nothing until the trial ends — cancel before then and you're never charged. You always own your license. Manage your plan, update your card, view invoices, and cancel a monthly plan anytime from the Account page.

Operators are per-user logins, each with mandatory TOTP two-factor (and an optional passkey via Face ID, Touch ID, or Windows Hello). From your server dashboard: (1) open the Users area and invite an operator by email — they set a password and enroll 2FA on first sign-in; (2) assign a role, which bundles the feature permissions they get; (3) scope them to one or more machine groups, so they only see and act on machines in those groups — and any new machine added to a group inherits that access automatically. To delegate user management without handing over the whole fleet, make a group lead a scoped admin: they can manage users only within their own machines/groups, and can't grant permissions they don't already hold. Note that even after signing in, controlling a machine still requires that machine's own local login or access code (the per-machine credential gate), and repeated bad logins trigger a brute-force lockout.

Yes. You can set your own company name, logo, and accent color, and that branding carries across the operator console, the agent, and the machine installer — configured once on your server and applied fleet-wide. The person at a machine sees your brand on the agent's access gate, not a generic product screen. A small "powered by MyRemoting" line remains.

No per-machine work is needed. Agents auto-update: your control server publishes new agent builds and machines pull them automatically (and an agent that ever goes offline after an update self-recovers via its service watchdog). The control server itself updates on your schedule: when a newer build is published, the Server page shows an update-available notice and an admin clicks Install to apply it and restart, so you pick a low-downtime moment. On managed hosting we do that step for you as part of the service; on self-hosted plans you click Install yourself. Year 1 of updates is included with every license; after that, updates are optional and the software keeps working without them. On-Prem/air-gapped deployments receive signed offline updates you import by hand.

Hosted customers get managed support as part of the service — we provision, patch, back up, and support your server — and you can reach the team from the Account page on the product site. During setup, a built-in readiness check confirms your domain, ports, and certificate before you go live, and the dashboard walks you through adding your first machine (it hands you a pre-configured installer or a shareable install link for Windows, macOS, or Linux). The formal reference library — Usage & License Agreement, Privacy Policy, Data Processing Addendum, Sub-processors, and Third-Party Notices — is published at myremoting.iownsoftware.com/legal/.