Apigee Reviews

It is easy to use from a developer perspective and a customer perspective. 

It is easy to set up. It is on Google Platform, and there are multiple deployment models they support, which is great.

There should be an integrated continuous integration and continuous deployment approach with Apigee. Currently, for development at a more integrated level, you have set it up yourself.

It lacks the connectors and connectivity. That's something that would be good to have. 

I have been using this solution for 10 years.

I have not faced any stability issues.

Their support is good.

For on-premise, there is complexity, but the cloud version is easy to set up.

Its price is reasonable for the features they provide and the maturity of the platform.

I would rate it a nine out of ten.

We use Apigee an API gateway solution. It can be used in many areas or industries. For example, in Indian, the railway and finance sector, or in Australia, for the Oil Industry.

Apigee is a strong-featured solution. It leads in Gartner Quadrant ratings and it is a full-slated API solution that has the features that an API gateway requires.

I have been using Apigee for approximately three years.

Apigee has been stable.

I have found Apigee to be scalable.

We have more customers using Apigee than other API gateway solutions.

The technical support for Apigee is very good.

There is installation documentation available.

We have standard administrators teams for the deployment. We can also receive support from the Apogee team. If we are unsure of the requirement for deployment, we have one person from Apogee for two months and they will do the job and leave afterward.  

The price of Apigee could be less expensive. The solution can be purchased monthly or annually. 

I would recommend this solution to others, it is a good choice.

I rate Apigee a nine out of ten.

I'm a part of a service provider company, and we basically provide all kinds of services for our customers. One of the areas for which we provide services is API management. We work a lot with Apigee, and we have experience and a good team working with Apigee.

In terms of use cases, we've created a good marketplace for one of the clients. They are a logistics company, and they have a lot of vendors and partners with whom they work. So, we have created a marketplace where the vendor's partners can integrate for their shipments and other things. They can integrate their applications into this marketplace.

We have also implemented developer portals where we do the onboarding of developers. They can create their code SDKs, etc.

Currently, we are at a customer site, and we are migrating the on-premise version H to Apigee X, which is the latest one.

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.

iPaaS is something that we would like to see. For example, MuleSoft is kind of an integrated platform as a service (iPaaS), and it provides a lot of out-of-the-box connectors and other such things. This is where Apigee lacks. I'm not sure if that's the roadmap for Apigee, but any improvements on those lines would be helpful where things become easier to implement.

It has been four to five years.

It is definitely stable. Performance-wise, we have not seen any major bottlenecks. What we have realized is that the performance is not just because of the tool itself. If you take any API management tool, the performance also depends on the way the integrations are done. So, if implemented correctly, performance is not really an issue.

With the SaaS model, scalability is there. 

It is suitable for large companies because it is a bit pricey. It is definitely not for small companies, but it might be suitable for medium companies.

We have not been in touch with them much because we mostly have done development, but they do provide good support. Their support during the initial design architecture phase is also very good. So, if you have bought the licenses, they do provide an architect to come in and define the whole architecture. That way, the support is good.

We work on multiple API management tools based on the requirement of a particular customer. We have worked on Apigee, Dotcom, MuleSoft, to name a few.

Managing an on-premise setup themselves can be a huge overhead for customers. Apigee, I believe, releases patches very frequently, and those upgrades and maintenance activities are quite an overhead. Having said that, it has good support. They provide a lot of scripts through which the installation and other things can be automated, but obviously, we have to tailor those to our needs. On-premise is definitely a little bit of overhead. We have to have a team to manage that, but now with Apigee X going on SaaS, most of the implementations are on SaaS. So, this overhead is minimized a lot, and you just have to do the configurations.

It is a bit on the expensive side. Its licensing cost is a bit high, and that's where we've seen people going back on their decisions.

In the latest version of Apigee, they've broadened the support for socket communication, which was previously missing in Apigee Hybrid.

I wouldn't recommend Apigee for simple situations because sometimes, it does become an overhead. It is overkill for simple situations. If you have very complex scenarios where you are trying to embark on a cloud journey and you still have systems on-premise or some systems are hosted on some other cloud and you want to do an integration, Apigee is really good. It provides support for the mesh architecture, and with that, it becomes quite easy.

