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

Serverless vs erwin Evolve 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

erwin Evolve
Ranking in Enterprise Architecture Management
12th
Average Rating
7.8
Reviews Sentiment
6.9
Number of Reviews
19
Ranking in other categories
Business Process Design (21st)
Serverless
Ranking in Enterprise Architecture Management
7th
Average Rating
8.0
Reviews Sentiment
6.0
Number of Reviews
23
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of July 2026, in the Enterprise Architecture Management category, the mindshare of erwin Evolve is 3.5%, up from 2.6% 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%
erwin Evolve3.5%
Other96.1%
Enterprise Architecture Management
 

Featured Reviews

ScottLawson - PeerSpot reviewer
Director IT Architecture at QAD
Enables us to present data and objects visually, in diagrams, and to make them available via the web. Also enables web-based editing of data.
We tried their collaborative web modeling and we used it with a few people but we tend to not use that piece. We tend to collaborate with the people and then my team of architects draws up the diagram using the modeling tool. We then iterate through those. I would like to use it, but it was a little clunky when they first rolled it out. Overall, it's more about the company having room for improvement. What they need to do is to consolidate more of their products. For example, I was just looking and I couldn't figure out what erwin DT is. It's on the website but it would help if they could put information together and make it more clear as to what products they have and how they work with other things. I hear them talking in the support forums and, when I talk to the representative, they say they're going to do a bunch of stuff but it seems the progress is slow. The changes they need to make are to take their old, legacy product, which we use, and focus a lot on it so they can transform it into a modern cloud tool so that we have fewer little pieces to deal with. They could also fix their security model. It's very confusing to get new people onto the tool and to make sure that your content isn't being exposed to the wrong people.
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 feature that stands out for me is the ease of configuring objects and the screens to show them. It's really easy to add a new type of object in this reference. Creating a new type of object, using it, and evolving it a little bit in terms of what we can document about it are the main features that made us decide to use this provider."
"Forward and reverse engineering were valuable features."
"We can efficiently deploy business models into the databases and generate SQL scripts."
"Evolve is scalable with multi-user ability, so multiple designers and engineers can work on the same data model simultaneously."
"It is a customizable tool that allows you to do a lot of architectural modeling for customers, and you can use different kinds of diagrams to represent the architecture setting."
"By placing the data and the metadata into a model, which is what the tool does, you gain the abilities for linkages between different objects in the model, linkages that you cannot get on paper or with Visio or PowerPoint. That is a huge discriminator."
"Workgroup Repository collection of data models allows research across models without worry about platform incompatibilities and provides easy KPIs about corporate data assets."
"The initial setup was really straightforward and the deployment was done within one day."
"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 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."
"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."
"There is a huge impact as my traffic gets auto-adjusted, I do not have to worry about whether my server is capable of handling the traffic or not, Serverless servers are much more capable, and I just need to pay for whatever I am using."
"After migrating to serverless, we saved about 50% of the cost that was occurring in the previous architecture, and our operation time also got reduced by about 40% compared to the previous architecture due to the use of Step Functions, Lambda, and Aurora Serverless, which are all services managed by AWS."
"The best features that Serverless offers include being without the server, which itself says we don't need to depend on the server maintenance, and so we don't need to worry about these server things."
"Serverless has positively impacted my organization by making us more agile in giving releases, which has benefited my teams by allowing us to continuously maintain our Node packages and different scripts, which are now more easily manageable."
"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."
 

Cons

"With the Excel importing, the "up to date" part is the challenge."
"It could have had a more streamlined navigation. It seemed that when you went to the explorer panel, there were just so many different ways of doing the work that I could not remember, "How did I do this? How did I get to that point in that model to get back to it?" If I wanted to build a new one, where do I start? It just seemed like there was such a smorgasbord of ways of doing it that it was just overwhelming."
"I would like it to be easier to make changes and then deploy them into production, especially when you have multiple web servers or front-ends. It would be nice to make a change and then have it propagate to the production servers in a more automated fashion."
"The way that we are using it for application management, we have several KPIs. We want to follow and monitor them regarding a number of solutions. We cannot calculate this today. We would like real-time calculations along with the KPIs in order to improve the user experience. We would like the tool to be able to display this, not only as signals, but as charts."
"For what it says it can do, it does a good job, but using it is too difficult."
"There might be improvement required to better support some of the MPP databases for non-relational data structures and NoSQL databases."
"They need to develop Evolve's user experience. For example, MEGA has a useful client view that helps with impact analysis. MEGA provides information about the processes, services, infrastructure, and portfolio of applications in one central view. It lets you see the periphery and relationships among components. This view is impressive, and Evolve doesn't have it."
"Add some ability to do conditional Visualization on the models and in reports (some ideas) – maybe as a specialized Theme or Diagram or Display."
"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."
"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 struggled with wanting to put breakpoints throughout the code and then use the debugger."
"Serverless is not suited for production environments."
"I would say in the debugging, we could maybe improve or in monitoring."
"Serverless can be improved with more usage videos."
"Improving Serverless is a difficult question because I am not deeply familiar with Serverless, so it is really difficult for me to judge."
"Serverless affects my team's productivity and collaboration by presenting some challenges."
 

Pricing and Cost Advice

"The licensing enables you to differentiate between people who edit the content and the people who consume it. We are able to keep the licensing costs down by keeping the "contributor" licenses to a minimum, and we then just roll out the content in a read-only version for the rest of our users."
"On a yearly basis, our licensing costs are 50,000 euro. There are no additional costs because we are on a SaaS model."
"Yearly, our cost is €100,000."
"The cost is something like $15,000, per license. But I haven't looked at those numbers in three years. It was over $100,000 to initially set everything up and get it all configured."
"Unless you are a one person shop – always go with the Workgroup edition and Concurrent licensing."
"I think erwin is quite expensive. I have difficulty selling the portal, in fact."
"I estimate that we pay between $40,000 and $50,000 a year for the solution, not including the upfront costs to buy things the first time."
Information not available
report
Use our free recommendation engine to learn which Enterprise Architecture Management solutions are best for your needs.
902,894 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
13%
Financial Services Firm
11%
Computer Software Company
11%
Performing Arts
9%
Construction Company
30%
Financial Services Firm
11%
Manufacturing Company
9%
Outsourcing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business7
Midsize Enterprise2
Large Enterprise12
By reviewers
Company SizeCount
Small Business12
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...
 

Comparisons

No data available
 

Also Known As

erwin EA, erwin Business Process, erwin Enterprise Architecture
No data available
 

Overview

 

Sample Customers

AT&T, Bank of America, Chevron, Duke University, ESPN, Fidelity, GE, JP Morgan Chase, KPMG, McGraw Hill, NASA, Pfizer, Royal Bank of Scotland, Teradata, Union Pacific, Vodafone, Wells Fargo.
Information Not Available
Find out what your peers are saying about Serverless vs. erwin Evolve and other solutions. Updated: June 2026.
902,894 professionals have used our research since 2012.