What is your experience regarding pricing and costs for IBM API Connect?

It is a pretty expensive tool. The tool is expensive if I consider how products like WSO2 are available in the market. You have pretty much many options in the open-source community, considering how IBM's pricing can be an issue. If you want to scale for more hits per month, although it's an SQL license, you need to buy it from IBM, and it becomes pretty expensive for me. The pricing is pretty high.

I rate the product price a seven on a scale of one to ten, where one is a low price, and ten is a high price.

There was a need to purchase an upfront license or a one-time license or upfront license, but I cannot remember the details about it clearly.

The pricing is significantly high. I would rate it eight out of ten.

The pricing for 3scale is definitely cheaper. However, for enterprise-level projects, we don't recommend 3scale. If the client is medium or small and requires a basic API proxy or minimal transformation, we propose Red Hat. But for big, mature clients with complex solutions, we recommend IBM API Connect. The pricing for us on a yearly basis. But currently, IBM API Connect also provides it as a cloud service, where you pay as you use it. That provision is also available. Only the license is covered. There are no hidden costs or extra charges.

API Connect is expensive - I'd rate their pricing five out of ten.

All IBM products are expensive and API Connect is no exception. The license includes everything such as a per BVU charge along with other integration components plus OpenShift for microservices and DevOps and others. You can purchase a better BVU and then you can use any features or components under this license. They have the Cloud Pak for Automation package which includes BAW Business Automation. They also have something called Aspera for file transfers.

The price for IBM API Connect is reasonable. It's $20,000 to $30,000 yearly for a subscription, and the pricing could vary around $40,000 per year, per subscription. Its price is reasonable for customers who have around sixty million API calls yearly for unlimited environments.

We pay for the IBM API Connect monthly. We only need to pay the standard licensing fee.

Be sure you do not run into installation or upgrade issues. Our problems here were caused by our closed environments, however, still, it is in the dark of the systems where the problems are.

Pricing for IBM API Connect varies. If they are offering me the platform, in particular what they used to call Bluemix and what's now called IBM Cloud, it will be subscription-based pricing. They'll charge you based on how many APIs are called off your specific portion of the Cloud. If you're doing your own private cloud, on the other hand, it's a special grade. You have to own most of that software licensing so that you can put it on your own private cloud.

API Connect was highly expensive for us, but the decision to switch was made before I joined the company. It seems like the company bought it, but they didn't know how to use it. After two years, they decided to reevaluate and conduct some cost estimates.

This is a licensed product. If your company is looking to obtain a license, you have to work with IBM partners.

API Connect's license cost could be a little lower. But, unfortunately, there aren't many open-source API gateways. Ideally, some new developers could come up with a minimum-functionality open-source solution. When I look for open-source resources that work with API C or Apigee, I find very few that can do that. It's not available or very popular in the open-source community. I've only worked with large companies that are capable of affording these licenses. A better option for smaller companies might be to have two or three developers build a custom API gateway. That might be more affordable for them.

It should be cheaper. It has a yearly licensing.

Licensing is expensive but it's a good product.

We have an SLA we can draw from. I need to keep within certain numbers, however, I don't have a problem doing so. I can't speak to exact costs.

It is quite an expensive product.

IBM API Connect could be cheaper. We pay for the license yearly.

It's an expensive product.

I do not deal directly with the area of budgeting. We are partners with IBM, so maybe we get different pricing. I do not know about standard prices other than that this product can be expensive. We did not need to pay them anything extra for support or add-ons. It may not be the same for clients who are not partners.

API Connect is quite pricey. The developer builds the API and determines what should be put together. However, the business people determine the price. The product plan and pricing needs improvement. It is confusing to the client based on the way a business might put it together. E.g., I have to be able to pick out different APIs, then group them together. I then have to explain to the client if they subscribe to this API product all the services available. Many clients want a variety of price groups based on their API selection. I haven't seen anyone go from on-premise to the cloud. In fact, I am seeing people go from the cloud to on-premise because the costs can quickly grow on the cloud. If you want to small small, start with the cloud.

The pricing is too expensive with IBM. Sometimes, we prefer to go with an open source or something more lightweight.

IBM sets the pricing, but it would be a good idea to bring down the pricing by at least 20 to 30 percent.

The basic appraisal based on the two models is available on their website. The one is PVU-based and the other one is consumption-based. But that is a ballpark figure. Obviously, when you engage with them in a contract, they can negotiate.