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

Serverless vs iServer 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

iServer
Ranking in Enterprise Architecture Management
10th
Average Rating
7.4
Reviews Sentiment
7.4
Number of Reviews
18
Ranking in other categories
Business Process Design (14th)
Serverless
Ranking in Enterprise Architecture Management
6th
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 May 2026, in the Enterprise Architecture Management category, the mindshare of iServer is 4.7%, up from 4.4% compared to the previous year. The mindshare of Serverless is 0.3%. It is calculated based on PeerSpot user engagement data.
Enterprise Architecture Management Mindshare Distribution
ProductMindshare (%)
Serverless0.3%
iServer4.7%
Other95.0%
Enterprise Architecture Management
 

Featured Reviews

Antonios Lazanakis - PeerSpot reviewer
Senior IT Solution Architect at a financial services firm with 10,001+ employees
Flexible, easy to use, and easy to import data
We use iServer to establish an enterprise architecture function in our organization iServer is a very flexible platform for defining your own enterprise architecture model. It is very easy to import data, and we also have good integration with Visual Drawing Tools and SharePoint. The solution is…
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

"iServer has valuable features for workflow and document management."
"iServer is a solution that helps catalog enterprise architect solutions and catalog information."
"We like the governance."
"This is a flexible tool compared to some other solutions."
"It has helped having data lineage in the business cluster, which is used as control artifacts."
"Process modelling through object creation and management is beneficial as a very effective change management of processes at the object level, because if you need to modify a process and it will impact other processes as well, the object changed automatically changes in other processes as well."
"Overall, I would say that it's a poor man's EA repository."
"The solution has wide use within Microsoft products. The integration with Microsoft products, and, in particular, Microsoft Office, is great."
"Serverless has positively impacted my organization because I can deploy without any downtime in the majority of cases."
"Serverless offers a great pay-as-you-go model that is really excellent."
"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."
"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 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."
"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."
"Serverless has positively impacted my organization by shifting our focus from infrastructure management to pure product delivery."
 

Cons

"The modelling needs improvement, specifically forecasting capabilities and scenarios."
"Overall, I would say that it's a poor man's EA repository. It seems like a good idea, but doesn't really work in practice."
"The one issue is that if you want to import predefined work, you need to put the licensing model in."
"More visualization techniques and ways to report the data might be helpful."
"The performance is slow, which is something that should be improved."
"It's a very simple tool, which makes me concerned with the performance."
"We could allocate permissions to use only specific components to the users rather than the entire instance."
"The modelling needs improvement, specifically forecasting capabilities and scenarios."
"I choose eight out of ten because to go ahead with Serverless, we need to do YAML file creation and other format file creation."
"The biggest area for improvement in Serverless is around cold start latency, especially for applications that aren't constantly active."
"Serverless could be improved if we had more flexibility in how we use memory and could manage memory usage ourselves, especially for background tasks."
"I struggled with wanting to put breakpoints throughout the code and then use the debugger."
"The reason I choose a seven is primarily resource-based scheduling. This is what we are not able to get around on Serverless."
"Serverless can be improved by effectively handling large scale applications, as large scale applications would save more money."
"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."
"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."
 

Pricing and Cost Advice

"The product has a moderate pricing."
"They offer annual subscriptions for developing countries, which are not affordable for small or medium businesses."
"The price of iServer is reasonable compared to other solutions."
"It's about 13K to set up and 9K for the license for three months. I think it's about 20K a year, but we haven't firmed up on pricing yet because the price depends on how long we commit to the solution."
"Aim for the exact number of people who shall define/review approve and view the processes, as it will impact the cost."
"The solution is cheaper than its competitors."
Information not available
report
Use our free recommendation engine to learn which Enterprise Architecture Management solutions are best for your needs.
894,738 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Government
9%
Manufacturing Company
8%
Retailer
5%
Construction Company
32%
Financial Services Firm
11%
Outsourcing Company
7%
Healthcare Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business7
Midsize Enterprise3
Large Enterprise10
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise5
Large Enterprise5
 

Questions from the Community

What needs improvement with iServer?
iServer should invest in enhancing the capabilities of the embedded drawing tool, draw.io. draw.io is a drawing tool used to draw architectural diagrams, flow diagrams, etc. It is an alternative to...
What is your primary use case for iServer?
We use iServer to establish an enterprise architecture function in our organization.
What advice do you have for others considering iServer?
I would recommend the solution to other users. Overall, I rate the solution a nine out of ten.
What is your experience regarding pricing and costs for Serverless?
My experience with pricing, setup cost, and licensing is that I recently feel the licensing is a bit expensive; we need to renew the license, but we are still renewing it. In the future, a lower li...
What needs improvement with Serverless?
Serverless can be improved by adding more plugins, as they help to support many integrations and can facilitate integration with other tools, such as monitoring tools like Grafana. User experience ...
What is your primary use case for Serverless?
My main use case for Serverless is to deploy Lambda functions from AWS. A specific example of how I use Serverless with Lambda functions is that we deploy Lambda functions for any transfer-related ...
 

Comparisons

No data available
 

Overview

 

Sample Customers

Barclays, Cathay Pacific, Deloitte, British Gas, MasterCard
Information Not Available
Find out what your peers are saying about Serverless vs. iServer and other solutions. Updated: April 2026.
894,738 professionals have used our research since 2012.