Kaseya Traverse Reviews

If I want to automate the management and maintenance of my server automatically, this product is a good use case for that.

The automation workflow is always going to be the most valuable feature. Automating processes is crucial for me, so the automation part stands out.

Improvement is needed in making it cheaper, of course. I am not emphasizing making it cheaper, however, it should be more competitive with other products. 

The product itself is very good and helpful for me as a customer. The issue always is the price, as we cannot beat most of our competitors on pricing alone. If a product is just nice to have, not essential like an antivirus, if it's not really competitive with pricing, we cannot sell it.

I think I have used it for five years.

The solution is pretty stable.

Every device is included and can scale.

Support-wise, it is very good. In terms of response time, the response is quite fast and very good, which makes me very satisfied with the response time. However, the issue lies in the adequacy of the responses to my questions, which are usually not up to par. 

Positive

It's very simple to set up. Most people are very capable of installing the application or the server without encountering any issues with Kaseya Server.

In the current market, we are talking about Managing Gen, Management Endpoint Central, and then endpoints from, unfortunately, I have forgotten the product name, but it is endpoints. Following that, there is Ivanti, and then there is another product I have also forgotten.

I'd rate the solution seven out of ten. 

As Kaseya sellers, we always promote Kaseya first. If the price is more competitive, then I think it will be better. It's a main pain point for us as a reseller. It always comes down to the price. 

In my company, we use Kaseya Traverse for network monitoring.

The most valuable features of the solution are its processing capabilities and its ability to monitor multiple different devices giving you capabilities to scale from your networks, access points, switches, files, applications, servers, fiber availability, uptime, downtime, and you can see when and not load shedding occurs, having UPS or invoice installed onto the module while giving a customer full visibility in terms of a customer dashboard and everything. Kaseya Traverse gives customers a clear view of their IT stack. From a service provider perspective, troubleshooting effectively and getting to the problem immediately rather than having customers log tickets with multiple different providers and slots to resolve their problem.

In terms of the integration and everything, our company would like Kaseya Traverse to integrate with our PSA system and merge or automate what we call false positives, making it more of a threshold than needing to raise an actual ticket to deal with real problems, which can cut off a lot of noise the system goes through. Our company is busy with the solution's integration part, and we wanted an update on the solution that can help us.

The tool needs to have some AI capabilities, which it lacks currently. I don't have a technical wish list like technical managers since the product manager looks after the product. From a wish list perspective, our company just wants seamless integration to cut out the noise by merging false positives since the system has the capability.

I have been using Kaseya Traverse for two years. The last update that we had in our company failed, so we are busy testing something at the moment.

It is a pretty stable solution. Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution an eight out of ten.

In my company, 25 engineers use the solution daily. We cater to around 450 of our customers. The customers can view their dashboards, allowing them to see their central reports. If we include Kaseya's engineers, there are 40 engineers. All the engineers use it to provide the customer with a system demo or to troubleshoot from a technical ability perspective or the customer themselves. The total number of people using the solution is around 500 people.

I rate the technical support a nine out of ten.

Positive

I use PRTG. We use PRTG for native monitoring, specifically, along with SolarWinds N-able.

The initial setup of Kaseya Traverse was straightforward since one can do it with a DGE that you load the tool onto.

The solution is deployed on-premises.

Deploying a DGE or putting it on a customer's server or desktop takes fifteen minutes, and that could be a Raspberry Pi server, or a desktop that runs twenty-four hours seven days a week, collecting data via SNMP over time.

The pricing of the product depends on what our customer pays. The solution's pricing varies from 150 ZAR at endpoints to 750 ZAR at endpoints because it's part of the monitoring tools we use for our solution. The price depends on whether you are monitoring different applications, especially in bulk, and depends on what you're doing. If you're monitoring one endpoint, it will cost you 150 ZAR.

It is a reasonably priced product compared to its competitors, and when considering the money you pay for the functionalities you get in the product.

My company did evaluate other products but chose Kaseya Traverse due to the full set of integration we got from it, allowing for seamless integration into the whole system. Kaseya Traverse's offer was a compelling one to go within everything one suite and integrate into everything else.

Around 40 engineers are involved in the maintenance of the solution in something called vCIO, which is like a continuous improvement from a strategy level. The engineers would take the metrics you get off the system, pull the reports, and delve deeper to know about load shedding, what causes the packet loss, and what causes the internet to drop.

The integration capabilities are not working how we want it to work in our company.

Overall, I rate the solution an eight out of ten.

Generally, it is used for monitoring.

