It's very scalable. The solution is built for scalability. I didn't know that we could even move into this sort of API world. I used to think, "We do those tests like this." JMeter provides its own sort of capability, but with BlazeMeter, there's a wow factor.

We plan to increase coverage as much as possible.

It's absolutely scalable. We have plans to increase usage.

BlazeMeter is a scalable product. It's user-friendly and easy to operate, which I find appealing.

I would rate the scalability a seven out of ten. 

We've never had issues with scalability. We've got hundreds of tests in BlazeMeter now, and we haven't had a problem aside from some performance problems with reporting. 

The scalability of BlazeMeter is good. The scalability of BlazeMeter is good. As BlazeMeter is a tool that allows me to trigger over 1,00,000 deployment-wise, I consider its scalability to be good.

Scalability-wise, I rate the solution a seven out of ten.

Around five or six people in my company use BlazeMeter.

The scalability is incredible. We could scale it to as big or small as we want, with our license being the sole limitation. The resources are in Docker containers in Docker images. We could scale within a few minutes if necessary. 

The product is fairly scalable.

Scalability-wise, I rate the solution a seven or eight out of ten.

It is a scalable solution, but our company currently uses the tool's free version, and we have not opted for its paid version. Considering the aforementioned fact, I can't comment on the solution's scalability though I have heard from one of my friends that the product's scalability is good.

Around 50 people can use the product in my company.

BlazeMeter is a highly scalable solution. The solution is SaaS and the cloud vendor controls the scalability.

BlazeMeter's scalability for our company depends on the cost and our testing needs. It is a complex decision since it is all about how much testing we do, for how long, and what our budget allows. It is all about finding the right balance between our requirements and affordability.

Though the product is scalable, I found the tool to be a bit tricky while setting up the scenario for the stress test and during step-up and step-down kind of scenario setup.

It is scalable as per our needs. In our working model, the only team that uses BlazeMeter is ours. This solution is used only by our team whose mission is to bring performance tests to projects and squads.

I see certain limitations when it comes to the scalability part of BlazeMeter since, in our company, we have faced multiple interruptions, because of which we had to stop certain testing processes.

Scalability-wise, I rate the solution a five out of ten.

I cannot give you an exact number related to the number of users of BlazeMeter in our company since we are just one of the teams in the company that uses the tool. I believe that around 150 to 200 people in my company use BlazeMeter.

The scalability is great. We can have a lot of virtual users when we need them.

We use BlazeMeter in different environments because we have customers with on-prem and cloud solutions.

We have not done a lot of scalability testing with BlazeMeter to determine the full capabilities of the solution.

Small enterprises would prefer to use BlazeMeter and those companies which have a favorable budget should choose Micro Focus LoadRunner or Tricentis NeoLoad.

The solution is highly scalable. Five people are using the solution at present. I rate the scalability an eight out of ten. 

It is a scalable solution. My company does not have a high user load to deal with using the product.

Right now, I don't know about the product's stability. I did not experience any downtime or performance issues with the solution.

We are planning to scale up to more BlazeMeter products very soon. You can scale it well. We want to scale up to ten products a month.

We did not encounter any issues here. Scalability is one of the wonderful parts of working with BlazeMeter.

The scalability is good. 

We have not had scalability issues for our needs. We're talking about scaling stuff out to hundreds of thousands of requests per second and those in turn generate a lot more traffic internally. So with whatever we use, it's perfectly fine.

Scalability was great; no issues.

One load engine was not sufficient to run the JMeter scripts that I’ve written. Scaling up to seven load engines largely eliminated these issues.

We encountered no scalability issues, though we were testing at relatively low volumes.

We have only used basic, but for one thousand users, it works great.

We didn't have any scalability issues. I can't remember how many users we had. We weren't doing incredible load testing. We were just using heavy load testing. There were no issues on the BlazeMeter side.

We have about 20 users who run over 1,000 test cases.

I implemented it for 1,000 users. 

The product seems extremely scalable. 

We have not encountered any scalability issues.

We have tested up to hundreds of thousands of concurrent users and the system performed well.

We encountered some scalability issues. The start time for load test increases with the increase in number of users to be simulated.

We did have scalability problems.