Try our new research platform with insights from 80,000+ expert users

Nintex Process Platform vs Temporal comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Nintex Process Platform
Ranking in Process Automation
9th
Average Rating
7.8
Reviews Sentiment
6.9
Number of Reviews
24
Ranking in other categories
Business Process Management (BPM) (10th), Workload Automation (11th)
Temporal
Ranking in Process Automation
7th
Average Rating
8.6
Reviews Sentiment
7.2
Number of Reviews
17
Ranking in other categories
No ranking in other categories
 

Featured Reviews

Damilola Adeleye - PeerSpot reviewer
Straightforward interface and user-friendly
There are a lot of apps in K2, but what I really found that needs improvement is the management section of K2, especially the management server and the admin page where you can manage processes, add users, set security fees, and add licenses. The reason for this is because the part that is the section of administration, particularly the management called rows, has multiple rules, as many as you want. For instance, you may have around 200 rules, and when you view them, only the first ten are displayed, and you have to click next to see the next ten and so on until you get to the hundredth rule. On that page, as of today, we only have what we call to fetch, where you can search for a particular rule you're looking for, or else you have to keep clicking until you get to the final page you want. So that's a bit challenging.
AbhishekDash - PeerSpot reviewer
Orchestrates infrastructure tasks like deployment, deletion, and management
Temporal focus on developers rather than business users. In contrast to older workflow orchestration engines like Camunda, which are more business-oriented and strongly emphasize UI and workflow authoring, Temporal is geared toward developers. It provides extensive capabilities for building complex workflows. A standout feature of Temporal is its handling of long-running workflows, a significant advantage over many other solutions. Temporal excels in managing distributed transactions and application state durability, especially in microservice environments where transactions might fail due to network issues. Temporal simplifies these challenges by managing retries, fail-safes, and circuit breakers. As a result, developers don't need to implement these features manually; Temporal handles them implicitly, though it also allows for tuning based on specific needs.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"NWC forms could be better. Also, the ability to build workflows that are not dependent on SharePoint is very desirable. The forms feature just isn’t as functional as the forms for SharePoint."
"It is very easy to use events. K2 has useful tools."
"The workflow engine of K2 is its main strength. Its workflow engine is probably one of the best, and that's the reason why Nintex bought K2. It can clearly handle any complex process or scenario. K2 is almost low-code. It is a no-code or low-code solution. You don't have to read a whole lot of code. It is pretty much GUI based. Their support is also excellent. The biggest advantage of K2 is SmartObjects, which allow you to separate the data from the application. It is a standalone application that allows you to build a data source from different places, which a lot of other applications also do. It is called SmartObjects technology, which is pretty powerful. If I have data from different applications, such as JD and ServiceNow, I can just create a SmartObject based on a data source and use it. I have some forms that have six, seven, or eight applications in a single form with data from different places."
"The Vizio-style designer that runs in the browser is, to me, by far the most valuable feature of the solution. It means that the customer doesn’t have to install any client tools to create powerful workflows."
"Provides the ability to automate SharePoint processes (building sites, lists, updating content). You can also automate document and content processes, onboarding and offboarding, and general IT and HR solutions."
"I really like the visual representation. It actually looks like a flow chart, which is nicer than a SharePoint Designer workflow, which doesn't have that ability."
"It has helped us a lot, especially during the initial phase of a project where most of the things are done on paper."
"Out of box connectivity with UiPath."
"Temporal focus on developers rather than business users."
"We like the fact that the whole process is durable, which is very useful to us."
"The solution's most valuable feature is its ability to fix things quickly."
"When some jobs take a lot of time and fail midway, the solution’s retry feature automatically causes them to retry."
"It's easy to get started and user-friendly."
"The solution's most valuable feature is its ability to retry from an interrupted state."
"The initial setup is easy."
"It is very useful for long-running workflows."
 

Cons

