ReadyAPI is a scalable tool. In terms of performance testing, you can scale it, but scaling it requires a different license. For example, the basic license allows up to one hundred users, while the advanced license allows up to five thousand users, but if you want to scale to more users, you have to purchase another license. ReadyAPI has different modules of license for performance testing, so you can scale it up based on the number of users you require.

The solution is scalable. Whatever scripts are created, it is pretty easy to upgrade them based on any schema changes. If there are any scenarios that are to be updated, it is easy when compared to other solutions that are skill-based tools.

We have 12 people who are using ReadyAPI and we do not plan to add any more to the team.

The solution is fairly scalable.

I think there is a lot of improvement required from the scalability point of view. 

Anywhere between 20-50 people use the solution at the moment, but that can go up to around 100 users. 

The solution is scalable. 

The solution scales well.

There were codes and services that were very complex or lengthy, so we created test suites for one code, which made everything easier.

I'd use the tool, as well as the test team. We'd do all kinds of testing, and it could handle it all. 

Between 200 and 300 people are using the solution. Almost all of the developers would use it for testing. 

ReadyAPI is scalable. At one point in time, we had eight people working with the product. Each of us would add our test and add to our repository. We also added it to our nightly run, on the weekly and daily runs.

Our system is quite scalable. We have many things that handle auto-scaling groups, which scales quite well. We have quite a bit of devices, millions of devices, and each time it scales very well. There's no problem with it. We have never had problems due to an area that didn't allow us to scale. 

There may be 50 million devices talking to our cloud. It's quite sizeable. 

I'm not sure if there are plans to increase usage. 

We are currently servicing ourselves and our customers well. I'm not aware of any plans to increase. I'm not aware of any growth plans.

It is scalable. For example, if I'm running a UI test case, it can take me a minimum of 1 or 2 minutes or 45 seconds to 2 to 3 hours, depending upon the complexity of the workflow. If I want to test the same in API and I have defined my framework and everything, I could do it in 30 seconds or 40 seconds.

It is a scalable solution. There are currently about six users in our organization. 

It is a desktop application, so technical scalability is not applicable. 

The scalability of the solution is good. I think about 150 testers in our organization use ReadyAPI. About 250 to 300 of our developers use the free version, SoapUI, to do basic API testing.

The solution is scalable. Approximately 50 people use this solution in our company.

Right now, I'm the only person using the solution. I'm not sure how scalable it is.

ReadyAPI is not as scalable as other solutions, such as Karate. More resources, especially in terms of memory, are required for the same amount of data.

The scale does not only refer to the number of users. It concerns the applications and how often they make calls to different servers or mocks. 

It is a scalable solution. However, it is not so flexible. If multiple team members are working together, they have to frequently pull and push the code to sync with the single team and take the latest code, which other team members develop. For better functionality, we have to go every time to Visual Studio.

Multiple teams are using the solution right now. On my team, we have seven to eight people using it. I'm unaware of how many people are using it from the client side. Users are a mix of automation testers and manual functional testers. 

This solution is best suited for medium to large-sized companies. However, the use of the solution is not dependent on the company size, it's dependent on the volume of data or the APIs that are being used. A small company can work on a solution that involves a lot of APIs

We haven't scaled it. We have approximately nine people using this solution in our organization.

The scalability is good. We have eight people in the IT department who use this product. There are four in development and another four in the QA team.

This is a scalable solution. 

The scalability is okay.

It is a scalable solution.

We have between twenty-five and thirty people who use this solution.

I think scaling up and down is possible. There are 10 users of this solution in my team but there would be many others throughout the company. We only use the solution for certain projects so it's not used on a daily basis. 

I have found ReadyAPI scalable.

The scalability of ReadyAPI is good. However, every one of the 20 QA team members uses it independently.

The solution has met our requirements and appears to be scalable.

Scaling this solution is quite easy. I had some problems migrating to the cloud, with Java, but overall it is easy.

We have about twenty users for this solution, although it depends on the project. Some projects have fewer users.

If you are thinking about huge numbers of APIs that need to be maintained and executed, this product can be scalable to large amounts. We can create multiple projects, maintain them and group them according to what suits our test skills. All this comes with a beautified structure from whatever SoapUI open source we have. They carry all the advantages of open source and additionally they are non-scripting and generate reports after test events. All these things as well as custom reporting if you need that, so it's very comfortable for scaling.

We need to use ReadyAPI for scalability, because if you go to RestAssured and are writing a framework there, it is good for a hundred APIs. But if you go for a thousand APIs you'll need to have someone to maintain the code completely and to fix it whenever it's failing. You need to rewrite the frameworks and then if your API is getting updated you need to modify all this stuff, but here the API is so good.

Scalability is actually another really useful and convenient function of this software. It has the ability to pass tests on different machines. You need to have a kind of server on a machine. Then you can instal clients from the other machines and then the application does tests on different machines. It's really convenient as well.

It's used on a daily basis.