Zuplo vs.Apigee API Management
Zuplo is redefining what it means to be an API Management platform and is an alternative to Apigee API Management. With Zuplo, you can easily build and share quality APIs with other developers. Compare features, pricing, deployment options, and customizability below.
Overview
Most companies that we speak with that use GCP have an obvious question... "Why would I choose Zuplo versus Apigee API Management?" Here are 11 reasons why engineering teams would choose Zuplo over Apigee API Management when publishing a public API or tackling the challenge of multiple teams working on many APIs.
"With Apigee, when we started integrating, the trainer recommended using the UI to make changes. We don't want to make changes using UI, we want to source control these proxy artifacts and use the management APIs." - Director, Staffing & Recruiting company
| Feature | Apigee API Management | Zuplo |
|---|---|---|
| GitOps-enabled | Information about the gateway is stored in abstracted databases. Configuration requires scripting of API calls. Deployments take 45 mins+, even to setup a development environment. | All gateway information is stored in text files that can be version controlled. Integrated with git services like GitHub, bitbucket, etc. Deploy unlimited preview environments (including developer portals) in under 20 seconds. Set up a new development environment in around 10s. |
| Cost | $$$$ | We have saved customers over 80% on the purchase cost of Apigee, and even more on operating costs |
| Cloud Deployment | GCP or custom on-premise deployment only. Takes hours to deploy. Additional environments cost $$$. | Edge native at 250+ data centers around the world. Under 20 seconds to deploy, unlimited preview environments. Serverless scalability with 0ms startup time. |
| Scalability | Manually scale by provisioning coarse-grained, expensive servers. | Auto-scales dynamically and globally with 0ms startup time. We already have customers processing over 1.5B calls / month who have had 0 downtime and never worried about scale-up. |
| Developer Portal | Dated portal | Just import your OpenAPI spec to generate beautiful Stripe-like documentation and developer portal. Check out an example portal here. |
| Single Product | ApiGee, ApiGee X, ApiGee Edge - we’re not going to do ApiGee’s job by describing the differences here, but we honestly don’t know after hours of researching. Email us at whatzup@zuplo.com if you can figure it out and explain to us. | There’s only one Zuplo, and it’s the only one you need in your life |
| Multi-cloud | GCP only. | Zuplo runs at the edge, in over 250 datacenters around the world, and can securely connect to your backend wherever it’s hosted. Zuplo often outperforms AWS API gateway when calling services hosted in the same datacenter in AWS! |
| Autonomous Reliability | Dependent on multiple Azure services for runtime operation. | Your Zuplo gateway will keep running even if other major parts of Zuplo are down (not happened yet, btw). |
| Designed for Programmability | Offers limited code extensibility but “… does not permit system calls such as network I/O, filesystem read/writes, current user info, process list …" | Developers get to write code in JavaScript/TypeScript, that runs natively in the gateway and feels familiar to any developer. |
| Secure Tunneling Connection Available for any Cloud | VPC connectivity to GCP. | Zuplo can secure backend connections to your internal APIs via a secure tunnel based on WireGuard technology - whichever cloud you’re running on (private, AWS, GCP, or Azure). |
Other Features That Make Zuplo Unique
Stripe-like Developer Portal
Just import your OpenAPI spec to generate beautiful documentation and developer portal. Check out an example portal here.
Secret Know-How
Founded by a product leader who also founded Azure API Management at Microsoft in 2013, but felt the product was stuck in the dark ages and decided to build redefine what it means to be an API Management Platform. Read Zuplo's story here.
