Apigee Reviews

Our organization currently has twenty Apigee end-users. We use the solution for API management of financial and e-commerce domains.

Apigee is relatively easy to use for developers.

I have been using Apigee for six years.

Apigee is a stable solution.

The SaaS version of Apigee is quite scalable. The hybrid version is also scalable depending on your requirements.

I am satisfied with the support offered by Apigee.

The initial setup is not straightforward, particularly for hybrid solutions. It is easier to manage the managed services or SaaS-based versions.

The implementation takes time. The production setup includes TLS among other things, and the management and operationalizing take time as well.

We implemented the solution in-house.

Apigee's licensing costs more than other solutions. Some add-on packages are sold separately. For example, monitoring is not included in the standard package of Apigee Edge.

Anyone considering Apigee as a solution should start small and increase usage with experience. Start with a centralized small team and expand based upon the maturity model that Apigee has and recommends. I would rate this solution an eight out of ten.

We use the Apigee platform for analytics, specifically for retail customers. We have used this solution to enhance the capability of some of our legacy systems. We have 300 users on this platform. 

One of the best parts of this solution is the implementation as we did not need to use code or out-of-box policies. When it comes to the cloud-based architecture, there is a high level of reliability.

When it comes to the rate limit, we don't have a specific category for rate limits for a particular customer.

I have been using Apigee for more than seven years.

This is a stable solution. 

This is a scalable solution. 

The customer support for this solution is very good. We have received immediate responses from the technical team.

Neutral

The initial setup is not that straightforward. 

This solution offers annual licensing.

I would recommend this solution for API management and is one of the best on the market.

I would rate it an eight out of ten.

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.

One feature I found most valuable in Apigee is its simplicity. All features remain the same in all of the API tools, and I have experience with IBM API Connect and Apigee, but Apigee is easier to work with, plus the learning curve is not that steep.

Another thing I like about this solution is that the support is really good, and this gives Apigee advantage over other providers.

I like the development feature of Apigee. You will find it easier to work with Apigee than IBM API Connect.

We found a glitch in Apigee, and we raised it with them: It's the response overlapping from the API with high traffic.

They have been working on that, and they have shared a patch with us, but I'm not sure if that is publicly available for all users. It was made available to our organization: one single patch of Apigee.

I've been using Apigee for over two years, and I've used it in the last 12 months.

This product is is stable.

Apigee is a scalable product.

Technical support for Apigee is very good.

I used IBM API Connect, but found it easier to work with Apigee.

I evaluated IBM API Connect.

I'm both a user and an integrator of Apigee.

We have deployments both on-premises and via cloud. We use both, like Google SaaS and the on-premises solution.

We are a consultant for different organizations. Some organizations prefer on-premises deployment, with everything on their private cloud, and this means they use the older version of Apigee. Some organizations use the latest version because they're using Google SaaS directly.

My advice to people who are looking into implementing Apigee in their organization: If it fits your budget, then it is a good product. If it fits into your ecosystem, e.g. you are in that ecosystem, not in IBM or other CA-based ones, Apigee is something you can go for. It is a good platform.

I haven't worked with CA, and there are others, e.g. MuleSoft, so I can't comment on how Apigee compares with those competitors, but compared to IBM API Connect, Apigee is a good one.

I'm rating Apigee eight over ten. There's still room for improvement, so it's an eight for me.

Apigee is a platform for API management.

Apigee is a pioneer in the industry and has good features and functionalities. It is a good tool for API management and it has more advancements than all other tools in the market in certain areas.

It has many features, such as flexibility, coding writing, and JavaScripting.

I have been using Apigee for approximately four years.

Apigee is stable. In the entire API management world, I feel this is one of the best tools for pure API management. If there are any orchestrations or business processes to be involved, then Mulesoft or Boomi can be used, but comparatively, all the security and governance policies that are available on the dashboards and the reports make Apigee the best tool for pure API management.

The installation is good. I won't say it is complex, but it has many configurations and types of policies that are available. However, it can be easily done.

Apigee is slightly expensive, but again, it can depend on the type of usage. All things considered, it is slightly expensive. 

AWS is winning in the cost category, they have many packages and services but when using all these services together I am not sure what the cost would be.

I have evaluated Mulesoft and Boomi. I have found these two solutions are being used secondarily to Apigee. Additionally, AWS and Azure's Gateways are becoming popular in the market. From the cost perspective, in the two years, AWS gateway is widely being used. These four solutions are widely being used in the market but Apigee is much far ahead than all other tools.

AWS and Apigee have similar features. I don't see any significant change in the difference at the moment. The choice is more about convenience and cost.

I rate Apigee an eight 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.

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.

We use Apigee to share open data for the government. It was a pilot project for one of the  government teams who wanted to start the journey of open data.

The capabilities are very powerful.

Support of integration is what is most challenging in Apigee, as well as the complexity of the components. When setting up an environment, you have many components with open-source content.

When there is an update on a new version or an automatic update, you have to be present and double-check that the update is reflected in the environment with no issues.

The implementation should be easier.

We implemented Apigee six months ago.

Apigee is stable. We have approximately 1,000 users.

This is a scalable solution.

Technical support is very good.

To construct the environment, can take two to three weeks.

The presentation is based on the business and can be done in three to four months.

The iicense is subscription-based.

I would recommend this solution to others who are interested in using it.

It's a very good product. I would rate Apigee a ten out of ten.

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.

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.