It is a cost-effective solution. 

I am not involved in the licensing side of things.

Pricing is the number-one downfall. It's too expensive. They could make more money by dropping the price in half and getting more customers. It's the best product there is, but it's too expensive. It could be 10 out of 10 if they dropped the price. There are so many people who don't use it because it's so expensive.

I don't have full visibility on the licensing aspect. I know it is very expensive mainly due to the size of the company also. In that way, IBM, which we've used before, is also expensive. From a license cost perspective, it is cheaper than IBM. However, from a support perspective, the software is costlier than IBM. 

We needed specialized support from the software vendor. The engineering cost was too high.

Currently, the licensing solution for this product is pretty straightforward. The way that Software AG has moved in their licensing agreements is very understandable. It is very easy for you to see where things land. Like most vendors today, they are transaction based. Therefore, just having a good understanding of how many transactions that you are doing a year would be very wise. Luckily, there are opportunities to work with the vendor to get a good understanding of how many transactions you have and what is the right limit for you to fall under.

With any solution like this, on day one you have a project that you're trying to work on, but just understand where you are trying to go with the solution. Some plugins are cheaper than others, and others are more expensive than others. Just make sure that you understand the full scope of what you might end up using the product for, so you can understand the all-in costs.

The tool works extremely well. Software AG offers packaged solutions for many packaged apps. Oracle SQL Server or Salesforce are add-ons that you can purchase and install easily for plug and play with packaged solutions. When you start moving into custom applications, there are no packaged solutions. The good news is that typically custom apps are built in some type of known technology, and that technology can easily be integrated into webMethods Integration Servers.

Business-to-business communications is an add-on that needs to be purchased. While super important to my organization, it is an add-on outside of the standard webMethods Integration Server. I would strongly recommend the business-to-business add-ons, especially if you're looking to use webMethods Integration Server in that capacity. It just makes the development cycles a lot shorter as well as making it much easier to manage your business profiles.

The solution's development license is free for three to six months. We have to pay for other things. 

Comparing webMethods Integration Server pricing with other solutions depends on the context. The cheapest will always be open-source ESB solutions, such as Apache ServiceMix and Apache Camel. Still, when you compare the quality of support of enterprise software, such as webMethods Integration Server, with open source software, enterprise software usually provides better support quality and higher level solutions versus open source software that typically doesn't have a real support model.

If you're lucky, you'll get someone who will immediately give you support for your open-source solution, but if not, you'll wait for months without any real support. webMethods Integration Server, on the other hand, as it's under Software AG and has an enterprise behind it, can create one-tier, two-tier, and three-tier support mechanisms, apart from providing you with timely support. Hence, you can use the product as part of an ongoing, much bigger integration project. That's where the differentiation and the value come in.

From an enterprise context, the price of webMethods Integration Server isn't that high because Software AG enters a relationship with companies and provides webMethods Integration Server as part of a much larger solution.

I don't think webMethods is the cheapest but I think the quality is worth it. But it's not cheap.

We're satisfied with our choice and the price is not a reason to look for something else.

The solution’s pricing is too high.

Keeping in mind that we haven't explored the microservices completely, which has been a key element of their innovation recently, I do think webMethods is coming under increasing pressure when it comes to their price-to-feature value proposition. It's probably the single biggest strategic risk they have. They're very expensive in their industry. They've been raising the price recently, especially when compared with their competitors.

The solution has a yearly licensing fee. It is very costly.

I'm not sure if there are any extra costs involved in using the solution. 

I would like to see better pricing for the license.

webMethods Integration Server is expensive, and there's no fixed price on it because it has a point pricing model. You can negotiate, which makes it interesting.

There are no hidden costs in addition to the standard licensing fees for webMethods.

For corporate organizations, it's a very cheap or fairly priced product, but for growing or small businesses, it's quite expensive. These businesses would probably need to consider an enterprise services bus at some point. Thus, from a pricing point, it closes out non-cooperate businesses.

A slightly watered down version would be nice so that small, growing businesses could afford it.

The price is a little bit high, especially regarding their support.

The support fees are very high and we don't need such huge support.

I'm working in the development part of the company. I'm not aware of the prices.

I would say it's an affordable product. When it comes to big organizations, it's for sure affordable.

I signed a three-year deal with them. It is a yearly locked-in price for the next three years.

I would like to have training for my team members, but the training offered is a little bit expensive.

It's a good deal for the money that we pay.

This is an expensive product and we may replace it with something more reasonably priced.

Initialy good pricing and good, if it comes to Enterprise license agreements.

It is expensive, but we reached a good agreement with the company. It is still a little bit expensive, but we got a better deal than the previous one.

I suppose webMethods aim for large-scale enterprises which is why the price is high, but with high output and better outcomes.

Some of the licensing is "component-ized," which is confusing to new users/customers.

Yet you can also choose between perpetual or periodically terms, in case you do not want to be bothered to buy another version once the newer version released you should consider periodic license.

I rate the pricing a nine out of ten. The product is expensive.

We purchase a yearly basis license for the solution. I rate its pricing an eight. It is not that expensive. The price depends on the use cases, support, and resources for implementation.

I'm a user of the application. I don't directly handle the licensing. 

There is a license needed to use the webMethods Integration Server.

The vendor is flexible with respect to pricing.

I'm not really familiar with the commercial side. I don't really know about pricing as I'm only on the operations side.

I cannot comment on the pricing, as this is in the purview of my boss, from whom I received access to download the product. My role is solely to explore the solution's capabilities. 

It is worth the cost.

Most of my clients would like the price of the solution to be reduced.

The pricing and licensing costs for webMethods are very high, which is the only reason that we might switch to another product.

Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client.

It was an Enterprise license and I am not sure of the current status.

Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials.

I don't have insight on the pricing.

I'm not involved in this.

I only use the product in the company where I work. The company bought the product so I don't have any idea.

Licensing is an issue since all products do not have central licensing. UM has a different license, IS has a different license, etc. This differs from client to client.