"A solid and mature API Management platform that helped us grow - but may not fit every long-term integration strategy"

Submitted

4.0
4.0
Overall User Rating

Product(s): Apigee API Management

Overall Comment:"We started using Google Apigee around five years ago when we began moving towards an API-first-strategy. At that time, it helped us bring structure and security to our API landscape and allowed us to manage multiple APIs across different teams and business units more consistently. The platform's built-in tools for monitoring, analytics, and policy management gave us good visibility into API performance and usage. Over time, however, as our integration requirements became more complex and we needed deeper connectivity options, we decided to migrate to other product. Even though we are no longer active Apigee users, it played an important role in our API journey and helped us mature our overall integration approach."

Lessons Learned

Description
Description

What do you like most about the product or service?

One of Apigee's biggest strengths was how it combined most of the essential API management capabilities in a single soltution. You can design, secure, deploy, and analyze APIs without having to rely on multiple tools. Security features like OAuth and traffic policies were straightforward to implement, and the built-in analytics provided valuable insights into usage patterns. Its integration with Google Cloud alo made it relatively easy to manage APIs across different environments.

Description
Description

What do you dislike most about the product or service?

When we first started with Apigee, the learning curve was quite steep, especially for teams without prior experience with API gateways. Over time, we also found that some of our advanced use cases - such as deep system integrations and complex hybrid deployments - were difficult to implement without significant customization. As our API ecosystem grew, the cost model also became a bigger consideration. Additionally, the user interface and developer portal, while functional, sometimes felt less intuitive than we expected.

Evaluation & Contracting

4.0
Description

Why did you purchase this product or service?

  • Drive innovation
  • Create internal/operational efficiencies
  • Drive revenue growth
  • Improve business process agility
  • Cost management
  • Improve supplier or partner relationships
  • Improve customer relations/service
  • Improve business process outcomes
  • Enhance decision making
Description

What were the key factors that drove your decision?

  • Product roadmap and future vision
  • Pre-existing relationships
  • Breadth of services
  • Strong services expertise
  • Strong user community
  • Overall cost
  • Financial/organizational viability
  • Strong consulting partnership
  • Product functionality and performance
Description

Which other vendors did you consider in your evaluation?

  • Microsoft
  • Amazon Web Services (AWS)
  • SEEBURGER
  • Salesforce
  • SAP
  • Kong
  • Gravitee.io
  • APIwiz
  • IBM
  • Oracle
  • IBM (Red Hat)
  • Postman

Integration & Deployment

4.0

Service & Support

5.0

Product Capabilities

4.0

Additional Context

Description

Deployment architecture

Hybrid Cloud and On-premises
Description

In which country(s) did your deployment take place?

Germany