No more typing reviews! Try our Samantha, our new voice AI agent.

OpenText ProVision vs Serverless comparison

 

Comparison Buyer's Guide

Executive Summary

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

OpenText ProVision
Ranking in Enterprise Architecture Management
25th
Average Rating
6.4
Reviews Sentiment
7.2
Number of Reviews
3
Ranking in other categories
Business Process Management (BPM) (45th)
Serverless
Ranking in Enterprise Architecture Management
7th
Average Rating
8.0
Reviews Sentiment
6.0
Number of Reviews
24
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2026, in the Enterprise Architecture Management category, the mindshare of OpenText ProVision is 1.6%, up from 0.4% compared to the previous year. The mindshare of Serverless is 0.4%. It is calculated based on PeerSpot user engagement data.
Enterprise Architecture Management Mindshare Distribution
ProductMindshare (%)
Serverless0.4%
OpenText ProVision1.6%
Other98.0%
Enterprise Architecture Management
 

Featured Reviews

reviewer1944672 - PeerSpot reviewer
Senior Director, Head of Process & Functional Architecture, Intelligent Automation at a real estate/law firm with 10,001+ employees
Good attribute attachment but problems with collaboration
I primarily use OpenText ProVision to create our end-to-end process repository and library for different parts of the organization, capturing the collaboration process to get the right inputs OpenText ProVision's best feature is the capability to attach a variety of attributes and extract and…
SA
Lead Software Engineer
Serverless workflows have boosted rapid AWS development but still need better CI and automation
Serverless has many advantages, and it is very easy to handle with a cloud solution. However, there are a few concerns about the limitations. Especially when I work with Lambdas, there are maximum Lambda timeouts. Likewise, there are several things from Serverless, such as maximum file uploads. Serverless can be improved by addressing the challenges faced when we have the first infrastructure. Sometimes it is hard because we need to manually create things such as Cognito pools. While 90 percent of the time is automated, more automation would be better. If Serverless provided CI/CD capabilities, that would also be great, as currently it only allows for manual deployments. Additionally, when working with cloud services, Serverless allows the use of LocalStack or Serverless Dev, but I think Serverless Dev might need simplification for easy access without organization registration. When considering needed improvements, I get frustrated with Lambda time and similar issues, which are actually not related to Serverless but rather are AWS issues. However, when discussing Serverless, the main points I see require improvement from the Serverless end.

Quotes from Members

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

Pros

"The stability of the product is very good."
"OpenText ProVision's best feature is the capability to attach a variety of attributes and extract and analyze that information."
"I like that all the features come as part of a standard license and that one license covers everything."
"Serverless has positively impacted my organization by shifting our focus from infrastructure management to pure product delivery."
"Serverless has positively impacted my organization as it has been a good experience for the team overall because it is a new framework that we had to learn, and cost-wise, it helps because moving to Serverless means you do not have resources spinning all the time."
"In terms of time or cost saved compared to before using Serverless, I save approximately 60 percent of my development time because everything is very lightweight and gives me the freedom to work within Serverless."
"The best feature of Serverless is cost; when the application is in use, then it will incur cost, unlike traditional servers where it is the cost of all the uptime."
"My advice to others looking into using Serverless is that you can use it if you want to save money, if you don't want to manage servers, if you only want to be charged for the amount of time you use, and if you want to run code and ad hoc tasks."
"Serverless positively impacts my organization by being really cost-effective and serving as a production performance testing tool, as we increase the load, it automatically increases the CPUs and RAM without needing any manual intervention or heavy servers for this type of testing."
"Serverless offers many best features; it is really easy to use, very developer-friendly, and has a great community."
"Serverless has saved me a lot of money and time in my organization."
 

Cons

"OpenText ProVision's collaboration management is quite complicated and difficult to use."
"My main complaint is that the solution is not open source in the sense that you can't have your own in-house developments."
"Integrating with or interfacing with other tools like data management tools would be very helpful."
"There are a number of drawbacks. Mainly, the collaboration is lacking to some extent - at least when it comes to how we are using it."
"Lacks the ability to have your own in-house developments."
"Transitioning from servers to Serverless results in a price increase due to the additional maintenance and patches AWS provides, but if costs could be reduced, more customers would consider moving to Serverless architecture."
"Serverless is pretty much stable, but I believe the only downside is when it has to do some kind of cold warming, which might actually take some time."
"I believe Serverless can be improved as I have faced some pain points and challenges."
"Serverless is a very comprehensive platform. I have not explored everything, but I use it only for traffic management and the auto-scaling features. That is why I deducted one point."
"I see that the local development setup in Serverless is more complex, so if you provide examples or automation that we can test and deploy locally on a local machine, then automatically shifting all methods or functions into production would significantly improve efficiency."
"The reason I choose a seven is primarily resource-based scheduling. This is what we are not able to get around on Serverless."
"With the upcoming technology change and the migration towards Generative AI and the exploration of large language models, it would be quite helpful if serverless services evolve with that."
"The scalability of Serverless is limited; as you increase your code, it is not scalable, and we need to think out of the box to solve several problems."
report
Use our free recommendation engine to learn which Enterprise Architecture Management solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
15%
Construction Company
13%
Comms Service Provider
10%
Energy/Utilities Company
10%
Construction Company
31%
Financial Services Firm
11%
Manufacturing Company
8%
Outsourcing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business14
Midsize Enterprise5
Large Enterprise5
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for Serverless?
Regarding pricing, setup cost, and licensing experience, I find the application to be very cost-effective. The headcount needed is much lower compared to supporting services in software development...
What needs improvement with Serverless?
Debugging distributed Serverless applications can still be frustrating. When multiple functions, teams, and events are involved, tracing a failure is not always straightforward. Cold start latency ...
What is your primary use case for Serverless?
Our main use case for Serverless is deploying APIs and background processing jobs without having to manage servers. We had several workloads triggered by API requests, S3 uploads, and scheduled eve...
 

Also Known As

Metastorm ProVision
No data available
 

Overview

 

Sample Customers

Delta Technology, Export Development Canada, Rompetrol, Salt River Project, AMEC, U.S. Air Force, HP Consulting & Integration
Information Not Available
Find out what your peers are saying about OpenText ProVision vs. Serverless and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.