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

Apollo GraphOS vs SEEBURGER Business Integration Suite 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

Apollo GraphOS
Ranking in API Management
20th
Average Rating
7.8
Reviews Sentiment
4.1
Number of Reviews
9
Ranking in other categories
No ranking in other categories
SEEBURGER Business Integrat...
Ranking in API Management
24th
Average Rating
8.6
Reviews Sentiment
6.9
Number of Reviews
39
Ranking in other categories
Business-to-Business Middleware (2nd), Managed File Transfer (MFT) (12th), Integration Platform as a Service (iPaaS) (14th)
 

Mindshare comparison

As of October 2026, in the API Management category, the mindshare of Apollo GraphOS is 0.8%, up from 0.4% compared to the previous year. The mindshare of SEEBURGER Business Integration Suite is 1.5%, up from 0.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
Apollo GraphOS0.8%
SEEBURGER Business Integration Suite1.5%
Other97.7%
API Management
 

Featured Reviews

MB
Business Development Manager at Digitaltrack
Unified schemas have streamlined team collaboration and have reduced API-related deployment issues
We had a positive experience with Apollo GraphOS, but there are a few areas where I think it could be improved. One area is the learning curve around GraphQL Federation and schema governance. Teams that are new to federated architectures often need to understand best practices. More guided onboarding, built-in recommendations, and practical examples would make adoption easier. I also think the observability and troubleshooting experience could be enhanced, particularly when diagnosing issues that span multiple subgraphs. While the platform provides useful insights, tracing complex requests across a federated environment can still require additional investigations. Another improvement would be more granular administrative controls and reporting, especially for larger organizations where different teams manage different parts of the GraphQL platform. Although the CI/CD integration is one of the product's strengths, having more out-of-the-box integrations and similar configurations for popular DevOps tools would reduce the initial setup effort. These suggestions would make the platform easier to adopt, operate, and scale, particularly for organizations that are beginning their GraphQL Federation journey. One thing I would like to see in future releases is deeper operational visibility for large-scale federated environments. As the number of subgraphs and development teams grows, it becomes more important to quickly identify where performance bottlenecks or schema-related issues are originating without having to correlate information from multiple tools. More built-in governance capabilities would be valuable, such as stronger policy enforcement, approval workflows for schema changes, and richer reporting for platform administrators. Another area that could be improved is the onboarding experience. While the documentation is comprehensive, having more guided setup wizards, architectures, and real-world implementation examples would help new teams become productive more quickly. I would also like to see even broader integrations with common enterprise monitoring, security, and development platforms so organizations can manage Apollo GraphOS as part of their existing operational ecosystem rather than relying on additional customization. These points would make day-to-day administration easier and improve the experience for organizations running GraphQL at a larger scale.
SS
Senior Software Engineer at HCLTech
Exceptional support and reliability drive optimal data flow and integration
The features of SEEBURGER Business Integration Suite that I found most valuable are related to entity flow. We can find the entity flow to be very useful so we can grab the flow accordingly. There is no disturbance in the connections, and it is very clear to check the connection flow with applicable queues. When comparing to other applications, SEEBURGER Business Integration Suite is the easiest way to understand the application. I have also worked on the cloud services where SEEBURGER Business Integration Suite is moving to cloud. I have worked on cloud services where the mapping part is in the cloud itself, along with the connection setup.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Apollo GraphOS has positively impacted our organization by reducing unwanted code and helping us combine multiple services."
"Apollo GraphOS has had a positive impact by improving the way we manage and evolve our GraphQL APIs."
"Apollo GraphOS has positively impacted my organization by improving API reliability, streamlining schema management, and reducing deployment risk, which made collaboration between developers more efficient."
"Apollo GraphOS positively impacts my organization by providing a complete platform for API orchestration, schema governance, observability, and federation."
"Apollo GraphOS has significantly enhanced both the developer experience and product delivery timelines by offering a centralized approach to managing GraphQL schemas and services, helping reduce overhead and improve collaboration between frontend and backend teams."
"The most valuable features of Apollo GraphOS OS for me are its security and authentication processes."
"Apollo GraphOS has positively impacted our organization by allowing us to streamline our GraphQL APIs for the front end and enabling us to grow much faster."
"Overall, Apollo GraphOS has been a valuable asset."
"We can use it to script and monitor processes."
"SEEBURGER BIS increased our efficiency by at least 30 percent."
"Partner connectivity and the process builder are the most valuable features."
"The SEEBURGER Business Integration Suite (BIS) was one of a few which provided translation for various formats, communications, and integration into SAP, all under one hood."
"One of the things that SEEBURGER always touts is their ability to do "any to any" formatting... it doesn't matter if you want to take a CSV file or an XML file or a flat file or a PDF file or a structure EDI file; you can transform it from one format to another - any to any or even to the same format - which is a really nice feature."
"We use Message Tracking, which is a very good feature. Message Tracking has about 300 to 400 business people who can find documents and ask the integration team about them. For example, they looking for a document that the vendor or trading partner tells them that they sent, but they don't see it in the ERP system yet. So, they go to SEEBURGER Message Tracking, which can tell them if we received it already from the outside and what happened, e.g., if it went to SEEBURGER BIS or if it's already in the ERP system. It's a very simple tool to use. They also can use that tool to see the source document."
"In our landscape, we have a lot of AS/400s or iSeries and SEEBURGER Business Integration Suite (BIS) has a file service listener that allows data to seamlessly be transferred between the SEEBURGER solution and the AS/400."
"Of all the projects where people have come to me, I can't remember having to say, "No, we can't do that.""
 

