Apigee Reviews

The solution is primarily used for managing the interactions between channels, customer experience systems, and other systems.

The API management on the solution is very good. It's likely the most valuable aspect of the solution for us.

The pricing is okay.

It is possible to scale the solution.

The solution isn't really lacking any features.

The user interface could be better. It could be easier to navigate and more user-friendly.

The pricing model could be improved. Things can get expensive for larger companies, or organizations that are growing.

The solution should offer more training to partners. It would help in the understanding of the product by quite a bit.

I've been using the solution for three or four years at this point. It's been a while.

The stability of the solution is okay. We haven't run into any issues.

Larger customers typically have 14-20 users on the product.

For large transactions, the commercial model is proving to be a constraint to some of our customers. For example, they're asking, when the scale grows, the commercial option becomes expensive. Some of our customers, for example, ask for an alternative approach due to the cost of the commercial model.

That said, you can scale. It's not a challenge in terms of doing it, it's just a challenge in terms of cost.

I've never really had to contact technical support, and therefore can't really speak to their level of assistance.

Typically, if I need assistance, I turn to Google or forums and I seek help online that way.

The initial setup is straightforward. It's not overly complex. A company shouldn't run into issues setting it up and rolling it out.

I'm part of a services organization. There are various developers, and Apigee users tend to be more than 300 people from our organization. In terms of support, there are 40 people. These are split across different customer organizations.

We are an integrator and can implement the solution for our clients.

The pricing starts off okay, however, for enterprise-level organizations, or companies that are scaling, the price can rise and become costly. If you don't scale too big, the pricing is fair.

We are systems integrators. We aren't just end-users.

In general, I would rate this solution at an eight out of ten. If the pricing in relation to scaling was better, or if they offered better partner training, I would rate them higher. There aren't really any features lacking and we're largely happy with the product.

We are working on some client POC where we have all the workloads deployed on Google Cloud. We wanted a gateway that was more like an API Management tool. We wanted to manage all our APIs centrally in one place. For example, we can route the traffic. We can limit, we can perform throttling, we can have the security checks like the authentication mechanism implemented centrally. We can also have a reverse proxy to our service endpoint.

I like implementing different policies, for example, rate-limiting policy. We can create a custom rate-limiting policy, and we can have an application-specific rate-limiting policy. That's what we're implementing or using, and I like that feature.

More documentation on the Open Banking Standard will help. For example, WSO2 supports the Open Banking API, but I can't find relevant documentation from Apigee. I'm not sure whether Apigee even supports the Open Banking Standard. If they do, then I think they have left out the documentation for that. For example, WSO2 has extensive documentation and training available to everyone. In that sense, I think, Apigee can improve.

I've been using Apigee for a few months.

It's a stable product. It's easy to manage, and we have implemented it for our production deployment.

Apigee is a scalable solution.

I never tried reaching out to tech support because the documentation is good. The documentation is available, and there is some training available on Udemy and the product site. These nicely describe how to deploy or set up different policies, which was enough for us.

The installation is straightforward. You just need to get a license for Apigee and then configure the reverse proxy. Once you have the reverse proxy configured, you have to set up whatever policies you want. One or two guys were able to install, deploy, and host our reverse proxy for our endpoint within a day.

We went through the documentation and the website and deployed the solution ourselves.

All these technologies are using Google Cloud for hosting our microservices, and we trialed Apigee. We were also using WSO2, an open-source API management tool, but as everything is on Google Cloud, we chose Apigee.

If your workload is already deployed on Google Cloud, integration is very easy. Even if your services are hosted in some other cloud, like AWS, I think you can use Apigee, but I haven't tried that approach. 

On a scale from one to ten, I would give Apigee a seven. 

We have an API, which I developed using multiple languages and different applications. We have a lot of applications, and they have their individual APIs. We create a proxy for those applications in Apigee, and we expose those proxies to access those APIs.

Apigee didn't exactly improve our organization, but it fulfilled a requirement. There are a few tools in the marketplace, but we thought Apigee was the best for our use case.

Apigee is very easy to use, and you can code in any language, like JavaScript, Java, or any other language. That's really helpful. It's cloud-based, so there's no need for any installation.

Access restrictions can be improved. For example, you can't restrict access to some people or some groups. You have to give them total access. 

I've been using Apigee for about three months. 

Apigee is a stable solution.

I think it depends on your license, but it's highly scalable.

The initial setup is straightforward. We don't need a lot of training for the developers to start working, just a few days at most. It's very easy to start with, and the development effort is also a lot less.

For potential users of Apigee, I'd tell them there's a free version if they want to check it out and have a trial. 

On a scale from one to ten, I would give Apigee an eight.

My current job is to compare all the different API gateways and to create a report for management. We use this tool primarily to secure our API. We have a set of API from our four businesses and we're trying to apply these APIs to multiple applications. For example, third parties can leverage our APIs built to their own solutions and applications and we build applications on top of these APIs. I make the system available like a mobile app. Primarily the API management for the entire ecosystem of AP that we are building and the DGPS are providing, have varied capabilities across the organization. Apigee also acts as a proxy, everything is done within that. 

