With Dundas BI, you need to have a dedicated development team that can work on creating visualizations and reports and provide them to the end-users. As long as there is a development team working on things and deploying them for the client as a dashboard, it works smoothly for even 100 users. We did not observe any major issues in terms of performance in our region because we used the in-memory option in Dundas BI. When it comes to scaling for a larger user base, the biggest barrier of Dundas BI is the inability of business users to create their own reports. If they can create their own reports, the license count will automatically go up.

While working on one of the projects, we had a team of around seven developers. Over the period of two years, the number went up to somewhere around 15 users, but the end-users were around 200 or 300. That's how it worked for that particular deployment. In the latest deployment that I worked on, we were in the initial phase of creating the sample dashboard for the users. They were planning to increase the number of users. We created the reports, and our client was planning to add on users. It went pretty well, and they're going to increase the number of licenses.

It is license based. So, it depends on the number of licenses. We had around 40 or 50 developers using it.

The solution is scalable. We use it regularly, several times a week. 

We have thousands of users accessing the Dundas BI dashboards. It does scale quite well.

My organization is small, but it should just be a matter of how powerful the server is that you run it on.

No, scalability was one of the reasons we like Dundas.

Dundas BI is very scalable.

I don't have enough experience to comment on this.

Not yet.

No issues with scalability.

No.

Good.

Nope.