Cons

"Apollo GraphOS could be improved with simpler pricing, more transparent usage and cost reporting, easier onboarding for new teams and learners, and more detailed documentation and troubleshooting guidance for complex GraphQL."
"Apollo GraphOS OS is using a detailed project, and it can be time-consuming because it has a lot of data to manage. It sometimes takes longer than three seconds, which can affect loading times and lead to user dissatisfaction. I would like to see improved performance."
"There’s room for improvement in schema collaboration tools, especially in large teams where multiple developers are working on overlapping parts of the API."
"The reason I held back from giving it a perfect score is that some enterprise scenarios still require additional effort."
"The documentation about the Federation could be clearer."
"I rated it six out of ten because while it offers useful capabilities such as schema management, schema validation, and API observability, I feel there are several areas that need improvement."
"I think Apollo GraphOS could be improved with more beginner-friendly documentation and deeper customization options for dashboards so that people could easily understand the dashboard and have clearer guidance for advanced GraphQL use cases."
"I think Apollo GraphOS can be improved since teams new to GraphQL federation may find concepts such as subgraphs, schema composition, contracts, and router configuration take time to understand, making the platform seem more complex than necessary for smaller teams."
"They need to be more competitively priced. From what I can see, their training is pretty expensive, and they don't do anything for free."
"We occasionally get ZIP files. Sometimes the ZIP file has one file inside of it, and sometimes the ZIP file might have 30 files inside of it. We have been working with SEEBURGER to enhance their PKUNZIP process to be able to unzip multiple files in a single workflow instead of just one file. This is still something that is in process."
"A person whom I work with, and is not very technical, found the setup complex, as there are a lot of steps."
"I would like there to be a feature that could handle the limited server."
"I don't think the scalability of the solution is that great because they have tied the solution to their named nodes and it does not allow scalability like some of the cloud products allow."
"The initial set up was done by SEEBURGER consulting. It can be complex due to various factors, such as server settings, database settings, and security settings."
"They have their own private cloud. That's the reason we did not go ahead with managing everything by ourselves or moving into the cloud. They said that they're going to be doing it within the next two years, having access to Azure and AWS. That would be something we would like to see."
"In the BIS, if I want to have some API functionalities, that is a separate tool. The integration between the API tool and the BIS is not that straightforward. If they were to combine these tools and give us one suite, that would be helpful. Today I have a lot of partners onboard. I have something like 50,000 partners doing API transactions. If I want to introduce a new tool for API management, I have to do a lot of workarounds. But if it were integrated well within the existing suite, it could be straightforward for me."
 