We also leverage the developer portal of Apigee as a main feature, which can be given to outside customers by third parties to build their own applications around our API. One of the standout features of Apigee is the different PolyPhaser functions that we use. For example, we use throttling, encryption/decryption and we also use external AP integration with PV.2 I'm a senior architect and big data engineer and we are customers of Apigee. 

I like the functionality of this solution. 

The cost of this solution could be improved and it would be better if it were on private cloud. 

The solution is stable. 

The solution is scalable. 

I'm not directly involved in the technical support aspect, but I've heard that the technical team is excellent. They provide support from the beginning until you completely run all your setups.

This solution is much easier to set up compared to any of the other API gateway solutions. There is extensive documentation available.

I would go with Apigee if you have the money. It will give you enough APIs for management. If you're looking simply for one functionality then I wouldn't recommend Apigee.

I would rate this solution an eight out of 10. 

It is a Google cloud solution for API management and analytics.  

I have not had the opportunity to completely explore the product's capabilities in the time that we have been using it. But I can say that the customization is really vast and it is a really good feature built into the product. I can customize different authentication methods and methods for authorization. I can also use redaction. So security is flexible to our needs and it works well.  

It is a user-friendly solution, but it would help if Google could provide a container-based solution instead of just a standalone one. With a container-based deployment and support for Terraform, it would be better for our deployments and that would be great. Right now we have to configure different areas manually. Some areas can be automated, but the deployments are not as fully automated as they could be otherwise. 

so, they currently have a software as a service offering or a standalone offering. I want to see something like a hybrid cloud deployment. I also want to see a private cloud deployment. 

We are still building out the environment. We are running four environments until we accept that it is fully tested. So we are not live yet and we will really go live and into production sometime in the first quarter of next year. But we have been using Apigee within the last 12 months for testing purposes.  

The scalability of the product is good. Our use case is right now is applied in only one environment. When we are about to go to production, we will probably do high-availability testing with a dual environment so we can come up with any potential scalability issues. But for now, we have not really touched that area in our testing.  

We do have a lot of people using Apigee already. This is the primary gateway for us to talk to external applications. I would say that services around 800- 900 applications which are using the gateways. That is also involving many teams and end-users who access those applications.  

My recommendation for installations is that the product installation, set up and delivery process could be improved. It is straightforward in the initial steps. The part which is automated by Google is very straightforward. The remaining part, we have to do manually. The remaining components have to be manually configured. If Google were to do a container offering of this solution, then adopting it would be seamless because everything would be able to be automated.  

I would say that it currently takes too long to set up and deploy and that it is not as short a time to complete the process as it should be. It is more mediocre, somewhere in the middle, and has moderate difficulty instead of being seamless and simple.  

We did not have to use an integrator, reseller, or a consultant for deployment. It was all done in house by our own teams.  

We tried Axway API gateway and we also tried MuleSoft. We found that these solutions did not fit our scenario as well as Apigee because our scenario is a very special scenario where we want to keep everything that we already have on board. In our current situation, we have big AWS (Amazon Web Services) accounts and a big AWS footprint. So we want to also be able to use AWS for Apigee hosting. That is where our environment and needs become a little bit of a custom scenario. Apigee works for us in this scenario and that is why we ultimately went with Apigee over other products.  

I would definitely recommend this product over any other products available in the market in this category. It has all the features necessary to work in anything from a basic scenario to advanced applications. So I find that everything in it is flexible and available in this one product. Because of that I highly recommend it to anyone.  

On a scale of one to ten (where one is the worst and ten is the best), I would rate Apigee around an eight out-of-ten.  

We primarily use the solution for all of our security. There are a few use cases for us where we use it to protect API to third parties.

The solution, overall, is quite good.

The product has a few restrictions I'd prefer weren't there.

We have trouble finding use cases. For example, when we google "data locator" we can't find a use case scenario at all. We can't find more than, approximately, five use cases, however, we need more.

We needed to do more than 20 configurations, and we weren't able to do that as the limit is 20 on the solution.

The solution tends to hide the limitations to keep selling the product. I can't blame them for doing it, however, it makes it difficult for those of us who eventually sign on.

The solution is expensive.

I've been dealing with the solution for close to three years at this point.

The stability of the solution is good. There aren't issues surrounding bugs or glitches. We don't find that it crashes or freezes. It's pretty reliable.

The scalability of the solution is okay. If a company needs to scale it, it should be able to do so.

Currently, we only have about ten people on our team that use it.

We haven't found the technical support to be that good, to be honest. We're not completely satisfied with the level of service.

We're currently using IBM Connect as well as Azure. Functionality-wise, there aren't too many differences. One is on-premises, however, therefore it's really difficult to compare both together. With IBM, you have to maintain a few more things. There are more administrative tasks.

The initial setup wasn't straightforward. It was complex due to the fact that Apigee didn't have any integrations and we had IBM APA Connect Resources.

There were many things we weren't told earlier. Once you clear certain items you can't change the name, for example. There were a few other items, like monitoring, which had a limited number of configurations which was an issue.

Deployment was fairly quick. It only took five minutes or so.

