Moorfox

Every machine you look after, in one place.

Remote monitoring and management for Windows and Linux. Remote desktop and terminal, quick support for machines you don’t yet manage, patching on a schedule you set, alerts that reach the right person, a security score for every machine, inventory down to the memory modules, and one small agent that keeps itself up to date.

Free for up to 10 devices, no card. One agent, nothing to open inbound, encrypted end to end.

Watch

Moorfox in 83 seconds.

Why we wrote our own agent, capture pipeline and protocol instead of wrapping VNC or RDP, and a quick look at everything else it does.

Plays from YouTube in privacy-enhanced mode; nothing loads from YouTube until you press play. Watch on YouTube

The full kit

Everything Moorfox does, on one screen.

The complete list, not the highlights. If a thing is not here, Moorfox does not do it yet, and we would rather say so than let you find out later.

Take hold 6

  • Remote desktop multi-monitor, clipboard both ways, Ctrl-Alt-Del
  • Remote terminal PowerShell or a root shell, running as SYSTEM
  • File explorer browse and transfer, no session needed
  • Processes & services inspect, restart, stop
  • Disk usageNew what is filling the disk: tree, file types, treemap
  • Quick supportNew attended help for machines you don’t manage

Keep watch 7

  • Security score thirteen factors, honest about gaps
  • Bitdefender EDRNew detection and response on the devices you pick, $4 each, beside Defender
  • Live inventory down to BIOS, GPUs and memory modules
  • AlertsNew CPU, memory, disk, offline, crashes; emails routed per tag
  • Network isolationNew cut an infected machine off the network; the agent stays connected
  • Streamed logs still readable after the machine goes dark
  • Activity trail append-only; nobody edits history

Set to work 6

  • PatchingNew Windows and Linux updates in a weekly window, held back until they have aged
  • Saved commands your script library, one click on any machine
  • FlowsNew command sequences with triggers, wipe a stolen laptop
  • Groups & tags structure for filtering, alerts and rollouts
  • Fleet enrolment one token onboards a whole estate
  • Your brandingNew name, colours and support contact on the desktop, per group or device

Trust it 5

  • Permissions & guestsNew per-person toggles; guests see only assigned machines
  • Self-healing updates checksum-verified; a bad build reverts itself
  • Controlled rolloutsNew group by group, pin or roll back per device
  • Nothing inbound agents dial out; no port forwarding, ever
  • Encrypted end to end media goes peer-to-peer where it can
Seen working

The screens you would live in.

Uncropped, from a live dashboard. The product and this site share one palette, so what you see here is what you get there.

Remote desktop, locked screens included

A Windows server at its lock screen, mid-session: send Ctrl-Alt-Del, sign in, work. The status bar keeps the truth in view, frame rate, bandwidth, latency, and whether media is flowing peer-to-peer. The person at the machine always sees who connected.

Read the docs: connect and manage
A Moorfox remote desktop session showing a Windows Server lock screen, with a toolbar for clipboard, shortcuts and screenshots, and a status bar showing 30 fps and a peer-to-peer connection

Every monitor, one click away

Multi-monitor machines are the rule, not the exception. The Screens menu shows a live thumbnail of every display on the remote machine: open one in its own browser tab, switch the current tab to it, or open them all at once and work across the lot side by side.

Read the docs: connect and manage
The Moorfox Screens menu in a remote session, listing three displays with blurred live thumbnails and options to open each in a new tab, view it in the current tab, or open all other screens in tabs

A real terminal, running as SYSTEM

PowerShell or cmd on Windows, a root shell on Linux, on any enrolled machine including headless servers where a desktop has nothing to show. File explorer, processes and services sit one tab away in the same pane.

Read the docs: connect and manage
The Moorfox management pane with Terminal, File explorer, Processes and Services tabs, running PowerShell as NT AUTHORITY\SYSTEM

A security score that shows its working

Every device scored out of 100 across thirteen factors: disk encryption, antivirus and EDR, firewall, patching, Secure Boot and more. Anything the machine could not prove is excluded from the score rather than guessed, and the card says exactly which points those were.

Read the docs: the security score
A Moorfox security score card showing 73 out of 100, medium risk, with per-factor findings such as disk not encrypted, automatic updates disabled and Defender for Endpoint installed but not enabled

Patches that wait until they are safe

A policy names a weekly window, evaluated in each machine’s own timezone, and how long an update must have been out before it is allowed on. That wait is counted from the day the machine first saw the update, not from a vendor’s release date, so a bad patch pulled in its first week never reaches your fleet.

Read the docs: patching
The Moorfox new patch policy dialog: security updates only, a Saturday 02:00 window evaluated in each device's own timezone, and a seven day wait counted from when each machine first saw the update pending

Alerts you tune once, then trust

Thresholds for CPU, memory, disk, time offline and Windows crashes, set once for the whole organisation. CPU and memory only alert when the level holds for the window you chose, the email switches say which types are worth a message, and routing rules decide which person gets it.