It's a simple and humble tool.

It doesn't have a CMDB, which is a basic one. It didn't have two or three other features which we were hunting for. Also, the Correlation feature was missing because it did not have CMDB. The reporting was not that great as well. The reporting was very, very shoddy and very basic. Additionally, Dashboards and Central Protection were an issue. Also, database monitoring was not there. Even though they said that it was there at an additional cost, that tool was very basic. We couldn't have device configuration backup also. It was not part of it.

Now every system, such as monitoring systems or any system for that matter, requires high availability, which means that by design, that system has a failover mechanism. When there are issues identified, there has to be a quick response and then a resolution. Kaseya Traverse had none of this. We started realizing this over a period of time, and very specifically when it reached the state where the version and revision updates were not done.

We started facing very, very huge problems. We were using it for a very basic purpose. So when it happened that we had to do the update, every time we raised the issue with Kaseya Traverse, they would say that you needed to update, and only then will the issue be addressed, multiple issues, We said, okay, go ahead. We also gave them a different cloud server, our server. They created an image of it, and they promised that everything would go smoother. The moment they upgraded and started migrating, every service failed. For a period, we had a blackout, and then it started coming up.

They could not restore the service completely. For every issue we were facing, whatever issues we had, which they said after version update or upgrade, everything would get sorted out, none of them got sorted out. Even the normal functions which were working in the preview version did not work, and they said everything had to go to the engineering team, and they needed to come back.

We had a very, very, very horrible time, and we regret it. First of all, having agreed to an upgrade because by upgrading, neither the earlier issues, which they said would get resolved by upgrading, got resolved, nor the functions which were already working came up, nor did we have any new benefits. We decided and concluded that we would move away from Kaseya Traverse.

There is no one person whom we can go to. We were taken up to be a chief operating officer, or maybe the chief delivery officer and head of design something, nice people, but that didn't help us. Many, many, many, many, many issues bogged us down. In fact, we had to pay a penalty to our customers for not monitoring and for having issues.

I have been using Kaseya Traverse for over ten years as an end user. Currently, we are using the latest version.

If it works, it works. There is no bad or major downtime. The downtime that we experienced was when we did the upgrade, and otherwise, we used to have issues cropping up with functionality.

In our organization, we had 10,000 devices.

I would rate the scalability of this solution a two or three out of ten.

For everything, they will say it is chargeable, and they will never respond. When I say a response, somebody's picking up a ticket and coming on a call, all of them are fine. Though it took time, that was fine. But permanent resolution per se, whether it is a design issue, whether it is an instant issue, a platform issue, or basic things, they would never ever get it resolved once installed. It was all backgrounds and managing the show.

As for the technical support of this solution, I would rate the people a six or seven. The people are good. Their knowledge is also good. But when the product is unstable, they are dependent on engineering, and the backend team is very high. Then the rating, as a product, would be two or three out of ten.

Negative

The solution was deployed on the cloud. However, on you can the cloud, we did not have high availability. If, for instance, the other feature, what you would have asked for was updates and upgrades. That's something that is very critical, and it was not there.

As for maintenance, the regular management functionalities were done by us. Otherwise, I don't think we did any maintenance. We did onboarding and offboarding. It was one of the complex solutions, but that was done by us. Otherwise, any application troubleshooting and all they used to do. So as for maintenance, there was nothing.

Maintenance required, maybe about 30 engineers. People come on different shifts. There could be people for databases, messaging, operating systems, and networks. So different sets of people, maybe about 30, are using it to administer and manage the infrastructure.

It is quite expensive and very basic.

I would not recommend this solution. I would say if somebody doesn't have any great expectations out of this, and they are using it for the first time and want to monitor it, I will say you can use it. But it is also costly. We were paying close to about ten dollars or $12, including network configuration management or something.

We were using it for our customers to monitor and manage our own customer infrastructure. We also were end users for about 600 or 700 devices. But the rest were all Kaseya Traverse tools our customers.

Overall, I would rate the product a two or three out of ten.

We’re an MSP. We use the solution for RMM and PSA tools.

The software does what it needs to do. It has all the necessary features we utilize to support our customers. The tool has all the features we require. The remote support and data collection features are great. We can get some nice reports from the system if we know how to manipulate it. We can get inventory reports.

Reporting is a bit difficult. It’s very cumbersome to set up new reports.

I have been using the solution for two years.

I rate the product’s stability a ten out of ten.

The tool’s scalability is fine. I don’t see any issues in scalability. I rate the scalability an eight or nine out of ten. We support 4500 users with the product.

