Link each customer once, then run everything from there
Revo is an MSP platform built from modules: a service desk, RMM, IT documentation, Microsoft 365 management and security. Use one beside the tools you already have, or all of them on the same customers, devices and people.
Illustrative: a fictional customer with every module on
Modules
Five modules. Turn on the ones you need
Each module works on its own, beside the tools you already run, or with the others. Turn one off and it leaves nothing behind in the app.
RevoPSA
Service desk and billing
Tickets with SLAs, a dispatch schedule, timesheets and projects, then contracts, estimates and monthly billing runs from the time your team logged.
- Tickets, SLA policies and satisfaction ratings
- Schedule, timesheets and projects
- Contracts, prepaid hours and billing runs
- Estimates, purchase orders, leads and a catalogue
- Tickets, estimates and invoices in the customer portal
RevoRMM
Monitoring, patching and scripts
Policies per customer, site and device decide what's monitored and patched. Alerts can open tickets, and Windows 11 moves to the version you approve.
- Monitors and alerts, with maintenance mode
- Patching and Windows upgrades in maintenance windows
- A script library with typed parameters and schedules
- Processes, services and event logs without remoting in
- Network discovery and firewall configuration backups
RevoDocs
IT documentation
Pages with versions and attachments, structured records with typed fields, and your team's own knowledge base, linked to the customer's devices, contacts and sites.
- Pages in folders, with versions and attachments
- Structured records with typed fields
- A knowledge base for your team
- Pages shared to the customer portal
RevoCloud
Microsoft 365 management
Every customer's tenant on one page: users, groups, mailboxes, licences, admins and policies. Turn on management access to act on them.
- Users, groups, mailboxes, licences and admins
- Block sign-in, reset passwords, change licences and groups
- Offboarding with a preview of every change
- A PowerShell console on the tenant
- The tenant's policies and Secure Score
RevoSecure
Security posture
Findings from devices, Microsoft 365 and external assessments, ranked with CISA KEV and EPSS and measured against the ideal state you set for each customer.
- Findings, vulnerabilities and an action plan
- Attack surface and dark web checks
- Ideal state, compliance and scores
- Security alerts and signed agent fixes
- Security reports in your brand
RevoCore
Each customer lives once
Customers, sites, contacts, domains and devices are kept once, with each customer's links to Microsoft 365 and ThreatLocker. Every module works from that record, so turning another one on never means mapping customers or consenting to Microsoft 365 again.
- Your other tools
- Alerts open tickets in RevoPSA, or in ConnectWise PSA, HaloPSA, Syncro or Atera if that's where your team works.
- Automations
- A ticket, alert, finding, device event, incoming email or schedule starts a rule. It can open a ticket, run an approved script, post to Teams or Slack, or send a text.
- Credential vault
- Each secret encrypted on its own. A person reveals one with a reason and a recent two-factor check, a token only with its own scope, and every reveal is logged.
- Roles
- Preset or custom roles, and technicians limited to the customers they look after.
- Customer portal
- One portal per customer, showing what you choose to share from each module.
- Ask AI
- Ask about a customer from the page you're on. Anything it would change becomes a request that a person approves.
RevoAgent
One agent, and nothing runs unsigned
RevoAgent serves every module from one install on Windows, macOS and Linux. It runs only signed jobs, and only the kinds that both the customer's modules and the device's own local policy allow.
A script runs only after one of your approvers signs that exact version with a passkey, and the agent checks the signature itself. After that, guardrails rather than approval queues:
- From 10 devices, you type the script's name to confirm
- Technicians run a script on up to 25 devices at a time
- Pause scripts stops every new run at once
- Unusually heavy use pauses scripts and alerts the owners
API first
Everything in Revo is an API call
Every action in the app is a documented API operation with the same permission checks. Your scripts, your own tools and AI agents work with Revo the way your team does.
- Service keys and personal tokens, each with scopes
- Idempotency keys, so a retried write doesn't run twice
- Signed webhooks when things change
- The revo command line, and an MCP server for AI agents
# Sign in, then approve it in the browser $ revo login --url https://revo.example.com # Overdue tickets across every customer, as JSON $ revo api GET /psa/tickets state=overdue # Find any operation the API offers $ revo ops scripts # Revo as tools for an AI agent, read-only by default $ revo mcp
Platform security
The same protection under every module
Revo holds your customers' credentials, devices and tenants, so these don't depend on which modules you use.
- Isolation
- Each MSP's data is separated in the application and by forced row-level security in the database, and again per customer for portal users and limited technicians.
- Sign-in
- Two-factor sign-in, passkeys to approve scripts, and a recent two-factor check before a person reveals a credential.
- Encryption
- Secrets and integration credentials are encrypted at rest with AES-256-GCM.
- Audit log
- Sign-ins, approvals, credential reveals, AI actions and support access are recorded in a log that can't be edited.
- Signed agent
- Signed jobs and signed self-updates, and a local policy on each device that can refuse job types.
- Outbound requests
- Addresses your team enters are fetched through a guarded client, so they can't reach internal systems.
Early access
Revo is in private alpha
We're opening it to a few MSPs at a time. Leave your work email and we'll write when there's room.