The solution is not a cheap product. Licensing can be quite expensive.

Our contract is around $2 million for three years.

We don't have a clear picture how the billing works. We have one service package of one size and yet we don't have a clear picture of the purchase or the status or if they will charge more due to earlier limits on services. The solution needs to make licensing more clear. Even if they charged us $10,000 or even $20,000 more but they were clear about the what and the why, we'd be okay with that. We'd just like to know.

We're just a customer. We don't have a business relationship with the company.

We are removing our IBM products and transition completely over to Apigee.

We have Azure's API as well. In next one year or two year, we are going to dissolve IBM API Connect as well as Azure CIM and move everything to Apigee.

Overall, on a scale from one to ten, I'd rate Apigee at an eight. We'd rate it higher, however, they aren't clear on their offering. We just want everything automated and easy. The cost is not the issue. The lack of information is.

I'd recommend the solution. It's a nice product and companies should go ahead with it, so long as they are okay with the pricing, as it is rather expensive. If a company is cost-consious, IBM API Connect may be better as the licensing costs are lower.

We've got quite a large technology footprint and I'm looking after the integration of our banking platform with our payment systems.

The REST API allows for faster user engagement.

The flexibility allows you to quickly run a cloud-native application architecture.

The ability to work across different management solutions in a plug and play fashion would make it easier for faster uptake.

Pricing is an area that can be improved, as it is a little on the higher side. It is more expensive when you compare to open-source products or other vendors.

I think it would be helpful if Apigee had support for voice-activated activities, rather than having to type.

More intelligence in terms of being able to learn from previous activities would be a good addition in the future.

I have been using Apigee for about two years.

Apigee is used on a daily basis in our payment systems.

It has performed relatively well from a scalability perspective.

We have about 15 users in the company. They are a mixture of engineers, architects, and administrators, with the majority being architects.

In cases where we have a problem and need support, we have an agreement in place with the vendor to help us navigate through it. They are good and respond to our issues quickly.

Apigee was our first choice for this type of product.

The initial setup is of medium complexity. End-to-end, we took about a week to get everything ready. This included the account, the proxies, the target endpoints, etc.

We received assistance from the vendor for our implementation.

Our in-house team is responsible for routine maintenance. This includes backup support, uptime support, patching, applying of certificates, etc. It is an ongoing activity and we also work with the business to continuously improve the integration, so that they are getting the value of the capability of Apigee.

My understanding is that there are costs in addition to the standard licensing fees.

My advice for anybody who is considering Apigee is to first do research and an analysis of what they want to use it for, including specific use cases. It is a good tool but it is important to have well-defined requirements to avoid a high implementation cost and rework.

The requirements have to be very well documented and understood by all parties, especially those who will be involved in implementing it. Following this approach is an important step to getting a good return on investment.

I would rate this solution an eight out of ten.

We use Apigee every day. Because we have a backend system, we use Apigee to capture and track all of our transactions and for monitoring calls, which is the target for our client service. We then use this information to create a report and provide a price for each transaction. For this reason, we created a proxy that we use as an integration layer, like API management, which helps build applications. For that reason, each and every call goes through Apigee so that we can track and capture all of the information.

There are a few features that are quite interesting. We can provide our API developer with an API proxy to the developer portal, which comes in handy. There are also some interesting policies, like authentication where we normally provide any code and quotas and rate limit policies for protection. The administration and monitoring features are also quite useful as you can receive alerts and notifications and monitor them on a virtual dashboard. There are just a lot of security features in general.

With Apigee, we can easily monitor applications, and our core IT team informed me that installing upgrades is very simple. We also have a portal where we can share our proxies with the convenors, which is quite useful. 

When compared with other products and tools in the market like MuleSoft or other API management solutions, I see some lagging in regards to integration capacity — where we don't have all of the connectors. It's not the perfect ESB, it's only for API management solutions. For example, MuleSoft will provide you with the API management solution as well as ESB, allowing you to integrate with large, complex IT systems. So, there is some lagging there that needs to be fixed. 

The main area they should improve is the integration capability. They should have useful connectors that we can use to provide code so that we can integrate with other systems. This needs to be improved.

When compared to other products, such as MuleSoft and other tools in the market, Apigee has some lagging issues. 

Over the last three years, we haven't had any issues with the stability, both on-premise and on the cloud. It's a stable solution. We haven't experienced any error-value from the product.

Product-wise, we don't have any technical support, our IT team takes care of it. We also have a number of applications we are managing, but only two recruiters are monitoring them.

It's easy to create proxies in Apigee. Compared to other integration tools, we can quickly and easily export any APIs in Apigee, which saves us a lot of time. 

The setup was taken care of by our core IT team, I was part of the development team so all activities relating to the setup, updates, and customer service were handled by the core IT team.

We would definitely recommend Apigee. You can use Apigee to create proxies (and share API proxies with consumers), monitor calls, and provide security for particular endpoints. We have a complete telephone portal under Apigee, I would recommend it.

I would give Apigee a rating of seven or eight out of ten. The API moderation, administration monitoring, product architecture, infrastructure, and overall quality is good. The only area lagging is integration capability.