The advice that we normally give is that when you are starting on an Apigee journey, you should not think of it just as an API management tool. We try to give it as an enterprise API platform that a large customer with different lines and businesses, such as a bank, would eventually leverage as a whole. You should not treat it in a way where only a particular group is using Apigee. It is an enterprise platform. So, you should treat it as a platform.

I would rate Apigee an eight out of 10.

Apigee is a platform for developing and managing APIs.

Overall the solution works well, it is one of the best solutions on the market. There is plenty of support documentation available.

The Apigee cloud admin UI could be more user-friendly by adding a few more features.

I have been working with Apigee for one and a half years.

The solution is highly stable.

We have built an API platform o over 2,000 different partners and all of them are using the gateways.

The technical support is very good.

The installation was not difficult.

I rate Apigee an eight out of ten.

The solution is primarily used for developing and publishing internally IPA (80% of the time). The other 20% of the time the product is used to create and develop an ecosystem with various partners.

Our clients would best be able to speak to that. As we just assist them in the process, it's not on us to divulge such details.

The developer portal is very useful to customers.

The mediation aspect of the solution is very good.

Technical support is pretty good. We are pretty happy with their service overall.

The solution is flexible and offers good customization capabilities.

In general, the product isn't too technical.

The pricing of the solution could be improved upon. We'd like it if it was less costly.

The solution needs something that supports real-time streaming.

Our customers are users of the solution; we don't use it directly.

There are close to 60 users at the moment. They are from the development team, the application team, and managers mostly.

We have not spoken to our clients about increasing usage or scaling the product. I am unsure of their future plans in that regard.

We have used technical support in the past. They have been pretty helpful. There's a mission team that deals with them mostly. I don't have much information beyond that.

I am unsure if our clients used a different solution previously. I don't have access to that information.

The initial setup is pretty straightforward. It's not overly complex. A company shouldn't have any issues setting everything up.

We did a hybrid deployment, the entire process took us less than a month. It's not a long, drawn-out process.

We are consultants. We can assist our clients with the deployment process if they need help.

The cost structure could be adjusted to make the pricing more reasonable. If they improved, likely they would ope themselves to many more markets.

We don't directly use the solution we are a service company so we help our customers use the product. We are consultants.

I can't say which version of the solution we're using at this time.

I'd advise other organizations that you have value any solution beyond a price comparison with other API management solutions. You will need to look at APS strategies needed in the organization and the importance of creating API products. Once that strategy is laid out you can put the right resources in place. Basically, everyone needs to have a plan first before investing in an API management solution.

In terms of Apigee, more exposure of the platform to wider stakeholders will definitely help in modeling best practice principles into EPA communication and evolution.

I would rate the product at a nine out of ten.

There's always room for improvement. However, it's not heavily technical. There's a lot of flexibility for developers to bring in customization. It's not rigid. If you have a team looking at APS cases, products, and you, how a corresponding APA team strategy, Apigee as a platform is very good. It's quite a comprehensive option.

There are plenty of use cases. My clients were using for internal API management as well as external API management, including subscription models and pre-payment models.  Essentially, it was for using internal data and selling external data.

Apigee gives you plenty of opportunities to set up your workspace depending on how you want to manage your APIs. This is something that the majority of clients like.

What my clients don't like is that the on-premises solution is not being treated and maintained as well as the cloud solution.

I know that they are working on the integration of no-code and low-code solutions to make it more accessible to users that have no technical background. This is something that I find very interesting and they should continue working on that.

I was working at a client site where Apigee was being used. I have two years of experience in this environment.

Stability-wise, I haven't observed any major issues with the product.

It is pretty scalable and we haven't reached any limits so far. We have thousands of users. There are a few hundred active internal users, a few thousand developers, and far more external users.

I haven't been involved in any interaction with support.

I would like to see the implementation of further options for billing because as it is now, the opportunities you have in terms of a package are limited. You don't have the choice of too many billing models, which is an issue that needs to be worked on.

