Product roadmap

What we are building,
and how we decide.

Help MSPs see an issue in context, know who owns it, act with control, and check the result. This page shows where each part of that stands today, with honest status labels instead of promised dates.

Only items marked Shipped are available today. Last reviewed November 2026.

How we decide

Evidence first. Then the next step.

Three goals, in order

Each goal builds on the one before it.

01

Reliable daily operations

An issue is detected, owned, acted on, checked afterward, and reopened if it comes back.

02

Connected, governed operations

Stable APIs, the integrations partners actually run, and AI assistance that stays inside the permissions you grant.

03

Enterprise-ready operations

Proven at larger scale with documented recovery and trust evidence.

Status labels. Shipped: running on production today. In verification: built, and being checked by someone who did not build it. Building: being worked on now. Planned: designed and sequenced. Exploring: evaluated only if operator evidence supports it.

Tier A

RMM 1.0

Tier B

SuperRMM 1.0

Planned · not available to purchase

SuperRMM 1.0

The planned $10 per device monthly tier adds governed AI and connected operations to A. It may be sold only after release acceptance and the RevEngine Triage pilot shows measured technician time saved; if the pilot does not show that result, the owners will revisit the price. No delivery date is stated.

Tier C

SuperRMM 2.0

Planned · scope and effort not estimated

SuperRMM 2.0

The planned tier adds broader native business, backup, migration, endpoint, security, email, network and CRM engines, plus mobile and enterprise qualification. The remaining admitted scope and effort are unresolved, pricing is to be announced, and no delivery date is stated.

The tiers follow the current product plan. Full release acceptance has not been established for any tier.

Status by area

Where each capability stands.

