Your RMM and your PSA. One platform.
Monitoring, remote control, service desk, projects, documentation, billing and AI automation in a single system. Nothing gets lost in the handoff between tools, because there is no handoff.
No credit card · No sales call to get started
Powering the world's best IT teams
Most MSPs run their business across four tools that don't talk to each other.
An RMM that sees the device. A PSA that holds the ticket. A remote tool with its own licence. A billing spreadsheet that reconciles the lot at month end.
Every seam between them is somewhere work goes missing: an alert nobody turned into a ticket, time nobody logged, a device nobody billed for.
| Running separate tools | Running Gorelo |
|---|---|
| An alert fires in one system, the ticket lives in another | The alert becomes the ticket, against the same asset |
| Remote access is a separate licence and a separate console | Remote control and file explorer are built in |
| Time logged in one tool, invoiced from another | Billing reads from the system that did the work |
| Client documentation in a wiki nobody updates | Docs sit beside the assets they describe |
| Four vendors, four renewals, four support queues | One platform |
| Integrations you maintain yourself | Nothing to integrate |
Five modules. One record behind all of them.
The service desk, plus everything around it. Alerts, projects, documentation, forms, and the two ways your clients reach you.
- Tickets with conversations, statuses, assignees, time entries and products
- Third-party conversations: a separate email thread on the same ticket, without exposing the client
- Alerts from assets, uptime checks and scripts, convertible to tickets
- Projects with tasks, timelines, checklists and time tracking
- Documents, either free-form guides or structured entries built from forms
- Forms for hardware requests, onboarding and user lifecycle
- Client Portal and Gorelo Messenger, the branded tray app
- Quick and Deep Search across tickets, assets, clients, invoices and documents
- Views and Client Focus to filter everything down to one client
Monitor the estate, reach any machine, and push change to thousands of endpoints from one policy.
- Gorelo Agent on Windows and macOS, deployed by PowerShell, manually, or through ImmyBot, Action1 and NinjaOne
- Gorelo Connect: remote control and file explorer, with consent prompts and an on-screen banner naming the technician
- Live Terminal to run scripts without starting a full session
- Scripts in PowerShell, Command Line and Bash, with the GoreloAction CLI for alerts and custom fields
- Policies that target by tag and distribute checks, plugins and scripts
- Asset tags that group endpoints automatically by client, location, OS, installed apps or your own rules
- Uptime monitoring over ICMP, HTTP and TCP from multiple regions
- Windows patch management with deferrals, deadlines and reboot behaviour
Client documentation that lives beside the assets it describes, and forms your clients fill in themselves.
- Unstructured documents for free-form how-to guides, with formatting, attachments and nested hierarchies
- Structured documents built from question-and-answer templates, so every printer, rack and application is recorded the same way
- Forms for hardware requests, user onboarding and offboarding, and client onboarding
- One-time submission links you can send by email or raise straight from a ticket
- Publish a form to the Client Portal, scoped to one client or open to all
- Reusable checklist templates so onboardings and hardware builds run the same way every time
- Checklists on tickets with owners and due dates
- Documentation shared per contact, so each client sees only their own
Invoicing that reads from the system that did the work, instead of a spreadsheet you rebuild every month.
- Contracts that invoice labour and products on a recurring schedule
- Dynamic Quantities: billable counts pulled automatically from asset tags, contact tags and Pax8 subscriptions, surfaced for approval before they bill
- Approve time entries and products before they reach an invoice
- Labour rates from a billing role base rate times a work type multiplier, so emergency and after-hours work prices itself
- Prorate items for mid-cycle starts and changes
- Pay Now buttons linking to QuickBooks, Xero or your own payment URL
- Send billing email from your own domain
Multi-tenant from the ground up. Clients, locations and contacts are first-class, not custom fields bolted onto a generic CRM.
- Clients, locations and contacts with custom fields, tags and domain tracking
- Contacts sync from Microsoft 365 through CIPP, assigned to the right client automatically
- Approval workflows: tag a contact as an approver and route purchases and access requests to them
- Inbound email matched to the right client by address rules and domains
- Spam view that intercepts suspicious email before it reaches the queue
- Projects with reusable checklist templates for onboarding and hardware builds
- Per-item sharing so each contact sees only their tickets, assets, invoices and documents
And more
The parts that don't need a column of their own, but that you'll use every day.
The handoff is where the margin goes.
Every MSP knows the failure modes. The alert nobody converted into a ticket. The two hours nobody logged because the timer lived in a different tab. The forty endpoints you onboarded in March and started billing for in June.
None of those are discipline problems. They're seam problems, and you can't fix a seam with another integration.
The same ticket, the same timeline, on the desk and on the phone.
Every module can read the others. That's where the functionality comes from.
One platform isn't about fewer logins. It's that billing can see your asset tags, a ticket can see the machine it's about, and a script can change what a policy deploys. None of that is possible across four vendors, however many integrations you wire up.
Billing counts the endpoints for you
Dynamic Quantities watches your asset tags, contact tags and Pax8 subscriptions. Tag a workstation or add a licence and the billable quantity updates itself, then queues for your approval before it bills. Nobody counts endpoints at month end, and nobody discovers in June that March's onboarding was never invoiced.
The admin work, done before you open the ticket.
Not a chatbot bolted to the sidebar. These run against your queue as tickets arrive, and you keep control of the prompts.
Automatic ticket types
The most relevant type assigned from the subject and first inbound comment.
Automatic tagging
Up to three tags applied on arrival, so nobody tags by hand.
Sentiment analysis
Inbound comments scored for negativity, with a group notified when it crosses your threshold.
Ticket summary
A concise rundown of a long timeline, so a reassignment doesn't mean reading forty comments.
Prompt management
Build your own prompts to draft or rephrase replies. Your tone, not a vendor's.
Event and time automation
Assign, notify or act on ticket creation, status changes and unread state.
Expiration alerts
Domains, warranties and contracts raise alerts at thresholds you set.
Scheduled tickets
Recurring work created daily, weekly or monthly with the group and actions preset.
One-click workflows
Canned responses, solve-and-close, and project baselines from a single action.
It fits what you already run.
Keeping your existing remote tool? Splashtop, AnyDesk, TeamViewer and RustDesk work through custom asset fields and launch shortcuts. Already deploying through ImmyBot, Action1 or NinjaOne? The agent installs that way too.
"Having everything in one place with Gorelo has made a huge difference. Before, we constantly had to switch between tools, risked losing tickets, and spent time tracking endpoints manually."
Dylan ProngerHall Computer ServicesOne price. Everything in it.
If $99 a technician sounds like a lot, add up what you pay now for an RMM, a PSA, a remote access licence and somewhere to keep your documentation. This is all four, on one invoice, with no lock-in.
per month, billed yearly
- Service Delivery
- Remote Management
- Documentation
- Billing
- AI & Automation
- Projects
- SSO with Microsoft Entra
- And everything on this page
For larger teams where not everyone is technical. Both sit alongside Full Platform rather than replacing it.
Service and financial workflows without the remote management layer.
Service delivery and remote management for a single client, for co-managed engagements.
The things MSPs ask before they trial.
How long until we see anything?
Deploy the agent to a handful of machines and you'll have monitoring and remote access working the same day. You don't have to migrate anything to evaluate it.
Do we have to move everything at once?
No. Most MSPs start with monitoring on one client, then bring the service desk across once they trust it, then billing last.
What about our existing remote access tool?
Keep it. There's a ScreenConnect integration, and launch shortcuts for Splashtop, AnyDesk, TeamViewer and RustDesk. Gorelo Connect is there so you don't need a separate licence, not to force the issue.
Is it built for MSPs or is it generic IT software?
MSPs. Multi-tenant from the ground up. Clients, locations and contacts are first-class, billing is built around billing someone else for the work, and the Client Portal assumes your clients are not your employees.
Will it work with our accounting package?
Xero and QuickBooks Online both sync clients, invoices, tax rates and payments.
Why is the pricing public?
Because you shouldn't have to sit through a discovery call to find out what something costs. The full price list is on the pricing page, in USD or AUD, monthly or yearly.
Are we locked into a contract?
No. There are no lock-in contracts, and the 30-day trial doesn't need a credit card.
Can we talk to someone first?
Yes, book a demo. But the trial doesn't need one.
See it on your own machines.
Start a trial, deploy the agent to a few assets, and judge it on your own estate rather than a demo environment.