My clients have a monthly pricing model.

If you compare this to Microsoft Azure API Management, Apigee is a bit better because Microsoft has no real built-in solution.

I would rate this solution an eight out of ten.

We are using Apigee as the API gateway. We also use it for our preparation. We use the API for security and a lot of other tasks. Our customer use cases don't have any legacy systems. We're using Apigee, however, Apigee doesn't provide for a subscribe-publisher capability. It meant Kafka was just to provide the matching capabilities of Apigee. However, mainly we consider this solution as the API gateway and management system.

The security provided by the solution is excellent. 

It provides for an on-prem setup. That's very important for us. As the regulation of communication policies. To be able to provide the telecom companies that tool and install their products on-prem for easy management via cloud inside Saudi Arabia is great. 

The solution provides very good mitigation capabilities.

The integration could be improved within the solution. There is a need to pay more attention to this. 

It would be ideal if the solution could provide publishing capabilities as API middleware.

We've just been using the product for a few months for a new project we are working on. It hasn't been that long.

The solution provides a very stable solution for us.

Our mother company has been using Apigee for maybe five years now. I talk with them about making assessments for selecting an API gateway solution. They didn't have any issues with scalability or monitoring. Apigee was perfect for them. We didn't face any issue with it in terms of scalability or even tenability. It's very easy to scale. 

As an integrator, we have about five different clients who use this solution. They have a different number of users.

The technical support for the solution is pretty good. We're satisfied with the level of support Google provides. They are knowledgeable and responsive.

The initial setup isn't complex. The setup configuration offers a very simple approach for developing and deploying services in Apigee. It's straightforward. It's easy for our developers to apply a lot of services while offering a faster time to market.

Apigee is not cheap. It's expensive. At the same time, our company is already buying an enterprise license so any company inside the group can use it. In general, however, it's pricey.  

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

Overall, I would rate the solution nine out of ten.

Whether of not this is a good solution for a company depends on a lot of criteria. The budget itself needs to be considered, for example. Apigee is perfect. They provide good support. People from Google are very cooperative as well. They listen for feedback on features. 

They don't provide a partnership to just any company. You need strong criteria to get a partnership and to be able to support and feature the license. I like this, to be honest with you. That's already making our implementation easy. We're only dealing with companies that know how to do work in Apigee setup and installation and configuration and they have a long history of providing strong criteria. In general, I recommend Apigee.

Primarily we do the Apigee implementations for the customer. We are more like a service company. We sell the product and consult with the clients about their needs. There are options for the API gateways and we look at the client's requirements, their budgeting, and then we deliver and install the new solution.  

Apigee makes it nice and easy for the clients and those using the product to access the product's help resources.  

It would help with Apigee if we could make a list of our assets. If the client knows more about all the extensions they can use to work with through the Google cloud and we have an extensions database it would be easier to let them know what is available and we could do more to recommend Apigee for all different kinds of customer needs.  

I have been working with Apigee at this company for the past three years.  

The stability of the product is not an issue.  

We have not had any issues with the product scalability.  

We are actually partners with Google, so we get the best support from them.  

I did have some previous experience with other products in this category before Apigee, like MuleSoft. The main differences between Apigee and MuleSoft are that Apigee is more lightweight and the licensing is also lesser than the MuleSoft. Based on the use case of big clients, the ones who want more services can get them and because the Apigee solution is more lightweight it offers more possibilities for them to use API solutions.  

With Apigee you can bring in some adapters to work with things like business rule engines. So those might create more standardization and help make the investment in Apigee more valuable.  

I tried to do the initial installation and setup a couple of times. It is straight forward and easy. It is just done by calling a couple of CMA (Connection Manager Agent) commands and you can get it up and running.  

What I would recommend for clients who are considering this type of solution depends on the customer's use cases. Since we are Google partners we generally go with Apigee as the solution. But if the client insists that there has to be a lot of orchestration and other integrations need to be done, then we will go with MuleSoft.  

On a scale from one to ten where one is the worst and ten is the best, I would rate Apigee as somewhere around an eight.