Read the docs: alerts and settings
The Moorfox alert thresholds card: CPU above 95% for 10 minutes, memory above 90%, disk above 90%, offline for 10 minutes and Windows crashes, each with an email switch

Contain an infected machine in one click

When a machine looks compromised, Isolate network in its Actions menu cuts it off the local network and the internet: no shares, no other PCs, no calling home. The Moorfox agent stays connected, so you can still remote in, open a terminal and pull files while you work out what happened. Offline machines are isolated the moment they check in, and a watchdog lifts it on its own if the agent ever loses its way back.

Read the docs: network isolation
A Moorfox device page for NORTHBAY-WS01 with a banner reading Network isolated, cut off from everything but the Moorfox agent, and a Lift isolation button

Flows, for the day you hope never comes

Saved commands chain into flows. This one runs the moment a laptop reported stolen next checks in: clear the mail cache, remove company directories, wipe the home folders. Destructive steps demand the device’s name typed back before they will run at all.

Read the docs: commands and flows
The Moorfox new flow dialog: a flow named 'Stolen laptop: wipe company data', triggered when a device is reported stolen, with destructive steps and a warning that running it requires a typed confirmation of the device name

An activity trail nobody can quietly edit

Every sign-in, remote session, script run and settings change, recorded with who, when and how long. The log is append-only: entries cannot be edited or removed, by anyone, which is the only kind of audit trail worth keeping.

Read the docs: the activity log
The Moorfox activity page listing enrollment tokens created, flows created, and remote desktop sessions with their durations, each attributed to a user and filterable by category

What is filling that disk, without remoting in

A disk alert names the machine. The Disk usage tab names the folder: a size-sorted tree, a breakdown by file type, the largest files and a treemap, the way WinDirStat draws one. The scan runs at background priority on the remote machine, so the person using it never notices, and the report stays in the dashboard after the machine goes offline.

Read the docs: disk usage
The Moorfox Disk usage tab for a scanned C drive: a folder tree with share bars, sizes and file counts, beside a breakdown of the same space by file extension

Permissions per person, and guests who see three PCs

Admin, technician and guest are starting points, not cages. Tick Add devices for the field tech who images machines without handing them billing. Give a customer’s office manager a guest account that can remote into their own PCs and cannot see that the rest of your estate exists. The server checks every request, not just the menu.

Read the docs: users and permissions
The Moorfox Users page: admins, a technician, a technician with custom permissions and a guest limited to three assigned devices, each with Permissions, Send reset and Remove buttons

Your name on the desktop, not ours

Managed Windows machines carry a small widget with the machine name, its address, Managed by your company and your support number. Set the colours with a live preview, give each customer group its own help desk contact, and hide the widget on a group of servers or a single device. The banner that tells someone their screen is being viewed follows the same branding.

Read the docs: desktop widget and branding
The Moorfox organisation settings card: name, support email and phone with switches to show them on managed machines, colour swatches for the widget background and accent stripe, and live previews of the desktop widget and the session banner
Enrolment

How it works

Three steps, and the machine appears in your dashboard within a minute.

Pick Windows or Linux

The wizard asks what you are enrolling first, then shows only what that platform needs.

Send an installer, or one line

Easy downloads an installer with the enrolment code already inside it, to double-click on the machine. Advanced gives you the PowerShell or shell one-liner, with a fleet token when you are moving a whole estate at once.

Manage it from anywhere

The device appears online with its inventory, in the group you file it under. Open a remote desktop session or a terminal straight from the dashboard.

The Moorfox add-a-device wizard with the operating system already chosen, offering an Easy installer download and an Advanced one-line command
The actual enrolment page: pick the platform, then a file to send or a line to paste. Either way the checksum is verified before anything runs.
Read the docs: the full installation process
Attended support

Moorfox QuickSupport.

For the machines you don’t manage: a one-off download, a nine-digit code read over the phone, and their explicit permission before you see a thing.

A code, not an install

Send anyone your team’s support link. They run one small program, nothing installs, and it shows a nine-digit code that only your team can connect to. They read it out, you type it in, they click Allow, and their screen is in front of you. Close the window and it is over, with nothing left behind.

See how it connects, step by step
The Moorfox QuickSupport window on a customer's desktop showing a nine-digit code and the note that nothing is installed on this computer
Changing over?

See how it compares.

Honest side-by-sides with the tools you might pick instead, our gaps included. We would rather you choose right than choose us.

Pricing

Ten devices free. Then two dollars.

  • No tiers, no contracts, no minimums, no sales call.
  • The free tier is the whole product, not a trial with the good parts removed.
Free $0 Up to 10 devices, every feature, no card.
Pro $2 Per device per month, and the first 10 are still free.
Quick support $10 Per technician per month, and only for the ones who ran a session.
Bitdefender EDR $4 Per device per month, on the devices you switch it on for.

See the full pricing, and how it compares

Bring your fleet in from the moor.

Sign up, install one agent, and your first machine is on the screen in a couple of minutes. Ten devices are free forever, so there is nothing to decide yet.

Start free