My company is big, and the Polarion Requirement works fine. 

The solution is scalable. Over a hundred people, including testing engineers, requirement analysts, and test managers, are using the solution daily in our company. I rate it a seven out of ten.

I would rate the scalability a nine out of ten. Compared to other tools, like Jira or PTC, Polarion is more scalable. It works similarly to the Windows operating system and Microsoft Office, tools I'm already familiar with. I haven't found any limitations with the work documents in Polarion yet.

It can work for medium-scale businesses as well. Siemens now offers a cloud-based SaaS model, making it easier to adopt without on-premises servers. 

This is a more cost-effective option than on-premises licenses, so even smaller companies could use the SaaS model if they can afford it.

I would rate Polarion Requirements' scalability seven out of ten.

This solution is scalable, but again it has limits. It can be scaled to a certain degree with new processors or memory, but it hits a point where it cannot scale anymore.

We have approximate ten people using this solution. They are all engineers.

The solution is very scalable. We have around 50 licenses.

I'm not sure that the scalability is good. I think we have enough room and memory on our server for it to work but it is too slow and we get timeouts. In that respect I don't think scalability is good. 

We never encounter any scalability issues during the deployment.

It is scalable. You can add a lot of documents and the volume can be increased. We have 20 users. It has not really been adopted by the end users in our company, but this is not because of Polarion. This is related to the processes used in the company.