The support is not so great. We've been struggling with some integration issues between some of the products, and it's been ongoing for nearly two years. The support team must improve the response time and shorten the support cycle.

Neutral

My systems manager did most of the installation. He did not have any concerns about it. The maintenance is not too bad. We do not have any concerns regarding the maintenance. The product is cloud-based.

The solution is a good investment. The solution reduces the time for support. We support most of our customers remotely. We do not have to send an engineer to the client.

The solution is not cheap, but it is not too expensive. We pay an annual license fee. There are no additional fees associated with the product.

It's a good product. The support could be improved. Overall, I rate the solution an eight out of ten.

Our company uses the solution to provide network monitoring and configuration management for our customers.

For some customers, we also provide monitoring for their entire data centers including storage, hypervisors, and the cloud environment. 

For another set of customers, we run links and provide link monitoring only. 

The solution covers all monitoring aspects and components from the network , server, and application cloud. 

Most of the features are pretty good and the solution is user friendly. 

Reporting is tedious and not organized in the way customers expect. Development is needed for reporting because it is almost nonexistent. 

Workflows and AI are missing from the solution. 

I have been using the solution for four years. 

The solution is stable with no issues. Once it is configured, there are no challenges. Any bugs are fixed with patches applied by Kaseya. 

I rate stability a nine out of ten. 

The solution is scalable and we currently have 10,000 devices that use it. 

Technical support is the worst. Responses are bad because support does not understand the priority of a customer's requirement. A customer uses the NMS tool to look after availability first and then performance of business services. The support team does not understand this workflow so responses are not good. 

In most cases, our tickets have been open for more than one year without resolutions. 

I do not even want to rate support because it is so bad. I would rate support a zero if given the option. 

Negative

The setup is easy so I rate it a seven out of ten. 

We implement the solution for customers. It takes 30 minutes to configure and deploy. One person can handle two or three deployments at a time. 

We have a template for new customers that includes device configuration. Any new discovery will grab the template by default and align to alert the server automatically. The solution integrates with Kaseya Vorex which we use as our professional services automation tool for ticketing purposes. All monitoring alerts are converted into a ticket in the Vorex portal. 

On a monthly basis, we handle database maintenance and upgrades. 

Our company is able to propose the solution as a service so our up-front investment is less. 

We have built a team for supporting the solution on the operational front. Unless there are software issues, we don't even need to engage with development. We save on implementation, management, and support because our team handles everything. 

Our monitoring and management services are bundled and provide us with a good profit.

The pricing model is pretty simple and all features are included in the base price. It costs about 5,000 rupees per device. The only add-on is network configuration management. 

In comparison to other products, I rate pricing a nine out of ten. 

We explored Zabbix along with the solution. Zabbix is not a bad product but is open source so does not have the level of support we need. 

In comparison to other OEM tools, the solution has a simple pricing model that includes all modules and features in one product. That is a benefit to us. 

Frankly, I am in favor of the solution but it lacks development and support. This is a major concern because customers are looking for good support. When we meet with customers, they first talk technical and then ask about support. Pricing discussions come later. 

I cannot recommend the solution because support is unsatisfactory. 

I rate the solution a seven out of ten. 

We use this solution for infrastructure monitoring.

Most which are available

Kaseya Traverse can improve by adding a Service Map to help us create a configuration management database (CMDB), this would be helpful for us. Additionally, competitors have been integrating a Network Visualizer as part of their offering and this is something that would be a good benefit to have in this solution.

Our team has been using Kaseya Traverse for approximately nine years.

There have not been any problems worth noting. However, there've been issues related sql database vulnerability which never came to us proactively and resolution is dodging.

The solution is scalable, to our current requirement. However, without incorporating service map / CMDB / visualizer, Traverse cannot take us any further.

The support for the solution needs some improvement. In my experience, the response time to answer a query is slow.

The setup is not complex.

Personally, I rate Kaseya Traverse a seven out of ten.

We use Kaseya Traverse as our RMM system. We connect it to customers' end points to manage their antivirus, update patching and to perform network monitoring.

In terms of most valuable features, we are happy with everything so far. Maybe in a year's time I'll have a different opinion on what can change, what can be better, but for now it's the perfect solution. It took us quite a long time to find a solution. We benchmarked it against a lot of other suppliers, as well as our current supplier, and they were more favorable with the sustainability functionality and support that they could give us.

In terms of what could be improved, we are innovating all the time, as well as having a look at different avenues so that the strategy follows the structure. 

I think the software is still a little bit too new to actually fully asses what it has.

