Apigee Reviews

We use Apigee in health care, where multiple databases and applications need API. So far, there has been no standardization, but in the near future, there will be standardization towards the FHIR, which will drive interoperability and integration.

Apigee is an easy-to-use solution.

The solution’s scalability could be improved.

Apigee is a stable solution.

The solution’s technical support is good.

It is easy to deploy Apigee from one vendor, but if you are talking about multiple APIs, then it becomes complex. Then, you have to wait for the standardization efforts.

The solution’s pricing could be more competitive.

Apigee is used by one of the largest healthcare groups, which has over 50 hospitals, and each hospital has 50 to 60 applications.

I would recommend Apigee to other users.

Overall, I rate Apigee a nine out of ten.

We use the solution as a platform to integrate different APIs and provide authentication, authorization, and performance security services.

The solution's most valuable feature is its ability to integrate APIs for various industrial sectors, including telecom, banks, and multinational companies.

They should improve the solution's monitoring tools for on-premises environments. Also, they should make all the essential features available for the private cloud.

I have been using the solution for more than five years.

The solution is highly scalable. I rate its scalability as a ten.

I rate the solution's initial setup process as a seven.

The solution is advanced. It works efficiently compared to other solutions, such as MuleSoft. I highly recommend it out of all the integration platforms. I rate it as an eight.

My company works mainly in the BFSI domain. The tool helps us to build, manage, and run the APIs. 

The tool is one of the earliest API management products and is good. It reduces the Time To Market aspects of products. 

I would like to see better integration and some architectural improvements in future releases of the solution. 

I have been working with the solution for more than six years. 

The product is stable and I would rate its stability a nine of ten. 

I would rate the product's scalability an eight out of ten. 

Google's tech support team is helpful in terms of knowledge transfer. 

Positive

The tool's setup is very simple. You would need around 50 people to maintain the solution. 

The tool offers good returns on investment. 

The product's pricing is fair. You need to pay additional costs for the support. 

I would rate the product an eight out of ten. 

We primarily use the solution for API management. We use the solution with open banking, and we are managing our customer's cloud, on-premises, and Apigee environments. 

The solution is great in general. There are many categories of APIs that need to be maintained. It helps maintain and add rules to manage open banking. 

The solution is stable.

The initial setup isn't too complex.

It can expand well. Google seems to be moving into the cloud more than on-premises and the cloud makes scaling easier.

Apigee deals with APIs. However, most of our clients need more tailoring done to the solution.

Google isn't enthusiastic about supporting older versions. Google is now trying to move all of its clients to X within the cloud. However, some still want on-premises. 

I've been using the solution for about four years. I've used it for a while. 

The solution is stable. However, it depends on the release, the customer, and the sophistication of the infrastructure. 

We have had some issues with bugs in the product itself. 

The solution is scalable.

We have three banking clients on the solution. 

The amount of users depends on the customer. Some use it internally. Others expose the API to clients. Some have more than a billion APIs. Some have less. 

The technical support is not the best. It does depend on the size of the customer. Larger customers tend to get more attention. 

The ease of setup depends on the level of sophistication of the clients. It can be rather simple; however, the more complex the infrastructure, the more difficult the setup can be. 

We do both cloud and on-premises deployments. The length of deployment depends on the customer. It depends on the kind of network or the organization. It can take a few months up to a year.

We have a strong knowledge of the flow and the templates. For us, it's pretty straightforward. 

There is a team of six people that can assist with deployment and consulting with clients.

There are different models that customers can choose from. They have a subscription model. 

I'm a consultant. 

We are using a few different versions of the solution.

I'd recommend the solution to others.

It'd rate the solution eight out of ten. 

We are resellers of Apigee and also use it internally. The most common use case is monetization for the APIs. I'm the sales manager and we are resellers of Apigee.

The ability to convert from language to language using the same tool without needing different developer teams to deploy is a valuable feature. It doesn't require a lot of skill to run Apigee and the security features are good. This is a powerful tool for API management. 

The only disadvantage with Apigee is that they lack market presence. I think they may have limited resources. IBM's strategy is stronger on the marketing level. 

I believe they're working on adding some integration features that are currently lacking. 

I've been using this solution for three years. 

The solution is very stable even in very complicated environments. 

The solution is scalable and it's great for enterprise companies.

Technical support is good. Google team has many teams can support it. And there is a lot of partners ecosystem who understand and implement and support strategy as well.

I previously worked with IBM Connect but I prefer Apigee. It provides all the features and requirements for AI management.

The initial setup is very straightforward and can be done by anyone. 

The licensing cost is very reasonable and it gives you unlimited transactions.

I would recommend testing this solution for a month or so. It's easy to implement and easy to use. I rate the solution nine out of 10 - the one point reduction is because of the marketing strategy. 

Our primary use case is for security but also the mediation that goes with it.

The most valuable feature is monetization.

I would like to see SOAP services and socket-based connectivity developed. Apigee is known for exposing the REST API but not the SOAP API. Our clients are requesting these two features and we do have a workaround we use, but an upgrade in these two areas would be great. I would like to see more integration for example Enterprise Service Bus and this will help Apigee gain more popularity.

I have been working with Apigee for the past six years.

Apigee is a stable product. We have had existing customers for the past four or five years now.  

Technical support is alright but I have mixed criticism. Sometimes you get answers very quickly and on time, but in some scenarios when there is a product issue it takes time. If there is anything that is not implemented and they need some time to implement it, then it takes them months. If the error is something that is a known issue they reply back quickly.

Apigee is more straightforward and flexible, with implementation and designing. Other products currently on the market are more complex overall to sustain. The time it took us to set up was around two to three months.

There is one main reason we went with Apigee and that is the importance of the Gartner and Forester ratings. Apigee is on top of all the Gartner and Forrester ratings. The other reason is because of the smooth operational perspective.

If customers are trying to do long-term planning, and want to apply monetization on their APIs, then Apigee will be the best in this situation. I would rate Apigee a nine out of ten.

We want to sell API products and if you want to market the API product that you are building, then definitely you can go for the Apigee or any API product, but if you are in Google Cloud, definitely you can go for Apigee because only Apigee offers current cloud.

The most valuable feature is the API gateway.

I have heard there maybe be some security issues that need to be addressed. If this is the situation I would encourage taking a look at the security matters.

I have been using Apigee for the past two years.

There is good stability with Apigee

Apigee is scalable and we have around one thousand customers currently.

Technical support is good with everything.

Positive

The initial setup is extremely straightforward and not complex at all.

You can do the deployment usually in one month with the documentation provided and it can be done in-house.

Apigee has several different licenses you can obtain depending on your needs.

Previously, I had used IBM Data Power.

I would rate Apigee an eight out of ten.

Apigee brings a lot of projects, including development projects. For example, when an oil company is swiping a card in the palm station for payment of oil. As it swipes, it hits the database, and Apigee manages the entire process with the help of dedicated proxies. Managing those proxies is very easy, and Apigee makes proxy management very simple.

We have found APA management and API health monitoring valuable.

The solution can be improved by simplifying the account creation process.

We have been using the solution for a year and a half and are currently using version eight.

The solution is stable.

The solution is scalable, and multiple users utilize it in our organization.

I rate customer service and support as six out of ten.

Neutral

We previously did not use any other solutions.

I rate the complexity of the initial setup as medium. The deployment method is based on the company's contract, and approximately ten people are required for deployment.

We have seen a return on investment.

I rate the solution a seven out of ten. The solution is good, but the account simplification process can be improved. I advise users considering this solution to go for it because it has many API management features, including the health log error-finding tool and developing a new proxy.