TIBCO ActiveMatrix Service Bus is an advanced integration platform designed for rapid data exchange and connectivity, ensuring productive workflows and robust performance in high-traffic scenarios.
| Product | Mindshare (%) |
|---|---|
| TIBCO ActiveMatrix Service Bus | 4.5% |
| Mule ESB | 17.2% |
| IBM Integration Bus | 15.5% |
| Other | 62.8% |
| Type | Title | Date | |
|---|---|---|---|
| Category | Enterprise Service Bus (ESB) | Jun 23, 2026 | Download |
| Product | Reviews, tips, and advice from real users | Jun 23, 2026 | Download |
| Comparison | TIBCO ActiveMatrix Service Bus vs Mule ESB | Jun 23, 2026 | Download |
| Comparison | TIBCO ActiveMatrix Service Bus vs IBM Integration Bus | Jun 23, 2026 | Download |
| Comparison | TIBCO ActiveMatrix Service Bus vs Oracle Service Bus | Jun 23, 2026 | Download |
| Title | Rating | Mindshare | Recommending | |
|---|---|---|---|---|
| webMethods.io | 4.0 | 7.7% | 94% | 95 interviewsAdd to research |
| IBM DataPower Gateway | 4.1 | 5.1% | 96% | 32 interviewsAdd to research |
| Company Size | Count |
|---|---|
| Small Business | 2 |
| Midsize Enterprise | 1 |
| Large Enterprise | 7 |
| Company Size | Count |
|---|---|
| Small Business | 39 |
| Midsize Enterprise | 10 |
| Large Enterprise | 49 |
TIBCO ActiveMatrix Service Bus is recognized for its speed, stability, and ease of use, offering a scalable, service-oriented architecture that meets high-security needs. Its low code environment facilitates efficient API development, reducing the learning curve for developers. As middleware, it connects systems like CRM and ERP, enabling seamless application and business communication. However, it can benefit from more frequent updates, enhanced cloud integration, and improved API management.
What are TIBCO ActiveMatrix Service Bus key features?Companies utilize TIBCO ActiveMatrix Service Bus across regions and industries for its central role in enterprise integration. It manages functions such as email, data transformations, streaming integration, and APIs, serving as a vital platform for connecting applications and facilitating business processes in environments like CRM and ERP.
TIBCO ActiveMatrix Service Bus was previously known as ActiveMatrix Service Bus.
| Author info | Rating | Review Summary |
|---|---|---|
| Cheif Specialist- Licensing Systems at Roads & Transport Authority | 3.0 | As a manager, I find TIBCO ActiveMatrix Service Bus essential for integration, offering robust performance and excellent messaging services. However, its API management lacks functionality, falling behind competitors. We switched to TIBCO as a corporate-level decision for core integration. |
| Managing Director at Talipoint (Pty) Ltd | 4.0 | I use TIBCO ActiveMatrix Service Bus to perform calculations and data transformations based on predefined rules. The most valuable feature is its stability, but the initial setup process could be simpler. I haven't considered or used other solutions. |
| Technical and Delivery Manager (Integration) at United Delta | 3.5 | I find this solution stable, scalable, and easy to use with its GUI/IDE. Initial setup was straightforward. However, it's very expensive, especially when adding components. Customer support is okay. I rate it 7/10 overall. |
| Senior Delivery Manager at Wipro Limited | 4.0 | I find this older version of TIBCO AMX/BW stable, reliable, and scalable for large clients. While it performs well, my main concern is the inadequate product support. I am looking to replace it, but I rate the solution an 8 out of 10. |
| Integration Lead at a comms service provider with 1,001-5,000 employees | 3.5 | We use TIBCO for system integration, finding it easy to learn but expensive with immature cloud and poor support. We're actively seeking alternatives due to these issues and termination of local professional services. |
| Middleware and Enterprise Integration Head at a financial services firm with 1,001-5,000 employees | 4.0 | I value TIBCO ESB's ease of development, considering it a market leader. However, its latest version (6.X) is less stable, more expensive, and has poorer support than 5.X, lacking clear upgrade advantages. |
| Senior Manager at a insurance company with 5,001-10,000 employees | 3.5 | I use TIBCO ActiveMatrix Service Bus for integration. Despite its ease of development and features, my intermediate version has stability issues with slow resolution. Its high licensing cost is a major concern, prompting me to explore alternatives. |
| Technical Enterprise Architect at a tech services company with 201-500 employees | 4.5 | My organization uses a stable, SOA-based platform for health services. However, our outdated version lacks cloud, containerization, and Agile capabilities, necessitating an upgrade or replacement to meet future requirements. |
| Head of Technology Department at a comms service provider with 1,001-5,000 employees | 4.5 | I use this stable, scalable API middleware with perfect support and straightforward setup. I recommend it for enterprise integration, rating it 9/10, though smaller container images and improved monitoring are needed. |
| CEO - Director General at Megapractical | 5.0 | I rate TIBCO 10/10. It's a stable, scalable, and fast interconnectivity platform praised for its ease of use. While initial setup is complex and the API manager needs improvement, its rapid ROI is highly valued. |
I use the solution in my company not as an engineer but as someone who currently operates at a managerial level.
The product adds to and serves as a corporate-level product that offers standard integration and helps transport data during one-to-one integration and multi-layer integration while also helping with streaming data integration, web services, APIs, and other tech services. Basically, TIBCO ActiveMatrix Service Bus serves as our company's core integration platform.
The most valuable feature of the solution is that the performance is robust. TIBCO offers its users with one of the best messaging services. The messaging services and integration offered by the product are the best in the market.
I don't like the product's API management platform, as it doesn't offer users enough functionality to help with API lifecycle management, making it a product that is way behind its competitors. The aforementioned area can be considered for improvement in the product.
I have been using TIBCO ActiveMatrix Service Bus for over ten years. In our company, we use the solution as customers or corporate users. If I am not mistaken, my company uses the latest version of the solution.
Stability-wise, I rate the solution a seven out of ten.
Scalability-wise, I rate the solution a six to seven out of ten.
My company consists of around 7000 employees, and we use the solution as an integrated service in around 300 to 400 systems, both internally and externally, making it a huge number.
Our company uses the solution every minute and every second, and we can't function without it.
I rate the technical support a seven out of ten.
Neutral
I have experience with another solution in the past, and I switched to TIBCO ActiveMatrix Service Bus as it was a decision made at a corporate level in my company.
One needs to have some level of expertise to be able to take care of the product's initial setup phase since it is not an easy process.
The solution is deployed on an on-premises model.
The time needed to take care of the solution's deployment phase is from use case to use case, but mostly, it can be done in a few days, considering that certain processes need to be changed.
My company has around 14 people to manage the entire platform, including the maintenance team, engineering team, etc.
Our company's in-house team took care of the product's installation phase.
Price-wise, I would say that the product is expensive.
I rate the overall product a six out of ten.
We use the product to perform calculations and transformations based on the data and predefined rules and logic.
The product’s most valuable feature is stability.
The initial setup process could be easier.
The platform is stable. I rate its stability an eight out of ten.
The product is scalable. I rate its scalability an eight out of ten.
The initial setup is complex. There should be enough guidance available to know the process. It takes around six weeks to complete. The number of executives required depends on the amount of work.
I recommend TIBCO ActiveMatrix Service Bus and rate it an eight out of ten. The product brings value in terms of long-term stability and good return on investment.
We currently mainly use this solution for its messaging functionality, but we also use the solution for email and file configuration.
The GUI and IDE features of this solution are easy to work with and to develop. We also find application management easy using this solution.
The solution is very expensive when you use multiple components, it would be better if this could be reduced.
We have been using the product for about three years.
It is a stable product.
We have found it to be scalable by increasing the amount of services we use.
We have found the customer support to be okay.
We previously used an open-source solution, but switched to meet our customers changing needs.
The initial setup was straightforward, and deploying the application was easy, but customization is slightly complex.
We implemented the solution in-house.
The price point of this solution would be more suitable for larger businesses. Each added component will require a separate license and increase the overall cost.
I would rate this product as seven out of ten.
Specifically, we have it in multiple regions for clients using ActiveMatrix (AMX). We are supporting them across multiple regions in the Asia Pacific and North America, including Mexico.
It's great for large clients, where it is largely being used. The BW and AMX are great.
The solution is robust. It's very stable and reliable.
It's definitely scalable.
I haven't actually gone through the latest version's features. I will not be able to comment on those as we don't use the latest. Many things that may be lacking may have already been taken care of specifically.
We don't need any specific improvements. The only thing is from a support point of view. We'd like to see improvements in product support. Whenever there is some kind of challenge or whenever there is a client issue, when we want to report it and offer some proactive solutions, we don't get proper assistance or support.
I've used the solution for quite some time.
The stability is great. It's robust and the performance is good. I don't see, for example, any drops in service, The reliability and availability are almost 99%. Stability is not an issue.
The scalability of the product is great.
The main challenge we have is support not being supportive enough. When we have issues, we'd really like them to be more helpful.
We are working specifically on a TIBCO exit strategy whereas we are actually trying to replace TIBCO iProcess and AMX with Red Hat products specifically. I used to attend all the Red Hat webinars, specifically any materials around which patterns were being used and what kind of challenges the teams faced. For that purpose, I'm just looking at those reports.
The initial setup is not that straightforward and it's not that complex as well. In my view, it is moderate. Once you actually get some training around it, you should be able to configure the setup and with proper training, it would not be an issue.
The amount of people needed to maintain and deploy it depends on the implementation. You need some administrators to support it. Not everyone will have elevated access. It requires multiple levels of people that run at a normal support level. Some likely need elevated access to actually look at the logs as well as the admin consoles.
I'm not sure of the exact licensing costs.
We do have an enterprise license, however, we do occasionally need to pay for some additional features.
We're consulting and implementing this solution.
We are using an older version. It is around the version 4.4 series. It's not even updated up to a version 5.
I understand there are a lot of new versions which have come up and can be implemented and deployed - and in the cloud as well. We can't look at them in the same way, as what we are actually supporting is somewhat older in terms of applications. These are not cloud-ready. That said, companies that have applications that are cloud-ready can actually go for the cloud-ready options and for early versions of AMX.
I would rate the solution eight out of ten.
We use this solution to integrate the various systems that we have. For example, from CRM to ERP, or from ERP to CRM, or to our billing system, or from CRM to our payment gateway.
We integrate the different applications, both northbound and southbound. If CRM wants to connect to a billing system, they don't go directly to the billing system, they come through ESB. If the CRM wants to connect to ERP, they don't go to directly ERP, they come via ESB.
ESB is like the central path that connects the various systems, both northbound and southbound.
The technology is really easy to learn. They use low code/no-code technology, which does not have a steep learning curve.
In terms of the cloud, I don't feel that TIBCO is mature enough. The cloud version was only released two years ago.
Sometimes there are issues with the loads. If the load is too high or if you have high traffic, you will experience some issues with the throughput.
They need improvements with the cloud version and the handling of the traffic.
Initially, we had the professional services with the TIBCO because we are in Africa, but unfortunately, they terminated it because they sold their business in Africa to another service integrator who didn't really understand the product. This service integrator was not as experienced using TIBCO, or maybe just assisting us with the TIBCO issues that we were having.
Issues with the support, the fees, and the termination of the professional services are reasons we are looking for other solutions.
I joined the company six years ago but have been using TIBCO for approximately eight years.
We have been working with TIBCO for more than five years and know how to work our way around it. We are comfortable working with it, apart from the throughput or if the traffic is high.
We are sure to find a few problems, but at least for right now, because we have been working with it for a long time, and now we know how to navigate our way around the issues that we get, it is stable enough.
The on-premises version is not as scalable. It is not the best, it needs improvement. We are experimenting with the cloud version right now.
It's a development tool. We have approximately 40 developers who use this solution.
We have had one or two issues with technical support. There seemed to be an issue with a ticket that we raised because it took almost four weeks to get it resolved.
Maybe the person who was supporting us didn't really understand the product or they didn't know what they were doing.
There have been a few scenarios where the support has been pathetic.
We have several TIBCO products including ESB, BPM (Business Process Management), and Spotfire for reporting.
My role is in integration and I typically use ESB.
The initial setup is straightforward. It's easy.
The deployment is not complicated. It is very simple to deploy.
The biggest issue disadvantage of TIBCO is that it is expensive.
It's just too costly.
We are looking for alternatives. We are looking to get away from TIBCO and looking for other integration tools.
There may be some services with TIBCO that we will continue to use, but any integrations going forward will be with another solution.
We are researching WSO2, Red Hat Fuse, and any other Mule software, or any other integration tools that can be used.
I would rate TIBCO ActiveMatrix Service Bus a seven out of ten.
I started with IntegrationManager, and I've seen TIBCO ESB grow from nothing to one of the top leaders in the ESB industry. I head the whole ESB team, the pool of developers, production, support team, enhancement whole all use TIBCO ActiveMatrix Service Bus.
The most attractive and beneficial feature is the ease of development. They have an excellent GUI that helps developers build any APIs in a few hours. No matter how complex they are, but they can be done in a few clicks. It saves a lot of time and increases the productivity and efficiency of the whole development process.
When I compare the new version 6.X with the classic 5.X, they are not giving the same kind of look and feel or the ease of use which we are used to. They are improving the DevOps and other new things we have now, but they still have to improve and mature.
When someone is planning to move away from their version 5.X to the latest one, they will have both options. Either upgrade to the latest version of TIBCO or go towards some other vendor. That's where they are not giving any competitive advantage or anything with the latest versions.
I think they need to improve. They need to really show the consumers what they'll get if they upgrade to the latest version.
I have been using TIBCO ActiveMatrix Service Bus for almost 15 years.
The stability of their latest version is not on par with their classic version 5.X. Their latest version 6.X needs to be more stable.
They set the standards for themselves with their previous versions, but now I see the quality of the whole product has gone down a little bit.
Fault tolerance, scalability, and durability have been maintained.
Their support teams aren't that great for the latest version.
The quality is good, but the price is on the higher side. The previous version and their pricing models were much more cost-effective. But maybe from their point of view, they have made changes. They have brought in containers and all the latest DevOps stuff, which is not very pocket friendly for their consumers.
For the same price, if I go for the previous version, I would have got a lot more capacity with similar features, but now they have changed their whole design.
I've been doing this kind of POCs and evaluating different ESB software from different vendors, including MuleSoft, WSO2, or IBM. I have to say honestly, TIBCO is still the best when comparing the features of all these things.
ESB is the middle component that connects to multiple systems. ESB works hand-in-hand with the API gateway, with your data leak projects, or with your streaming. If your requirement is purely from an ESB perspective, I think TIBCO ActiveMatrix Service Bus is still the market leader, and you can go with them.
I would giveTIBCO ActiveMatrix Service Bus an eight out of ten.
We are using it for integrating our enterprise applications and core systems with the front-end systems.
The version that we are using is neither the latest one nor the oldest one. It can be deployed on the cloud and on-premises.
It is easy to develop. It has a very wide range of features.
The older versions are very stable, and there are no issues with the product.
The intermediate version that we are using has stability issues. These stability issues should be resolved, but it seems like TIBCO is not focusing on resolving these issues. The resolution timelines are quite high even for high-priority incidents.
Its price should be lower. Its licensing cost is considerably high as compared to other ESBs.
I have been using this solution for more than 10 years. In our organization, we have been using it for more than 15 years.
The intermediate version that we are using has stability issues. Its older versions are very stable. I have not used its latest Container Edition, which probably is also stable.
It is scalable. This is a back-end product, and almost all front-end applications are using this solution.
Their support is excellent, but currently, their resolution timelines are quite high for stability-related issues that we are facing.
Its installation is straightforward. It takes around two hours in our lower environment where we don't have high availability. It takes around half a day in our production environment where we have high availability.
We installed it ourselves. You just need basic computer knowledge to be able to deploy it. For development, you need some skilled people, but deployment is quite easy. We have a team of 15 people for deployment and maintenance.
Its licensing cost is considerably high as compared to other ESBs.
We will have to migrate to Container Edition, which is the latest version, but it is not an easy migration. It is almost like redeveloping, and it requires specific changes. Our strategy team is exploring other ESBs. We will be deciding this within a month because we need to pay for the license.
I would definitely recommend this solution, but it also depends on a specific use case. If you can afford it and you are looking for a high-standard and high-performing solution for your use case with excellent support, you should go for it.
I would rate TIBCO ActiveMatrix Service Bus a seven out of ten.
There are a number of applications including use cases from the health industry, including health human services.
We're making good use of it, although our version is an outdated platform that needs to be replaced in order to be ready for the future. For example, we will be moving applications to micro-services and migrating components to the cloud.
The most valuable feature is that it is a service-oriented architecture, SOA-based.
Our version does not have cloud capabilities.
Containerization is not supported.
The is no support for Agile development.
We have been using this product for 12 years.
This product is very stable.
Scalability is fine, although our current version is just not able to move us to the future.
I was not part of the original implementation, although I'm sure that it was complex.
We have been working with this version of TIBCO for at least the past 12 years. We are now looking at replacing it with either a new version or a new solution from a different vendor.
This is a good platform but in our case, it needs to be updated. The future is on the cloud, the future is containerized, the future is Agile development, and our version is incapable of any of this.
I would rate this solution a nine out of ten.
We primarily use the solution as a middleware for exposing APIs so that one app can talk to another in separate application via APIs.
There are so many valuable features on the solution, there's almost too many to list.
If TIBCO could be able to sort the size of their base image in the Container edition, it would be really marvelous. Right now it's around 299 MB. We'd really want it to reduce to a few MBs.
TIBCO needs to improve its monitoring capability to be able to make use of alerts and to be able to have an alert threshold. For example, if there is an API, if it encounters a given number of errors or long response times, it could send an alert to a configured list of users either via email or SMS.
The solution needs to have cloud integration. There should be continuous integration and continuous deployment of new features.
We've been using the solution for six years.
The solution is very stable.
I believe the solution is scalable. With the Container edition, even with the non-containerized edition, depending on your architecture, and how you write your code, it's very scalable.
Currently, we have about 10 users as a support team. TIBCO is an integration layer, not really a place where users can log on and do transactions or approvals. It's not the type of technology that has a large user base.
We do plan to increase usage in the future. There are so many new integration use cases that we want to use on TIBCO.
The technical support offered by TIBCO is perfect. I don't think we have faced any issues when dealing with TIBCO support. Each time we raise a ticket and put the correct classification, they normally respond by SMS. We've been satisfied with the level of support we've received.
In the past, we tried using Oracle OSB. I don't think we'll go back and use them again. TIBCO has proven to be far superior. We didn't switch to TIBCO. What we wanted to do is to explore what Oracle had to offer. We later realized that the capabilities that TIBCO had were far, far superior to what Oracle was able to offer so we chose TIBCO instead.
The initial setup was very straightforward. There was no complexity in the implementation. Deployment takes a maximum of one to two weeks.
The last time we implemented the solution, we were installing certain components and adding in hot fixes.
We're users as well as consultants of the product.
Although we currently use the on-premises deployment model, right now, we are also exploring the possibility of having the service deployed in some hybrid form of the cloud. That's still on a theoretical basis. Nothing substantive has been done yet.
I would recommend the solution to any other organization which is interested in standardizing their integration layer. To me, this solution has really served the requirements we had with respect to enterprise integration.
I'd rate the solution nine out of ten.
The primary use case of this solution is to provide our customers with a faster way to get their data and to connect information between different environments, especially with corporate companies that have different branches in different parts of the country. They need to receive and share information as quickly as possible between the different environments.
This is the main way that we identify, in a fast way, to connect with different platforms.
It's a platform of interconnectivity that we provide to our clients with this solution.
We are specialized in installation and deployment using this platform. We use it to move the transformation of the companies to the new mature service-oriented architecture.
TIBCO has the best platform in terms of speed and ease of use.
The brand is very important, it has a percentage of the research and development of the product. They look at how you can get to obtain the best features from the platform. Most other platforms offer the same features in the same way and the same kind of platform, but with TIBCO, you get answers in milliseconds.
If you have high traffic transaction volume and you need more speed, more governance in your services, then you need to use TIBCO. This is the value that TIBCO offers and how it differs from others.
One of the areas that this solution could be improved is to provide the vendors with updated information. We don't always know what is going on with the development of the solution.
In the next release, there should be improvements made to the API manager. Other platforms are better.
This solution is stable.
This solution is scalable.
I don't work directly with technical support, but my team does. To my knowledge, they have not had any issues with technical support.
The technical support is good and they are knowledgable.
The initial setup is complex. Not all companies are ready to move forward with this platform because they don't understand how it works, what the real benefits are, and how to take advantage of this platform to obtain the best results for your company.
Before we can begin, we must understand the vision of the business. When you have that understanding then the setup is easy, but if you don't then it's complex.
It depends on the company, but it can take approximately six months to deploy this solution.
We consider the preparation of the environment, the installation, the testing, then the training. Not user training, but training the technical team in the companies to manage the platform inside the environment.
Then we deploy the solution together. We apply one life cycle, then certify it by CMMI.
Part of the sales process includes deployment and implementation. If this solution is not implemented correctly it is not the fault of the solution but with the vendor and not providing the necessary training.
With this platform, the return of investment would be less than one year.
There are many ways to measure the return of investment, it is not always just about how much money they will make, there are other factors.
ROI can be measured in terms of effort, social benefits, political initiatives, and many other things.
We consult with TIBCO to understand the market and try to get the customer's different levels of pricing.
Latin America has many vendors working with the same type of solutions that are open source.
Companies feel that by it being open source it could be the key to getting a free platform, but that is not the case. They would prefer to purchase a solution like TIBCO but don't have the budget.
In Latin America, there is a lot of immature environments in terms of connectivity or service-oriented architecture.
The wave of technology or the wave of the transformation came from the US and other first-rate countries. Latin Americans adopted technologies. It's not easy to deploy this type of technology quickly.
The first challenge is with the consultant and in making the sale by explaining what exactly is the value that you would be getting by staying in a real service-oriented architectural environment.
The second is that the corporate companies grow in a Catharsis because the growth of the companies is not well planned.
The best way to fix the problem that they have is to buy a platform to connect all of the different platforms that they have acquired in the past.
It's not enough to purchase the right product. You have to hire the right team to help you deploy this solution. Most of the vendors forget the customer, but the most important thing is to have the customer understand the solution that they will be working with.
The founder of TIBCO is an entrepreneur who always invests money to improve the product. He invests money to improve most of the products that he has. You will always be a leader in this area if you don't lose the philosophy of investing to improve.
I would rate this solution a ten out of ten.
