
We moved to Gorelo from HaloPSA and NinjaRMM. Both of those are powerful tools, but we wanted our RMM and PSA in one platform, and Gorelo gave us that. Setting it up didn’t take a specialist or months of configuration, and we didn’t have to give up anything our growing MSP needed to get there. The interface is clean and makes sense, and it feels purpose-built for how an MSP actually works. The agent is light on endpoints. Having tickets, devices, and clients in the same place means my techs aren’t jumping between two systems to work an issue, and onboarding new techs is simpler because there’s one tool to learn. We also pay for one platform instead of two. The team behind it listens to MSP feedback and acts on it. Review collected by and hosted on G2.com.
Gorelo is still a younger platform, and a few areas haven’t caught up yet. SLA tracking is basic and only covers response time, not resolution, which makes us more conservative about the targets we publish to clients. The API has gotten better, but it’s still growing, and we’ve had to work around gaps when connecting Gorelo to our own internal tools. Fuller SLA tracking and a more complete API would make it easier to report to clients and connect Gorelo to the rest of our stack. The good news is the roadmap is public and they’re steadily working through these. Review collected by and hosted on G2.com.