Apigee and webMethods.io are competing in the API management solutions category. User feedback indicates that Apigee, with its extensive feature set, is slightly favored over webMethods.io, which excels in specific integration capabilities.
Features: Apigee offers comprehensive features like API Management, a Drupal-based Developer Portal, and Monetization capabilities. Its developer portal simplifies onboarding and documentation, while monetization supports various revenue models. Analytics features provide insights into API performance. On the other hand, webMethods.io strengths lie in application and data integration with adaptable integration server capabilities, making it ideal for complex integrations.
Room for Improvement: Apigee needs to improve its complex on-premise setup, integration with versioning systems, and role-based access management. Users find its support documentation and integration capacity lacking. webMethods.io could enhance automation capabilities, improve integration with modern tools, and offer more flexibility in orchestration and user experience.
Ease of Deployment and Customer Service: Apigee provides deployment options in Public Cloud, Hybrid Cloud, and On-premises, but faces challenges in data locality in hybrid models. Reviews of Google’s technical support are mixed, with some users experiencing slow responses despite general satisfaction. webMethods.io also offers similar deployment options but lacks robust support, often needing third-party consultancy, though it benefits from a supportive partner ecosystem. Users desire better orchestration independence from the integration server.
Pricing and ROI: Apigee is considered expensive, targeting mid to large enterprises with features that can justify the cost, though this might deter smaller businesses. High operation costs and complex licensing are noted, but monetization offers ROI advantages. webMethods.io aligns similarly with larger enterprises, offering competitive pricing, though the cost complexity from licensing and add-ons can be a downside. Both report positive ROI from effective API management, albeit with concerns about pricing.
They are responsive and provide assistance even during production issues.
The customer service and support are cooperative and effective in providing insights and solutions during challenges.
In the past two years, I have been experiencing less assistance.
An incident portal is available where we can raise tickets and based on priority, they reply.
Adding extra Cassandra databases is complex.
Whenever more resources are needed, they become available automatically without any human interference.
If any webMethods.io product is installed on-premises and a company wants to scale its application, either vertical scaling or horizontal scaling is needed.
Vertically, scalability is fine, however, I have not expanded horizontally with the product yet.
Apigee is stable, and we have had the system running on Apigee servers for more than four years without any stability issues.
We provide support to our clients, and the minimum calls I receive are for webMethods.io; it's very stable.
There are some issues like the tool hanging or the need for additional jars when exposing web services.
Apigee only allows validation of transactions up to a four-hour period, which requires manual hovering over the date and time.
Apigee should also incorporate these capabilities, especially in the on-premises version.
Analytics is one of the areas needing enhancement, specifically more visibility and control over traffic to improve capacity management and high availability.
When comparing the license cost and request per minute cost, webMethods.io needs to address that.
Another enhancement would be in OCR; currently, there is a huge demand for OCR capabilities. It would be perfect if webMethods.io had a built-in component for OCR, as this would be tested and allow customers to use it better than a third-party OCR application.
A special discount of at least 50% for old customers would allow us to expand our services and request more resources.
Apigee's product cost is quite high compared to other products.
Apigee is costlier compared to other solutions.
Apigee is high-priced, suitable for large enterprises where the benefit aligns with the cost.
Regarding the pricing and licensing of webMethods.io, I don't think it's expensive when compared with the features.
It provides all the necessary capabilities for current technologies, enabling communication and translation between protocols, along with supporting stringent security features.
Apigee's analytics capabilities aid in monitoring and optimizing APIs, which are also beneficial for our operations.
We rely on Elasticsearch to monitor traffic, which provides high visibility and control and surpasses Apigee in certain features.
If we want to make a REST API, SOAP, REST, or any other type, all kinds of things are put in one box and we can make anything we want to.
It facilitates the exposure of around 235 services through our platform to feed various government entities across the entire country.
I believe data transformation is exceptional in webMethods.io because they have an online database that can cache the database online.
| Product | Market Share (%) |
|---|---|
| Apigee | 8.8% |
| webMethods.io | 2.5% |
| Other | 88.7% |
| Company Size | Count |
|---|---|
| Small Business | 20 |
| Midsize Enterprise | 9 |
| Large Enterprise | 65 |
| Company Size | Count |
|---|---|
| Small Business | 23 |
| Midsize Enterprise | 11 |
| Large Enterprise | 64 |
Apigee is a platform for developing and managing APIs. Apigee offers an interface for your core services by wrapping them with a proxy layer which is then accessed by other developers. With Apigee, you can design and build APIs and then securely share their services and data without exposing any code.
Because app developers make HTTP requests to an API proxy rather than directly to your services, your services are separated from the developers. All the developer needs to know is the URL of the API proxy endpoint, necessary query parameters, authorization credentials (if they exist), and the response data format.
The API proxy isolates the app developer from your backend service. Therefore, you are free to change the service implementation if the public API remains consistent. By maintaining a consistent frontend API, existing client apps will continue to work regardless of changes on the backend.
Key capabilities of the Apigee API management platform include:
Reviews from Real Users:
Apigee stands out among its competitors for a number of reasons. Several major ones are its rich developer portal, its advanced analytics, and its central monitoring system.
Carlos R., a software architect at Caja Los Andes writes, “The central monitoring feature is the most valuable. It also provides security for the APIs and high availability for our use cases. Apigee is the best product in the industry in comparison to other API management solutions. It helps in fast development, which is a top point. It also supports a lot of industry standards and has excellent documentation.”
An associate vice president at a tech services company notes, “The analytics function and the developer portal are the two valuable features of Apigee. The analytics part is very good, and the developer portal is quite rich in features. The authentication mechanisms are quite easily built into Apigee, which is something that most of the other products have also now started supporting.”
webMethods.io Integration is a powerful integration platform as a service (iPaaS) that provides a combination of capabilities offered by ESBs, data integration systems, API management tools, and B2B gateways.
We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
