Monitoring, remote control, backup, a credential vault and a helpdesk. One login, one bill, unlimited devices. Built by the MSP that runs its own desk on it.
Endpoints under management today
Per technician, per month, plus GST. Every feature, unlimited devices
Instead of five vendors, five renewals and five support queues
One line installs the agent. From then on it streams CPU, memory and disk, and raises the alert before the customer picks up the phone. Machines group into sites, so every client has a clean view of their own estate.
Passwords, secrets and live TOTP codes encrypted with AES-256-GCM, with every reveal on the audit trail. Tickets arrive at a per-tenant address or the public portal, and the reply goes out under your own name.
Sites for an MSP are customers. For an internal team they are offices, departments or campuses. Same structure either way. One console above, isolated tenants below.
Servers, workstations, the domain controller
104 devicesNAS, scanners, the backup target
38 devicesReception, consult rooms, one print server
61 devicesLaptops on home and mobile networks
45 devicesThe job is identical: keep the machines patched, get on them fast when they break, hold the credentials safely, answer whoever raised the ticket. An internal team just does it for one organisation instead of thirty, and pays for technicians, not machines.
Every customer isolated: their own devices, documentation, credentials and ticket queue. Taking on a client costs nothing extra in licensing.
One organisation, nothing switched off. Split by site, department or campus, and pay for the technicians who use it.
No editions, no modules to buy back. Every seat has the whole thing from the first day of the trial.
Saved PowerShell and batch scripts, run on any machine in seconds. Clear the print queue, restart the service, done.
Remote sessions are written up automatically from the recording, ready to file. The knowledge base builds itself.
A time-limited link to one machine, dead after they connect or when it expires. No account to create.
MFA, IP allow-listing, role-based access and super-admin impersonation, with the whole trail behind it.
Updates itself from RSA-signed releases, verifying signature and hash before it swaps a binary.
What is installed, where, and on which build, with event logs, services and scheduled tasks a click away.
An RMM is the most privileged software an MSP runs: it can reach any machine, on any client site, at any hour. We build it as though somebody is already inside, because the controls that matter are the ones that hold when they are.
Multi-factor is mandatory on every account, not a setting an owner can forget. Add IP allow-listing, roles scoped to individual customers, and a remote-access level per technician: unattended, or the person at the machine accepts first.
The vault seals each secret under its own key, and those keys under a master held in AWS KMS. Reading one is an auditable act, and the trail records who opened what and when.
Joining a customer's tenant, restoring their mail, watching a recorded session: each writes an audit entry, and the ones that warrant it will not run until the technician states a reason. That is what you hand an auditor.
Every control below runs on a timer rather than a good intention. The point of a posture screen is not that somebody looks at it; it is that the platform keeps looking when nobody does.
Every machine reports what it is missing and how severe. Windows updates install inside the maintenance window you set, per policy, per site.
BitLocker across the whole fleet on one screen: which disks are protected, and whether anybody could actually recover them.
Rules evaluated continuously against live telemetry, raising a ticket on the rising edge rather than every minute it stays wrong.
Recordings, activity history and metrics are pruned to the periods you set. There is deliberately no "keep forever": a schedule the product does not honour is not a schedule.
Endpoint backups run to their own schedule, and the console reports what could actually be restored rather than whether a job ran.
New agent releases roll out from RSA-signed manifests, with the signature and hash verified on the endpoint before a binary is replaced.
Contractor links die on use or on expiry, one-time shares open once, and offline machines age out on the schedule you choose.
Click a machine and you are on it before you have finished sitting forward. The mouse feels wired in, not posted overseas. That speed is engineered, not promised.
Your click wakes the machine itself. No polling, no spinner: a live screen in a second or two.
Relays run in AWS regions around the world and every session pairs on the nearest one. Round trips stay under 50 milliseconds, and remote stops feeling remote.
Round trip for a fleet near one of the relay regions, instead of an ocean crossing on every mouse movement.
A$77 a month all up on a tax invoice. Every seat carries the whole platform, including RMM, remote control, backup, vault, helpdesk and AI auto-docs, with unlimited managed devices. Monthly billing, cancel any time, no card to start the trial.
The heavy lifting that costs real money is metered, pooled across the account and itemised on the invoice. A quiet month costs less.
File and full-image backup. Point it at your own AWS bucket, or use ours.
Every recorded remote session written up. Flat rate, any volume.
* We encourage you to use your own AWS bucket: point backups at it and you pay us nothing for storage. Our storage is charged monthly at $0.20 per gigabyte, with usage visible in-platform before it reaches the bill. All amounts are AUD and exclude GST; 10% is added and itemised on your tax invoice.
Create your account, verify your email, and your trial starts on the spot. Nothing to pay up front, no card, and we will help you migrate off the stack you are on.