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

OrbusInfinity 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

OrbusInfinity
Ranking in Enterprise Architecture Management
13th
Average Rating
8.0
Reviews Sentiment
7.2
Number of Reviews
2
Ranking in other categories
IT Service Management (ITSM) (37th)
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 OrbusInfinity is 3.3%, down from 3.8% 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%
OrbusInfinity3.3%
Other96.3%
Enterprise Architecture Management
 

Featured Reviews

Kenneth Igiri - PeerSpot reviewer
Enterprise Architect at Ecobank Transnational Incorporated
Cost-effective, integrates with the Office tools, and allows us to articulate all entities across the enterprise on one platform
The refresh cycles for our dashboards could be better. I keep complaining about that. The refresh is supposed to be once a day, but I would love it if it was real-time so that if I make a change to the data in iServer, I should see those changes immediately reflected in the dashboards. They use Power BI, and it seems they've scheduled their refresh to be once a day, which is not that good for us. We've had some issues with the integration between Visio and iServer because sometimes the add-in that allows you to do that integration takes a lot of memory and then your Visio crashes. However, I've not experienced this issue for some time, so it was probably fixed in the recent version. Also, if I copy a large amount of data and I want to copy from one Visio file to another, I have had a case where it suddenly just closes Visio without saving. So, that integration could be more smooth. There should be ease of integration with other systems in our environment such as SysAid. I understand that there is an integration to ServiceNow, but we use SysAid. We need to be able to say that when there's an incident that impacts or requires a change in a particular component, ServiceNow or SysAid should be able to communicate to Orbus that this component is about to change. Similarly, when it comes to discovery or when a new architecture change has happened in the enterprise, we should be able to detect the change in the baseline Enterprise Architecture. There should be such advanced automation. The visibility of our models is limited to those to whom we have assigned licenses. I would've loved it if everyone in the organization could at least see the diagrams. The licensing should be there for those who need to make updates or changes.
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

"I like the integration with the Office tools such as Visio and Excel. The integration with Excel helped us to be able to upload data very easily. Integration with Visio helps us to be able to make changes once and have a centralized diagram. We don't have versions of the diagram. This integration with the Office tools is very useful."
"The most valuable features are mainly the reporting side of things and the dashboard."
"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 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."
"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."
"Serverless offers a great pay-as-you-go model that is really excellent."
"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."
"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 because I can deploy without any downtime in the majority of cases."
"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

"We found a few issues with importing data and all the manipulation of data, especially when it came to the BI side of things because it utilized a particular template to be able to get certain reports. The user administrators could not manipulate it to get the right reports."
"The refresh cycles for our dashboards could be better. I keep complaining about that. The refresh is supposed to be once a day, but I would love it if it was real-time so that if I make a change to the data in iServer, I should see those changes immediately reflected in the dashboards. They use Power BI, and it seems they've scheduled their refresh to be once a day, which is not that good for us."
"I would say in the debugging, we could maybe improve or in monitoring."
"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."
"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 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 challenges I have faced while adopting or using Serverless include the different syntax, syntactical understanding, and the steep learning curve with team members."
"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."
"Improving Serverless is a difficult question because I am not deeply familiar with Serverless, so it is really difficult for me to judge."
"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

"It was very cost-effective as compared to the other ones we evaluated. We spent about $20,000 per annum for support and license together. There was also an implementation fee at the beginning. I would rate it a nine out of ten in terms of pricing."
"The licensing is on a yearly basis. We currently work with a standard fee."
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
Government
18%
Financial Services Firm
11%
Manufacturing Company
10%
Insurance Company
9%
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...
 

Comparisons

No data available
 

Overview

Find out what your peers are saying about OrbusInfinity vs. Serverless and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.