IBM API Management vs. Kong Konnect

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
IBM API Management
Score 8.9 out of 10
N/A
IBM API management enables creation and management of web application programming interfaces (API).N/A
Kong Konnect
Score 8.3 out of 10
N/A
Kong Inc. is a cloud connectivity company headquartered in San Francisco. They are the creator and primary supporter of Kong, the open-source Microservice API gateway, and offer Kong Konnect, an enterprise-tier platform that delivers connectivity and visibility for services in multi-cloud environments.
$250
per month
Pricing
IBM API ManagementKong Konnect
Editions & Modules
No answers on this topic
Plus
$250
Service/Month
Enterprise
Custom
Offerings
Pricing Offerings
IBM API ManagementKong Konnect
Free Trial
NoYes
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoYes
Entry-level Setup FeeNo setup feeOptional
Additional Details
More Pricing Information
Community Pulse
IBM API ManagementKong Konnect
Top Pros
Top Cons
Features
IBM API ManagementKong Konnect
API Management
Comparison of API Management features of Product A and Product B
IBM API Management
8.0
1 Ratings
1% below category average
Kong Konnect
-
Ratings
API access control8.01 Ratings00 Ratings
Rate limits and usage policies9.01 Ratings00 Ratings
API usage data9.01 Ratings00 Ratings
API user onboarding7.01 Ratings00 Ratings
API versioning7.01 Ratings00 Ratings
API monitoring and logging8.01 Ratings00 Ratings
Best Alternatives
IBM API ManagementKong Konnect
Small Businesses
NGINX
NGINX
Score 9.1 out of 10

No answers on this topic

Medium-sized Companies
NGINX
NGINX
Score 9.1 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 8.8 out of 10
Enterprises
NGINX
NGINX
Score 9.1 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 8.8 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
IBM API ManagementKong Konnect
Likelihood to Recommend
8.0
(1 ratings)
10.0
(1 ratings)
User Testimonials
IBM API ManagementKong Konnect
Likelihood to Recommend
IBM
If you are truly using IBM API Management for an API gateway, you will be ok. if you start trying to build custom scripts to transform messages complex in nature, it will soon become unmanageable.
Read full review
Kong, Inc
Using Kong [Konnect]'s declarative settings, a user may control traffic, automate deployment, and maintain container-based software after it's deployed. In addition, it handles the whole lifecycle of service management. Installation, management, and operation of Kong [Konnects]'s cloud-native connection runtimes may be performed in any cloud or Kubernetes provider environment, as well as on-premises environments. In order to optimise their services and transactions, users may keep track of their services and transactions in real-time via real-time monitoring.
Read full review
Pros
IBM
  • Import APIs - We have an existing inventory of APIs and services, so having an easy import process was required. IBM provides the ability to import Swagger so the process was quick and easy.
  • Service Offerings - Can create plans to control various model offerings for varying clients depending on the need. You are not locked into a tier structure and can customize if a need arises.
  • API Usage - visibility into the use of an API with a wealth of reporting information allows you to support an API from a production use to trending and forecasting any future growth.
Read full review
Kong, Inc
  • Application orchestration
  • Error tracing
  • Analyzing traffic
  • Load balancing
Read full review
Cons
IBM
  • Troubleshooting deployment pipeline - identifying issues with your api based on restrictions through a deployment pipeline is difficult. If a quality assurance environment is less stringent than a production environment, making sure your api is accessible and configured appropriately is tough.
  • Code level scripting is limited to javascript and xslt. so if any complex fanning needs to occur, you are limited in tooling.
  • Administration is more cumbersome than it needs to be. There are roles/profiles that are defined, but to use a group email for the approval or use of an api needs to managed better. A more thorough thought process needs to be defined - which I think IBM is tackling as an improvement.
Read full review
Kong, Inc
  • Community support
  • Sample projects for easy integration
Read full review
Alternatives Considered
IBM
There are a lot of similarities between Apigee Edge and IBM API Management. Some of the differences at the time of this posting is... 1) IBM APIM/C integrates better with other products. Dynatrace is used to track API and service specifics with the ability to offload those statistics for operational reporting. 2) If you are evolving from DataPower, IBM API Management is a logical choice to support additional REST APIs. 3) Generating keys is simple. Integration of those keys with a secure data vault is easy as well for your consumer.
Read full review
Kong, Inc
No answers on this topic
Return on Investment
IBM
  • Centralizing on an API management platform was imperative. Being able to support SOAP UIs as well as REST APIs was required. Because of the tooling, service inventory and provisioning can be managed - regardless of the pricing and cost structures are used.
  • Constructing plans that provide tiering options based on rate limits help in onboarding new consumers. The lesser cost in onboarding through an API gateway outweighs the cost of modifying/configuring an API to handle multiple clients.
  • Defining guidance and onboarding practices while rolling out the product also helps in the adoption, reference architecture, and governance that can save your company money.
Read full review
Kong, Inc
  • Increased application efficiency
  • Reduced system downtown
  • Significantly improved error resolution
Read full review
ScreenShots