As things change and as new products come in, we look at different plugins and all those things. The reason why we're using Kaseya is because it's a full solution. It's one supplier, it's plugged into a lot of things like a customer documentation system. It keeps all their setups, documents, all those types of things and it just integrates with a lot of the other tools that the MSPs use. It is very user friendly.

We have been using Kaseya Traverse since the end of November.

Kaseya Traverse is a very stable solution and very sustainable in terms of what the market wants, what is out there, price-wise and functionality features. They're quite competitive and they are always innovating.

We have about 40 people that are using it internally to monitor, and about 3,500 end points to manage in Bahrain. 

We just signed a very big customer now as well, with over 1,100 users. We manage network devices and important security, as well as touching and monitoring updates. I'm quite impressed with it's GMS system, which is their ticketing system. Their functionality and everything is pretty new. I do have helpdesk managers, support managers, and installation managers that work on it more than I do. So I've been given a high level overview and demonstration on it. I haven't really had the time to work on it myself yet. I've been busy with more strategic things than the operation side.

We moved from SolarWinds because it wasn't giving us the support that we needed. Some of SolarWinds' helpdesk functionality was archaic. It didn't work with our new strategy that we wanted to go to market, in terms of monitoring and managing our customer's network equipment and their endpoints. It was time for a change on a lot of other systems, and price-wise Kaseya Traverse was very competitive.

The deployment support was pretty straightforward. They really come to the party in terms of assisting us with a lot of things that we have needed help with and so forth.

The licensing for Kaseya is on a monthly basis.

We manage the platform and they obviously look after the back end, the software itself. We get training and briefing on the actual platforms that are used. Obviously it's license is based per agent, depending on the plugins that you're putting onto it. Clients who would have an antivirus or would have an OS patching, all those types of things, impact price. And then you have the RN install to connect to the user's end device.

We are very happy with the pricing. They've given us a savings.

At the moment, on a scale of one to ten, I'll rate Kaseya Traverse between a seven and an eight. I've seen it's functionality and everything. So when I get some more time to get into some of the other features that are available and its functionality, then I'll have a better idea. But I do know about the current functionality that we are getting versus what Kaseya Traverse BME and all the other features could give us. It's a new product, so there are different features and things work different ways.

I would never say something is perfect.

We have 20 - 25 customers.  We primarily use the solution as a monitoring device for, depending on the client, a mix of servers, storage, networking devices, platforms or databases.

Everything is running seamlessly on the solution, to the point where you don't see any gap. 

We've noticed a few bugs as of late. However, this seems to only be in the reporting part of the product. 

The development of the signature or request takes a lot of time. However, the development is very slow at their end. As is the support. This might be why. Everything goes to the product team and lab, even for small requests and even if it makes sense to send it through to the product team instead. 

In any case, they aren't adding any signatures to the devices, and I cannot give the tool to my customers if there isn't the capability to add it to the tool. I can't go to my customer and tell them it isn't possible.

They have not even developed a signature for basic things that are being upgraded, like Exchange 2010. They have not yet added the signature after Exchange 2010 and it's now 2020. That's a serious concern. We are running on Exchange 2019 and Office 365. Now 2019 is not yet being developed. On top of that, with Microsoft HyperV, they are still using the old 2008 signature. That has also not been upgraded anywhere. There are many things that are not developed as per the industry.

When we take any contract from a customer, it is agreed that I will monitor each and every device that they have in their data center. It causes an issue for me when I can't deliver due to some issues on the solution's side. It makes clients unhappy.

I'm facing many support issues with them. I am actually looking for another solution to purchase.

We've been working with the solution for eight to ten years at this point. 

With my most recent experiences on the solution, I can say that it isn't currently stable. There are a lot of glitches and bugs. The reliability just isn't there right now.

The solution is scalable. There is no issue in that sense. There have been recent requirements now, with the onset of COVID in which there are current customer requirements, that are not being developed, however. That's an issue for both us and the clients.

We have about 20 different customers on the solution currently.

Technical support is very, very poor at this time. They don't help and they send you to the wrong people who end up not being in the position to help you. We've been extremely unsatisfied with the level of service they've provided.

The initial setup is very easy. It's not a complex solution to implement.

The pricing is quite competitive. It's actually quite low compared to what else is on the market. They are very affordable.

While we started as a Traverse reseller, we are now only customers, even though we do sell Kaseya products.

We're not overly happy with the level of service we receive from the solution's support.

I'd rate it overall five out of ten. There are many features that could be added to make it much better.