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

OpenText ProVision vs Serverless comparison

Why PeerSpot?
 

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) (44th)
Serverless
Ranking in Enterprise Architecture Management
6th
Average Rating
8.0
Reviews Sentiment
5.7
Number of Reviews
26
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2026, in the Enterprise Architecture Management category, the mindshare of OpenText ProVision is 1.6%, up from 0.8% compared to the previous year. The mindshare of Serverless is 0.5%. It is calculated based on PeerSpot user engagement data.
Enterprise Architecture Management Mindshare Distribution
ProductMindshare (%)
Serverless0.5%
OpenText ProVision1.6%
Other97.9%
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 because I can deploy without any downtime in the majority of cases."
"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."
"Serverless has saved me a lot of money and time in my organization."
"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."
"Making use of Serverless has at least helped us save 50% in cost spending on resources."
"Previously, when we were deploying it on VPS, our whole day was spent on setting up a VPS and setting up all the CI/CD pipelines, but with Serverless it is instant and in just 10 to 15 minutes you are up and running."
"Serverless is a great tool for every software engineer, and if any software engineer has not used this tool, they are lacking knowledge and a great opportunity."
"Serverless offers a great pay-as-you-go model that is really excellent."
 

Cons

"Lacks the ability to 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."
"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."
"To improve Serverless, I think if the AWS team provided more common examples of how to implement in our current project, along with some demos, it would be very helpful for us."
"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."
"We have been using this framework for a long time but now feel the cost is expensive, so we need to improve in this area."
"Serverless could be improved if we had more flexibility in how we use memory and could manage memory usage ourselves, especially for background tasks."
"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."
"The biggest challenges I have faced while adopting or using Serverless include the different syntax, syntactical understanding, and the steep learning curve with team members."
"Serverless is not suited for production environments."
"I would say in the debugging, we could maybe improve or in monitoring."
report
Use our free recommendation engine to learn which Enterprise Architecture Management solutions are best for your needs.
915,341 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
15%
Construction Company
14%
Comms Service Provider
12%
Financial Services Firm
8%
Construction Company
28%
Financial Services Firm
11%
Manufacturing Company
9%
Outsourcing Company
8%
 

Company Size

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

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for Serverless?
The experience with pricing, setup cost, and licensing was pretty straightforward and smooth. AWS has a number of in-built Serverless options, so you didn't really need to go to the marketplace. Th...
What needs improvement with Serverless?
I think we are moving in the right direction because AWS recently announced something regarding VMs and Lambda VMs for long-running Lambdas. There are also SnapStart and a few other things availabl...
What is your primary use case for Serverless?
We primarily run jobs on Serverless, specifically on AWS Lambda, using short-running jobs triggered by events. We can connect to an API Gateway for various purposes. For instance, if a client wants...
 

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: September 2026.
915,341 professionals have used our research since 2012.