"Currently, a notable challenge lies in the alignment of user experiences across the eight or nine applications within the suite. Transitioning between applications can be somewhat cumbersome due to varying user interfaces. However, the provider is actively addressing this concern by consistently rolling out updates every four to five months, aimed at harmonizing and streamlining the interfaces. This ongoing effort is expected to enhance the user experience over time. In terms of functionality and features, the platform stands out, offering flexibility with the option for both on-premises and cloud deployment. This flexibility extends to the RPA tool, providing clients with choices tailored to their preferences. An advantage lies in the shared security and data infrastructure across the toolset, facilitating smooth data transfer between applications. This contrasts with experiences with Oracle, where data transfer may involve complexities such as the need for intermediary file formats like TXL or SCZ."
"The tool can be limiting when more complex solutions are required. Improving it to offer greater functionality and less reliance on technical expertise could be beneficial."
"We would like to have access to an on-premises solution. In our country, we have a relationship with Central Bank of Egypt, which do noes not allow cloud solutions to be used. They should offer an on-prem solution with a flexible price license."
"​Bring all features available from the on-premise product into the cloud version and the workflow error reporting.​"
"The management server and the admin page where you can manage processes need improvement."
"The licensing needs to be improved. Right now, we find it's getting more expensive to use the product."
"The interface could be better and more language support is needed in the development environment or in the solutions platform in general."
"We would like to design parallel workflows and long-running workflows, along with new features for connecting to cloud-based systems."
"Sometimes it scales kind of badly, but it depends on the process of our products."
"While the tool can be a bit daunting initially, especially if you're not used to async programming models, it's generally a pleasure. There's always room for improvement, though. I've noticed some limitations with the .NET SDK regarding dynamic workflows, but this might have been improved in recent versions. Overall, I think Temporal could be more open about implementing features in a more—.NET-friendly way, especially in how you add workers and clients."
"There are areas where Temporal could improve. For instance, calling multiple microservices with Temporal introduces latency due to workflow registration and analytics overhead."
"Temporal images aren’t FIPS compliant, and we have to be FIPS compliant."
"One area where I think Temporal could improve is its dashboard, particularly in event tracking. Currently, the dashboard doesn't show a time-based view of events, meaning it doesn't display when an event started or went through the retry process. If this feature could be added in a future release, it would significantly enhance monitoring capabilities. Other than that, Temporal's overall performance is quite impressive, and we're confident we can migrate to the Temporal workflow."
"Configuring workflows can be improved —the solution could offer more options, but it's not a must-have."
"One area for the product improvement is the learning curve."
"Temporal could be improved by making it more user-friendly for beginners and non-technical staff, ensuring easier integration and usability across different use cases."
 

Pricing and Cost Advice

"Nintex Workflow is more expensive than Microsoft's native products, but it is still considered moderately priced when compared to higher-end products such as K2."
"Our maintenance costs are reduced."
"The price of this solution is affordable but the problem in Algeria is our community is a bit slower. The new clients might feel the solution is a bit expensive."
"Certainly. Notably, in terms of cost, this solution presents a substantial advantage, being approximately forty percent more economical compared to Oracle. It offers flexibility with two deployment options, catering to both cloud and on-premises preferences. Moreover, within each deployment option, there are two variations available. For organizations with limited IT resources and relying on citizen developers—individuals from the business side comfortable with technology—the platform allows for a more hands-on approach. These users can independently implement solutions without extensive coding or custom development. In contrast, the KQ solution at Symantec is adept at addressing the needs of sectors like banking, where extensive custom development is required for seamless integration with existing applications, websites, and ensuring robust security measures."
"The annual support costs are expensive."
"Nintex products are expensive, but valuable. Licensing in on-premise was historically based on a perpetual model, where you’d license per Web front-end. However, they are switching exclusively to a consumption (subscription) model, where you purchase the number of workflows you think you’ll use in your environment, and can scale up from there."
"Prices for licenses of K2 are high."
"Comparatively, it's expensive."
"Temporal is a free, open-source tool."
"The savings weren't as big as we initially expected, but they were pretty great from a developer's perspective."
"Temporal is open-source and free to use, which is great. We didn't have to pay for any premium features."
"The tool is open source under the MIT license, so there are no hidden fees. You can freely use everything on their GitHub and Docker images."
"It is worth the price."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
850,028 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
19%
Financial Services Firm
18%
Government
7%
Manufacturing Company
6%
Financial Services Firm
27%
Computer Software Company
18%
Retailer
8%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about K2?
The latest version of Nintex has many features. We have a clear roadmap and the necessary application to integrate it into our platform.
What is your experience regarding pricing and costs for K2?
Nintex Process Platform is expensive. Prices relate to both features and the professional services necessary due to our lack of an implementation team.
What needs improvement with K2?
The user interface in Nintex needs improvement. It is not very intuitive and requires changes. Additionally, the deployment process should be easier.
What is your experience regarding pricing and costs for Temporal?
Temporal OSS is expensive in infrastructure, but it brings back the reliability that companies need.
What needs improvement with Temporal?
The actual user interface is still in its early stages. It’s very basic. Users don’t really have a complex permission model yet. Users don’t really have ways to automate things like, for example, p...
What is your primary use case for Temporal?
We [my company] use it to run a large workload. We have a set of security scans we want to perform, and we distribute them over a full day, that’s over 24 hours. We use it to orchestrate all the st...
 

Comparisons

 

Also Known As

K2 blackpearl, K2 Five, Nintex Workflow
No data available
 

Overview

 

Sample Customers

SEA Corp, Omnicom Group, Verizon, STIHL
Information Not Available
Find out what your peers are saying about Nintex Process Platform vs. Temporal and other solutions. Updated: April 2025.
850,028 professionals have used our research since 2012.