Apigee Reviews

Our primary use case is for building an open API platform for a financial services company, and we needed something that could do the task quickly.

The most valuable features are low-code play, quick packaging, and production.

I would like to see the support improved. I think the time frame should be shorter for responses when it comes to technical support. This is not the ideal situation you want to be in when you need support.

I have been using Apigee for the past four years.

The stability is definitely close to a ten on a scale of one to ten.

On a scale of one to ten, I would rate the scalability around an eight. We currently have around twenty users implementing the solution on a regular basis.

When it comes to customer support I would rate them a six and a half because of the response time and prioritization. This prioritization factor is most likely due to geography.

We were using API Connect from IBM before switching to Apigee for better user readiness options.

The initial setup took a few weeks.  This was primarily because of us. It took us a while because of internal approvals. The team I was working with just was not fast enough.

When it comes to the return on investment it is pretty good. There is value for money when it comes to engaging external partners and collaborators. The initial cost is one tends to recover quickly with the right business case.

Apigee is expensive and not cost-effective. On a scale of one to ten, I would rate it an eight for the high cost. The changes individuals need to make on their side are costly.

Your team should be familiar with the product before you jump into it. There is training involved for the team, and before deploying and starting to use it, the team should get adequate training. On a scale of one to ten, I would rate Apigee an eight out of ten.

I work for a medium to big size IT consultancy firm in Mexico, and I am in the innovation and interoperability division. Our main work here is to develop projects on interoperability platforms and KPI management, et cetera, and transition from a legacy system to micro-services. In the last year, I have worked on a project on migrating a very big telecom firm from several API gateways and API exposures to Apigee. They're centralizing all their API gateways into Apigee.

We are hoping to lay out the plan for migrating the first sprint of about 200 APIs starting in January. Originally, the plan was to start in December, but the project is so big that it was suffering from delays.

We are going to start doing the actual proxies and migration in January next year. The project consists of about 10-month long sprints. We are going to use all of next year on this first phase. During the course of the next year, we are going to lay out the plan for the next phases. At this point, the total number of APIs to be migrated to Apigee is not clear, but we're thinking that it's about 300, 400 APIs that are going to be migrated.

The solution is deployed on-premise. They're thinking that in the second phase, they're going to go hybrid to have some of the features in the public cloud and some in the proprietary. 

We are integrators.

I think the most valuable features are the security features. Of course, the user access control is the same as the security. The other very important issue is the sandboxing capability of Apigee.

The caching capabilities are somewhat limited. This is more on the developer-oriented capabilities.

At this point, we aren't sure of what else could be improved since we are migrating some pieces of code that are really legacy and really difficult to model as a standard REST API. We are not sure in which areas Apigee is going to fall short. I think that next year we will have a more clear picture of some issues that we are going to find that could be addressed by a new feature, or by enhancing some existing feature in the next versions of the tool.

I have been using Apigee for one year.

Right now, in the development area of Apigee, we have about 20 developers, architects, et cetera. We are in the process of training because our expected growth drives us to have about 100 developers by the end of next year. I think that by the end of Q1, next year, we're going to double our capacity. By mid-year, we have to have 20 more, and so on, until the end of the year. We are planning to have about 100 trained developers, or configuration experts, in Apigee.

All the infrastructure, the enablement, is being done by another company. They are in charge of all the dimensions and actually creating all the infrastructure to host the platform. I have never installed Apigee as a proprietary cloud. I have been working either on the pure cloud environment or hybrid environment. I didn't phase the deployment of the tool, just the configuration.

In Latin America, Apigee is expensive. It's not for small businesses; it's more for big businesses. That's why I was trying to compare, for example, WSO2 against other API management tools. We are trying to create an inside practice in our company to also recommend WSO2 for a mid-size or small-size company where maybe the Apigee pricing for them is too heavy.

Apigee prices are targeting medium to large companies in Mexico. In Latin America, it's basically the same.

I would rate this solution 9 out of 10. 

I think the correct roadmap should be first an approach to Google to create a partnership. Then create a team of developers and an architect, and then start adding more resources as the demand grows.

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. 

I use Apigee to design the proxy and rebuild the pilot, which becomes the API developer's design. This saves time and money for the customer and Rapid7 and 8 by simplifying the process of synchronizing and obtaining actual IDs. 

Apigee is the tool we use to test the API.

Apigee provides good documentation.

The pricing is reasonable.

Apigee's certification is beneficial.

I like the customized tools included with Aigee such as CI/CD.

Apigee integrates well with Kubernetes, Atos, Jira, Microsoft Teams, as well as ServiceNow.

I'm not a fan of the developer portal. It should be simplified. There is an excessive amount of customization required. 

When compared to Azure, Azure is more user-friendly to customers.

Monitoring could be improved. Google Cloud provided better monitoring than Apigee. 

I still prefer monitoring in Azure or Anypoint MuleSoft.

It also requires additional tools to assist in the deployment of Apigee.

I would like to see the monitoring, dashboards, and reports improve.

I have been using Apigee for five years.

I am working with version 8.

Apigee is a stable solution.

Apigee is a scalable solution.

Technical support is very good.

They resolve issues quickly.

I have experience with many different platforms such as Mulesoft and Microsoft API Management.

In Azure, I use Azure DevOps and with Mulesoft I use Jira.

In my previous location, I partnered with Microsoft using Azure in API Management.