Generated from our product roadmap. An item is Shipped only when production runs the release that carries it.

  • AI spending controls (Building). Review usage, set spending limits and stop automated assistance when needed.
  • API token restrictions (Building). Limit token permissions, network access and lifetime.
  • API usage tracking (Building). Track integration usage and manage key expiry, availability and request limits.
  • Integration roles (Building). Restrict what an API identity can read and change.
  • Integration token lifecycle (Building). Set when integration access begins and expires and which customer it covers.
  • Named API permissions (Building). Give each integration key the permissions needed for its purpose.
  • Partner API access (Building). Limit integration access and retrieve large result sets in smaller pages.
  • Restricted API requests (Building). Apply access permissions and request limits to integration calls.
  • Role-aware API access (Building). Keep an integration's permissions aligned with the user's access.
  • Signed event notifications (Building). Let an integration verify that an incoming event came from the platform.
  • Related alerts (Building). Connect alerts and logs across devices to investigate a shared problem.
  • Alert routing (Shipped). Route alerts by client, check type and severity to email addresses or a webhook. Release notes →
  • Maintenance windows (Shipped). Pause alerts for a device during planned work. Release notes →
  • Alert rules (Building). Threshold and heartbeat rules that group related alerts and respect maintenance.
  • Alert templates (Building). Reusable alert settings with severity-based routing and test messages.
  • Event details (Building). Open any event to see its full details in one place.
  • Sustained-condition alerts (Building). Alerts wait for a condition to persist, which cuts noise from brief spikes.
  • Read-only assistant interface (Building). Query operational information through an interface that respects customer access.
  • Activity log (Shipped). Key administrative actions are recorded with who did what and when. Release notes →
  • Verifiable audit log (Shipped). Administrative actions are chained so any later change to the record can be detected. Release notes →
  • Anchored audit history (Building). The audit record is anchored every day so its history can be checked independently.
  • Protected audit history (Building). Protect recorded audit events against changes by the application account.
  • Queued actions for offline devices (Shipped; reboot and antivirus actions). Actions wait for an offline device and run when it reconnects. Release notes →
  • Scheduled scripts (Shipped). Run library scripts at login, startup, once or on a schedule for an organization or location. Release notes →
  • Automation library (Building). Reuse automation steps across recurring maintenance tasks.
  • Event-driven automations (Building). Run an action automatically when an event happens.
  • Scheduled tasks (Building). Run tasks daily, weekly, monthly, once, on demand or when a check fails, including scheduled reboots.
  • Backup and recovery states (Building). Distinguish a completed backup job from an available restore point and verified recovery.
  • Snapshot restore (Building). Restore files from a verified backup snapshot.
  • Verifiable backups (Building). Each backup carries a manifest that can be verified before a restore.
  • Client portal (Shipped). Your customers open and follow support requests in a branded portal. Release notes →
  • Branding (Building). Show your own brand to your customers.
  • Configuration drift (Building). Compare device settings with a baseline and identify changes.
  • Clients and sites (Building). Organize devices by client and site.
  • Customer export and erasure (Building). Define which records are exported, erased or retained during customer departure.
  • Customer-bound changes (Building). Check server-side customer access for each change to customer records.
  • Separate database per workspace (Building). Each MSP workspace has its own database and role.
  • Strict workspace boundaries (Building). Workspace boundaries are checked by exact match, never by a range.
  • Workspace lifecycle and billing (Building). Each MSP workspace has its own branding, entitlements and billing.
  • Workspace scoping everywhere (Building). Every data store refuses a read that is not scoped to the current workspace.
  • Departure data export (Building). Provide an export path with clear availability and exclusions.
  • Simple to run (Building). The platform runs on a single server without extra infrastructure services.
  • Connected experience information (Building). Bring device experience measurements together while showing access limitations clearly.
  • Device audit (Building). Hardware, patches, security, services and software collected for each device.
  • Device change log (Building). See what changed on a device over time.
  • Device deletion coverage (Building). Define which records follow a deleted device and which history remains.
  • Device detail (Building). A full view of each device in one place.
  • Device record continuity (Building). Keep device history when a device is enrolled again and distinguish retired assets.
  • Fast device lists (Building). Device lists stay current and quick as devices and tags change.
  • Device lifecycle continuity (Building). Keep declared management records available when a device returns after inventory removal.
  • Email security gateway connections (Shipped). Connect email security gateways and see their activity and response actions in each customer's security view. Release notes →
  • Agent updates (Shipped; Windows agents). Agents update themselves to the current release. Release notes →
  • Visible tray icon (Shipped). On Windows 11 the agent icon stays visible beside the clock. Release notes →
  • Agent binary signatures (Building). Verify the publisher of a downloaded agent binary.
  • Agent health watchdog (Building). A watchdog restarts the agent if it stops responding.
  • Agent installer links (Building). Share a download link that installs the agent for the right customer.
  • Per-device agent credentials (Building). Each device holds its own credential, so one device can never speak for another.
  • Signed agent commands (Building). The agent refuses any command that does not carry a valid signature.
  • Signed agent updates (Building). Every agent update is signed, and devices refuse an update without a valid signature.
  • Update checks always on (Building). Update signature checks on a device cannot be switched off from configuration.
  • Windows agent signing (Building). Check the publisher identity of Windows agent binaries.
  • Security awareness training (Shipped). Assign video training with optional quizzes and run tracked phishing simulations. Release notes →
  • Endpoint protection connectors (Building). Connect the endpoint protection tools your customers already use.
  • Security posture (Building). See disk encryption, antivirus and firewall status for each device.
  • Zero Trust application policies (Building). Review application rules and approve requests from one queue.
  • Cloud app security posture (Building). Collect findings from cloud apps and raise incidents from rules.
  • Credential vault (Building). Keep operational credentials in a controlled store.
  • Service desk integrations (Building). Send events to the service desk tools you already use.
  • Apple device management (Shipped). Enroll iPhones, iPads and Macs and send refresh, lock and wipe commands. Release notes →
  • Lost-device mode (Building). Help locate a missing managed device using supported mobile controls.
  • WAN monitoring (Shipped). Get an alert when repeated checks show a site's internet connection is down. Release notes →
  • Device checks (Building). Checks for disk space, CPU load, memory, ping, Windows services and custom scripts.
  • Website availability monitoring (Building). Check web service availability alongside device health.
  • Agent network discovery (Building). Find network devices from a managed endpoint.
  • SNMP monitoring (Building). Monitor network devices by class with stored samples and export.
  • Application update discovery (Building). Identify installed application versions and available updates.
  • Application update policies (Building). Choose whether to leave an application alone, update it or install and maintain it.
  • Explicit patch assignment (Building). Apply patching only after a device receives a patch policy.
  • Operating system patching (Building). Scan, approve and install system updates with visible restart and result states.
  • Patch failures open tickets (Building). A failed patch opens a ticket with the patch history attached.
  • Patch risk guidance (Building). Review advisory information about update stability before approving installation.
  • Reboot deferral (Building). Let device users choose when to restart after updates.
  • Update restart prompts (Building). Ask users to restart when an update requires it.
  • Verified patch outcomes (Building). Distinguish installed updates, incomplete attempts and results that could not be confirmed.
  • Windows Update policies (Building). Scan and install Windows updates per device under a policy.
  • Machine-readable documentation (Building). Make product guidance and API definitions discoverable by software tools.
  • Operational guides (Building). Find instructions for installation, upgrades, backup and recovery.
  • Proven database schema (Building). The full database schema is rebuilt from empty and checked against production.
  • Reliable upgrades (Building). An upgrade is complete only when every expected change is confirmed applied.
  • Device policies (Building). Set antivirus, monitoring, jobs and scripts per policy.
  • Inherited policies (Building). Apply settings from customer groups down to individual devices.
  • Policy revisions (Building). Review policy changes, publish revisions and restore an earlier revision.
  • Dependency security floors (Building). Prevent dependency and deployment references from falling below required security fixes.
  • Installer integrity (Building). Verify downloaded installer bytes against the expected digest before execution.
  • Known native libraries (Building). Every bundled native library is identified by name and version.
  • Locked dependencies (Building). Every project pins its dependencies so builds are repeatable.
  • No third-party scripts on sign-in (Building). Sign-in pages load no script or style from another origin.
  • Resolved dependency checks (Building). Check installed dependency versions for remaining vulnerable copies after an update.
  • Running build identity (Building). Identify the source revision behind a running release.
  • Scans match what ships (Building). Security scans measure the exact set of components in the released build.
  • Verified downloads on devices (Building). Everything the agent downloads and runs is verified first.
  • Consent before remote access (Shipped; Windows only). The signed-in user can be asked to approve remote access first, following your policy. Release notes →
  • Remote control (Shipped). Take control of a device screen with mouse and keyboard from the console. Release notes →
  • Remote control in the browser (Shipped; beta). Control a device from a browser without installing the remote access app. Release notes →
  • Remote registry editor (Shipped). Read and change the Windows registry on a device without a full remote session. Release notes →
  • Connection reason shown to the user (Building). The person at the device sees why a technician is connecting.
  • Desktop assist (Building). Help a user on their own screen with a lightweight support session.
  • Managed remote support settings (Building). Remote support is installed and configured centrally for each device.
  • Remote file browser (Building). Browse, upload and download files on a device.
  • Remote session relay (Building). A relay connects technician and device for remote sessions when they cannot reach each other directly.
  • Screen sharing helper (Building). A small helper lets the user share a screen with a technician.
  • Windows remote tools (Building). Remote shell, event log, task manager and file tools for Windows devices.
  • Reports and dashboards (Building). Reports and dashboards across customers, sites and tags.
  • Command signing (Building). Sensitive commands are signed before a device will run them.
  • Script secrets (Building). Provide scripts with managed secrets without embedding them in script text.
  • Script tasks (Building). Run PowerShell and shell scripts on devices.
  • Reusable service processes (Building). Reuse process templates while retaining control over local customizations.
  • Separate ticket conversations (Building). Coordinate with a supplier on a ticket without exposing the client conversation.
  • Text message to ticket (Building). A text message from a customer opens a ticket.
  • Ticket parts and invoicing (Building). Carry parts used on a service ticket into its invoice.
  • Ticket subtasks (Building). Create linked child tickets for a request with multiple steps.
  • Two-factor sign-in (Shipped). Technician sign-in is protected by a second factor and escalating lockouts. Release notes →
  • Access reviews (Building). Review who can reach each customer workspace and confirm or remove access on a regular cycle.
  • Deployment-specific credentials (Building). Use credentials supplied for each deployment instead of shared source defaults.
  • Missing-secret refusal (Building). Refuse credential checks when their required secret is absent.
  • Passkeys (Building). Sign in with a passkey as a second factor instead of a code.
  • Protected credential reveal (Building). Local administrator passwords and disk recovery keys are shown only to users with elevated access.
  • Roles and permissions (Building). Give each technician only the access their role needs.
  • Single sign-on (Building). Technicians sign in with their organization's identity provider.
  • Software deployment (Shipped). Upload installers and deploy them to Windows devices, tracking each device's install status. Release notes →
  • Software installation prerequisites (Building). Identify supported installation methods and explain missing prerequisites.
  • Software inventory and updates (Building). Use supported system tools to manage installed software across operating systems.
  • Assisted script drafting (Building). Draft a script for a technician to inspect before execution.
  • Assisted ticket replies (Building). Prepare a draft response for a technician to review before sending.
  • Customer AI settings (Building). Choose assistance settings separately for each customer.
  • Expired command cleanup (Building). Commands that time out are closed with a recorded outcome on the command and its case.
  • Installation outcome checks (Building). Confirm that installed software connects to its intended service before reporting success.
  • Verified fixes (Building). A case closes only after later observations confirm the device recovered.

Shipped

Recently shipped.

Improvements now running on production. This list updates itself when a release reaches production.

What the numbers mean. Each entry is tied to the release version that carries it, and it is listed only once production is running that version. The month shown is the month that release reached production. Nothing here is written ahead of a deploy.

Design partners

Help shape what ships next.

The items marked Planned and Exploring are where operator input changes the most. Bring a real workflow, show us where it breaks down, and we will tell you what we decided and why. Your feedback informs priorities; it does not guarantee a feature or a date.

See where it stands for your workflow.

We will walk through what is available today, what is still on the roadmap, and whether an evaluation makes sense.

This roadmap shows direction and current status, not delivery commitments. An item is called Shipped only when it is running on production.