Pricing and Cost Advice

Information not available
"Price and licensing are comparable to other systems. It's well-priced and simple. It's not user-based or anything. It's just per seat, per system. So, it's pretty straight forward. Because it's per system, one system is enough. However, if you want to make it larger, then you can grow with it."
"On an annual basis, our support costs, which are based on the licensing, are about £120,000."
"Our licensing model is based on transactions. We have a base service contract which is priced against a volume of transactions and another volume of individual transactions, which are covered by one service agreement. Then, we have development services on top of that. Our annual spend is around £80,000. It's about mid-priced, as there are some cheaper alternatives out there and some more expensive ones. It's neither cheap nor expensive. It's somewhere in the middle."
"I have had exposure to other big vendors over the years and would have to say the pricing is pretty typical. They all fall into a common pricing range, at least the bigger vendors: Axway, IBM Sterling, Globalscape, and SEEBURGER. They all fall into that mid-tier pricing. So, SEEBURGER is commensurate with other large integration vendors operating in this space. Maybe it is lower than some of the really high-end ones. You can get some of these high-end transactional messaging integration systems, like TIBCO, that tend to be kind of on a higher echelon of pricing. I would say SEEBURGER is more mid-level."
"They need to be more competitively priced. When it comes to training, they need to lower their prices. It shouldn't be so specific. Maybe they should outsource training to another company. From what I can see, their training is pretty expensive, and they don't do anything for free."
"We pay maintenance of between $75,000 and $100,000 per year, per box."
"The pricing seems to be competitive and the maintenance is standard."
"The way they have their licensing structure set up, they have a lot of different modules. For us, we did not really know if we were licensed for certain things or not. We had to reach out to them multiple times to tell them that we were looking for this or that capability. We had to buy licenses for different things at different points in time, not knowing that we could have it bundled initially."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
919,894 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
14%
University
10%
Program Development Consultancy
10%
Financial Services Firm
9%
Manufacturing Company
13%
Financial Services Firm
10%
Construction Company
8%
Retailer
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise3
Large Enterprise3
By reviewers
Company SizeCount
Midsize Enterprise4
Large Enterprise38
 

Questions from the Community

What is your experience regarding pricing and costs for Apollo GraphOS?
I am not sensitive to nor very knowledgeable about the pricing and setup cost.
What needs improvement with Apollo GraphOS?
I think Apollo GraphOS could be improved with more beginner-friendly documentation and deeper customization options for dashboards so that people could easily understand the dashboard and have clea...
What is your primary use case for Apollo GraphOS?
My main use case for Apollo GraphOS is to manage, monitor, and optimize GraphQL APIs. It helps to organize schemas, improve API performance, and make it easier to collaborate and control access acr...
What is your experience regarding pricing and costs for SEEBURGER Business Integration Suite?
Regarding the pricing of SEEBURGER Business Integration Suite, I would rate it as 7 out of 10.
What needs improvement with SEEBURGER Business Integration Suite?
Regarding areas of improvement for SEEBURGER Business Integration Suite, the cloud functionality needs enhancement. The cloud interface is currently too cluttered, especially when creating new tran...
What is your primary use case for SEEBURGER Business Integration Suite?
I have worked around 3.5 years with SEEBURGER Business Integration Suite ( /products/seeburger-business-integration-suite-reviews ). Currently, I am working with WebMethods. Previously, I worked fo...
 

Also Known As

No data available
SEEBURGER BIS
 

Overview

 

Sample Customers

Information Not Available
Altis, Autoliv, Cebi, Cofresco, MoneyGram International, Samsonite Europe, VSP Global, BMW Group, OSRAM, Magna, Lavazza
Find out what your peers are saying about Apollo GraphOS vs. SEEBURGER Business Integration Suite and other solutions. Updated: September 2026.
919,894 professionals have used our research since 2012.