The initial setup was straightforward, however, when compared to MuleSoft, MuleSoft was easier.

QMance, C1/CD, GitHub, GitLab, and Jenkins were among the applications we used to manage Apigee deployment.

We completed the deployment ourselves.

The north direction used in SolarWinds and MuleSoft is the same as the north direction used in Azure and Azure DevOps for solution and system deployment.

From my perspective, Azure and Azure DevOps are the appropriate solution and system deployment tools.

I like the deployment and customization in Apigee.

The deployment process is a  scheduled tool on the file. In my opinion, testing the tool is important during the development process. However, in Azure, I haven't seen any tool testing. Therefore, I need to test the tools for the testing and deployment process. In IT, I require sales tools to test the APIs.

it is necessary to have two forms for testing, and I see the testing tool in MuleSoft, but in Azure, I haven't seen any testing tool. I need to test the tools for the testing and deployment process.

In IT, I need the sales tools to test the APIs.

Licensing fees are paid on a monthly basis.

The prices are comparable. It is comparable to MuleSoft, WhiteCloud, and other similar applications.

Apigee X improves the connection series by solving a different problem for me. It refers to service connections.

Apigee is something I would suggest to others. It has good documentation, is simple to install, has great support, and is a good testing tool.

I would rate Apigee a seven 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. 

It's deployed on the cloud. There are a few hundred people in my organization who use this solution. 

It's easy to use and the security features are valuable.

I have used this solution for about three years.

It's a stable solution.

It's scalable. You can onboard multiple partners.

Setup isn't very complex.

My clients pay for a license.

We also use Amazon.

I would rate this solution as eight out of ten.

I would recommend this solution to those who want to start using it, but it depends on the requirements and automation.

I am API architect. We are service providers and provide API solutions to our customers.

Apigee provides out-of-the-box policies, so it is ready to use with minimal configuration to those policies. You can govern your API and manage the life cycle of the API completely with the Apigee tool.

You can use the documentation through the API portal and integrate it with the open API specification, and then design and create your API process.

When we compare Apigee with Mulesoft, we find that Mulesoft provides many out-of-box connectors to your legacy applications and it is now part of Salesforce. It was acquired by Salesforce. It has hundreds of soft connectors available and an exchange place where you can put your reusable assets. A similar kind of thing is available in Apigee as well, where developers start putting their assets which can be reused.

Right now we can create custom policies using Java scripts and other supported languages. That's the good thing. But if you are supposed to have created some APIs that are available on the market as public, it would be good if you can share it. It would give a bit more flexibility and then connect configurations that you can do on your own which are not supported by APIs.

From a connector perspective, it would be good if it could allow you to create a custom connector, or it could provide out-of-box connectors, or some in the backend. That would be great.

I have been working with Apigee almost five years.

Apigee is an excellent product.

The scalability depends on your configuration. You can make it scalable.

Other vendors are basically giving more. For example, Azure. Azure is cloud-based, so they offer many things, including client support and hosting. So if you take Azure for all your storage and hosting, then they are inclined to use their API data solution. Similarly, MuleSoft provides you many things. It is an ESB kind of service broker, so you can connect to many varieties of backends. It supports that, so they can use Mulesoft API. Apigee provides a number of out-of-the-box policies and it handles the API governance. But if are looking for an end-to-end solution, Apigee is a bit behind. But if it is combined together with Google Cloud, and if the Google cloud offerings are comparable to Azure, then probably Apigee will lead.

Technical support is very good. In my previous company we had on-premise Apigee installed. For that we reached out to customer support. It was excellent. And while deploying it to our customer side, we reach out to them, for both Mulesoft and Apigee. And it has a very good community portal. Customers have shared their experiences troubleshooting - their challenges, issues, and resolutions. It was good.

We have used Mule API, Mule API Gateway, and API Manager.

The initial setup is pretty simple.

It provides some sort of integral service communication support. We have a multiple API proxy with multiple APIs currently deployed. So if API A is calling API B, and API B is calling API C, if that left to right communication is also available in API B, for that we have to use some kind of service tool. That is also available inside Apigee.

Apigee is more of an entry level solution that does basic things pretty well, but if you want to go more customizable, you want to really look for another solution.

My general advice is, suppose you have minimal organizational and transformation requirements, and you have an all HCTP backend with no processing required, then definitely you should go for Apigee, because Apigee provides all those things out of the box. It can protect your backend from any penetration threat and you can integrate it with your identity provider for security. All those things are provided by Apigee. Suppose you have very, very little request response, it does not require much transformation. In that case, you can use Apigee. But if it requires a huge transformation and lots of calculations and business logic is involved, in that case, you have to go for where you can write your custom logic, so for that you should go for a Mulesoft kind of solution.

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

We use it for API monitoring purposes, and for the management of KPM metrics around the APIs.

They need to work on the cost of the solution. But again, it depends on the use case. The use case which I have installed serves the intended purpose. I don't have any negative feedback on it.

We have been using the solution for the last six or seven years.

I am satisfied with the stability of the solution.

I have around 500-2000 users using the solution in my company. It serves the purpose of my use case.

There is no real technical support unless you have a problem with the servers or something gets lost. It is only when the service is down or there is some issue, there'll be a reply from them depending on your subscription.

The biggest advantage of the competitors over Apigee is cost. I would advise you to be careful due to its cost.

I would rate the solution a seven out of ten.