Its scalability is good. I would rate it an eight out of ten in terms of scalability.

I found Device42 pretty easy to scale up, so its scalability is a ten out of ten.

You can scale it where you need it and even do a satellite setup. For example, suppose you had some servers in California, and you had to collect data from California, or you had a hot site in California. In that case, you could put a note on Device42 that collects your device information in California, and it could send the information to wherever your base is.

For example, if your base was on the East Coast, DC, then you could send all that information, and it doesn't have to be connected 24/7 to the internet. It can send information whenever you schedule.

Once you're reconnected to the internet, you'll receive the data, so that was an excellent Device42 feature that allowed for more scalability. You could also add more notes to ensure you didn't get a lag, or you could mitigate that lag.

Device42 is fully scalable.

Scalability wasn't an issue.

Scalability-wise, there could be improvements. Currently, the scalability is only upwards. You have to increase the resources that you apply to it. You can't have multiple instances of the same thing. You can't scale horizontally; it's just vertical.

The tool’s scalability is very nice. We must speak to the vendor, and they will send a new key code. We can install it and start working. It's easy to scale the product.

The scalability is very capable. There are a lot of things that you can do with this solution. I'm hoping that as our configuration matures that we can take more advantage of them.

We have 15 users who are segmented into users of the application. There are administrators of the application and super admin accounts for the management of the back-end. We have two super admins, three administrators, and then all of the rest are users.

A big push will be when we build our new data center, then that will be hopefully set from the ground up when we redo our network. The solution is not being used too extensively right now. The infrastructure upgrade network is the main upgrade component. You have to start with the networking in Device42, so I'm hoping it will give us a fresh slate to do everything properly instead of mismatching everything in there. We definitely have plans to use the software fully and to fully utilize all of its functionality. However, we're still in the early phases.

We have a lot of devices with a modern database architecture. It does not have a problem handling our data. 

Many people from my company are now working with Device42. They switched over from the old tool to Device42. There are about 300 people working at the company.

The whole technical department is using Device42 (120 users). Technical department, at our company, means we have infrastructure, network, application management, and application support teams along with an internal IT department. Even development uses this tool to see devices and clusters.

I would assume it would be fine for all of our future needs. But we're a relatively small organization, so I don't think we're ever going to really stress it.

It is scalable, though it all depends on the size of the database. If that grows, you have more room to read in more devices.

We are looking at some long-term goals of other teams using it. We are looking at having the network team map out everything, then letting them have access to go in and look at all their inventory. However, for now, we have started the push to the cloud, which is about mapping all the dependencies into the topology of the network, such as what talks to what ports so nothing gets left behind, firewalls, dependencies, etc. This is all flushed out ahead of time.

Device42 is currently hitting about half of our environment/LOBs, which is approximately 4000 servers. From what I've heard, there are plans to extend it to the rest.

There are two to three system admins who I have handed the project over to for day-to-day operations. The project that I was on, which was on hold, has picked back up, so I'm on it full-time. Therefore, I have been training other people to take over Device42. Right now, I'm in more of a training role than an active user of it.

The scalability is good. Depending on the number of servers that you want to restore, you can scale up or down. You can have one or multiple Remote Collectors for more stability and load balancing.

We have three different customers using Device42, and I have supported seven to eight customers until now. One of our customers, they are doing their plans in waves: wave one, two, and three. In wave one, they managed to discover almost 500 servers. In their second wave, they helped manage 400 servers. In wave three, they are now managing 500 to 600 servers.

It's scalable. It all depends on how a customer purchases its license. Overall, it's able to handle the capacity.

It's being used in just one environment. It's not deployed across multiple environments. There are four to five admins who use this solution. 

The scalability is pretty good. It's possible to have many devices in Device42, but we can see some limits. For a very large organization, it would be a little bit difficult to use Device42 because it's a single server. It's not possible to have scalability by load-balancing the load onto different servers. That's one of the reasons why we decided to have four different implementations, to be sure that we do not have everything on the same server.

We have more than 1,000 users in Device42 and most of them use it for the password management. Some users are using it for audit purposes, for asset management, and to be able to provide reports to senior management.

We have deployed Device42 everywhere. If our organization does not expand the number of devices, we won't need to extend Device42.

It is very scalable and have had no issues. We are running the device across multiple divisions, organizations, and regions across the globe. Device42 is everywhere in our company. There are 30 to 40 users, e.g., help desk administrators and auditors. We will potentially be using it for vendor management down the road. Also, the DevOps teams is using it for information.

In the beginning, the solution did not reduce the time spent managing IT assets since we didn't do any management. There was a lot of turnover of teams with every team doing it differently. Therefore, we had to focus a lot on it. Now, it's part of the day-to-day management.

We haven't tried to scale it. We use the solution across multiple locations, on-premises and in the cloud, and for multiple teams and organizational units. The number of end-users who access the Device42 dashboard in our organization is about 20.

Technically, the solution scales. The only issue I have with this is that it needs various remote connectors to get as much information as you need. Depending on the number of assets, you can just add connectors and you're good to go.

Nmap is the de facto standard. But Nmap is still slow. If you wanted to look at 10,000 different IP addresses and get a little bit of information from each of them, it would take a little while, unless you multi-fitted them. There's a new tool out called Masscan. I've taken it and written a middleware so that the Device42 stuff uses Masscan now. That would be something that would really help Device42 scale much faster, in the discovery-specific portion of its tool.

For what we're doing, the scalability hasn't been an issue. We knew a lot of people were going to be using it. We have people from all over the world — from three different places in India, seven different places in the United States, and a bunch of people in the European Union —  working on this at the same time, 24 hours a day, seven days a week.

We haven't reached the solution's limits. The solution's collectors give it very good scalability because you can separate the manager from the collectors.

We continue to check its capabilities. We plan to expand to another, small data center, a location with, say, 10 racks, with a rack dedicated to communications — such as a firewall, router, and switches — and the rest of the racks for servers. Expansion depends on the plans of our regional offices in other countries. The idea is to test if we can install info-collectors in these offices to give us information about their assets. We are planning these kinds of projects. Maybe we can expand our usage in this way.

From what I understand, it's very scalable. It's very easy to scale up on it as well. But it's more the app team that would know that kind of stuff. I deal more with the DCIM stuff.

It's being used very extensively in our company. As I said, we've got 77 offices globally and about half of them have been populated fully in Device42. The rest still need to be audited, so we are going to be increasing the usage of it. It just takes a bit of time.

My boss loves the fact that he can run API commands and get information that way. He's a huge API-guy, so he loves it.

I don't deal with the scalability of it. I deal with procurement mostly. But my colleagues say it's easy to work with and they don't have difficulty with this. 

I think it can be a bit tricky when they need to add many assets. We may need to do some internal upgrades when it comes to serial number scanning of small items for replacement, but that's not related to the tool. In the end, all this information will go into the tool and it will help us to track things better.