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
9th
Average Rating
7.4
Reviews Sentiment
7.4
Number of Reviews
18
Ranking in other categories
Business Process Design (13th)
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 iServer is 4.2%, down from 4.5% 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%
iServer4.2%
Other95.4%
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 is a very flexible platform for defining your own enterprise architecture model."
"I love how there are no milestone swimlanes."
"This is a flexible tool compared to some other solutions."
"Tech support is very responsive. They solved issues within a prompt response time."
"There were lots of different requirements, and collaboration and review is one of the biggest things. There is also Office 360 integration, and there's flexibility to use it as a database as well."
"Central repository holding single version of truth."
"iServer has valuable features for workflow and document management."
"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 the outcome was very positive in most of the projects we used it, especially with the fast delivery made possible by clear boundaries for each function and the ability to resize the team constantly without needing to think too much about that, while the price remains very reasonable."
"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."
"I can share specific metrics indicating Serverless's positive impact: I achieved 100% uptime, an impressive feat compared to traditional servers that often experience downtime during peak usage."
"Serverless impacts my organization positively in many ways by enabling us to easily debug issues when any pipelines break; we can get errors, debug them, and address issues."
"Serverless has positively impacted my organization as it has become the de facto standard for any POCs I have been doing, unless something specific is required that demands an on-demand instance."
"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."
"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 migration tool needs to be included in the main package, and not as a separate license."
"I do not find it friendly to use."
"The product is more expensive than Spark."
"It definitely needs help to improve the visual aspect of the solution."
"It's a very simple tool, which makes me concerned with the performance."
"The one issue is that if you want to import predefined work, you need to put the licensing model in. So if you wanted to import work that was done before, you then need to buy a separate product for that."
"iServer should invest in enhancing the capabilities of the embedded drawing tool, draw.io."
"There could be features for process mining, process simulation, and analytics."
"When that account was temporarily blocked for an unjustified reason on their side, it became an issue for our whole project and caused significant costs and loss of users because of that single incident."
"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."
"Improving Serverless is a difficult question because I am not deeply familiar with Serverless, so it is really difficult for me to judge."
"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."
"Serverless can be improved with more usage videos."
"Serverless is not suited for production environments."
"I believe Serverless can be improved as I have faced some pain points and challenges."
 

Pricing and Cost Advice

"Aim for the exact number of people who shall define/review approve and view the processes, as it will impact the cost."
"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."
"They offer annual subscriptions for developing countries, which are not affordable for small or medium businesses."
"The solution is cheaper than its competitors."
"The price of iServer is reasonable compared to other solutions."
"The product has a moderate pricing."
Information not available
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
Financial Services Firm
22%
Government
9%
Construction Company
6%
Manufacturing Company
6%
Construction Company
31%
Financial Services Firm
11%
Manufacturing Company
8%
Outsourcing 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 Business14
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?
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
 

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: August 2026.
909,725 professionals have used our research since 2012.