I would rate the scalability an eight out of ten.

I am the only one who uses this solution in our company. I am introducing this solution in my company. However, there's a 99% chance we'll stick with BizFlow.

When it comes to K2 applications, it automatically has access to your active directory to prevent users and the organization from signing up separately. So if you are in the active directory, you can access the platform. And if you are not in that directory, you don't have access. Every access to K2 is controlled by the active directory, making it very scalable.

I rate the solution's scalability an eight out of ten. There weren't any scalability issues, really. I think that we found it to be a little bit of a scalable device, but we were not able to achieve it. So there were limitations. So, maybe on the SharePoint side, there would be a limitation that we can raise only these many requests, and the space is about to get full. So that kind of scalability issue, I can remember.

In my organization, around 1,000 users were using the solution.

It is not a scalable solution because of its high prices. We also need K2 engine for small businesses for 50k USD since small businesses are already using other tools for form building. We need something similar to a workflow engine. We use a Russian product offering good protection since it is a .NET-based workflow engine, and its server also can use any programming language. We turned to this tool owing to K2's high prices since, in the end, we ended up paying 300k USD. 100 to 5,000 users work on the solution.

The solution is scalable according to our original requirements. It meets our needs. 

We have about 100 users on the solution. 

This is a scalable solution, however, some features are not available on the on-premises solution. An external vendor's assistance is needed to overcome this. 

I rate the solution’s scalability an eight out of ten.

The scalability of Nintex's product range is highly commendable. Positioned as an entry-level to medium-top product, it accommodates a broad spectrum of complexity in process execution. The distinction between the Flipflare and K2 products lies primarily in the level of development customization desired. Nintex Workflow Cloud caters effectively to businesses with minimal software development skills, offering a user-friendly, drag-and-drop interface with a no-code mindset. This empowers citizen developers to independently manage workflows.

The versatility of Nintex's offerings extends across the business spectrum, making them suitable for small and medium enterprises as well as large corporations. Notably, a substantial portion of Fortune 500 companies, around forty to fifty percent, currently leverage Symantec's products, attesting to their widespread adoption and effectiveness across diverse business landscapes.

The scalability is dependent on SharePoint, which relies on Active Directory. If you have an Active Directory, it depends on the Windows operating system, specifically the Windows server. While it might be challenging to scale horizontally, we can undoubtedly scale it vertically by adding more RAM, CPU, and other resources. The scalability issue has become more apparent recently, especially considering the on-premises solution. However, the number of processes within Nintex plays a significant role. If only ten processes are in place, scalability shouldn't pose a considerable challenge. Understanding the level of processes running within Nintex is crucial for addressing these issues effectively.

We cater the solution to enterprise-level business.

I rate the solution's scalability a seven out of ten.

It's a scalable product. We have approximately 4,000 AD users for this solution in our organization.

It is used across the board. Almost everyone in the accounting department uses this solution. We also have a bunch of different legal departments, and they also use it. It is being used from the bottom to all the way up. When someone submits a request, it can go to the VP and all the way up. Because it is an approval process, it depends on how high it goes.

The solution is scalable.

Nintex Workflow is definitely scalable.

It is a scalable product.

It is a scalable solution. From an end-user perspective, we have close to 6000 employees. In addition, we have a third party who does maintenance.

The solution is scalable. Approximately 100 people use it in our organization.

It's scalable. It's able to expand easily. 

There aren't too many users using it in the company. We had maybe 1,000 users at one point. I'm not sure if this is still the case. 

It's my understanding that the solution is scalable. If a company needs to expand it, it should be able to do so.

We have about 1,500 users on the solution currently. Anyone who can access SharePoint can access this product, and that is pretty much the entire company.

Scalability is tough. Workflows in SharePoint have the lowest priority of any task, and, in on-prem, workflows execute against the Web front-end servers. If your WFEs are under spec or at spec, workflow load will impact performance, and you may need to up resources or consider adding WFEs to enable large-scale deployments. 

In Office 365, the licensing model will be your limiting factor (subscription for the number of published workflows) so scalability is a non-issue.

Scalability is a kind of dependent thing. Essentially, it would require infrastructure and IT development to be able to do anything with the infra scalability or the platform scalability. We haven't tried it. We do know that when we want to sync up different environments, it's not that straightforward. I mean it's not complex, but it has a lot of activities. It's not a straight sync up between the two servers. You have to do a lot of tasks including download packages. It's a bit annoying because it takes up too much time from the ops team to be able to sync the two environments, especially when you're uploading packages that at times are not compatible. Again, it could be dependent on the way we've set it up on-prem. I don't necessarily know if that's a K2 issue or if it's an infra issue on our end, but assume it's likely both.

I would rate the scalability a six out of ten.

We have approximately fifty thousand users, right from the VP to the workshop people.

The Nintex solution can scale from a single server to multiple server deployments to manage workloads.

We have two people using the solution in my company. We are building demos to show potential clients.

Scalability is good. We implemented it in Belgium and then in France and we're now expanding the scope further.  

The product doesn't seem to have many limitations. It can likely scale well. 

This is a very easy solution to scale out.

We have approximately sixty thousand users for this solution. Perhaps one hundred of them support the applications and integration, but the majority of them are end-users.

No.

It is very easy to add users.

We have implemented K2 for two companies, but there are four or five companies using K2. There is a common problem right now in Turkey, so it is not easy to manage software installation.

You can definitely scale the solution. K2 has a feature that allows it to go with other solutions quite well. It's the best option for companies that need a solution that can scale due to the fact that it can integrate with many systems.

We have over 200 users in our organization.