Apigee

cloud.google.com ↗

Place managed API proxies in front of backends to govern traffic, security, and developer access.

SI Score
75/100
Pricing
Pay-As-You-Go AI reading, not confirmed
Free plan
No AI reading, not confirmed
Sign-up required
Required AI reading, not confirmed

Ask SI about Apigee

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the Apigee homepage

What it does

Apigee is Google Cloud's API management platform for building and operating API proxies in front of backend services. A proxy can apply security and traffic policies, expose API products to developers, and provide analytics for an API program. Apigee supports REST, SOAP, GraphQL, and gRPC designs, with a managed runtime or a hybrid option where customers run the runtime in their Kubernetes environment. It is an API gateway and management layer, not an API client for unrelated services.

Put a proxy between consumers and a backend

Apigee's documented lifecycle starts by provisioning an organization, then creating an API proxy that fronts a backend. The product page links a first-proxy tutorial and describes policies for security, rate limits, quotas, and transformations. A team can import an OpenAPI description, deploy the proxy to an environment, and publish an API product through a developer portal. Hybrid deployment keeps runtime services in a customer-managed Kubernetes cluster while the control plane manages API operations.

Apigee is aimed at API programs that need governance across services, not a single lightweight reverse proxy. It supports multiple API styles and offers analytics, cataloging, developer onboarding, and monetization features. Choosing between a standard or extensible proxy affects the available capabilities and per-call rate.

Pricing has an evaluation period, pay-as-you-go API-call and environment charges, and subscription plans. Environment cost is separate from API-call volume, and region-specific networking and add-ons can contribute to the bill. The pricing page should be used with an estimate for the intended deployment rather than treating the free evaluation as a permanent plan. No organization or proxy was provisioned for this listing.

Strengths

  • API proxies can apply security policies, rate limits, quotas, analytics, and other controls in front of backend services.
  • Supports REST, SOAP, GraphQL, and gRPC API styles.
  • Offers managed and hybrid deployment, API cataloging, and developer-portal workflows.

Watch out for

  • Pay-as-you-go costs include environment charges as well as API-call meters, with possible networking and add-on charges.
  • The 60-day evaluation is a trial, while ongoing access uses usage-based or subscription pricing.

Best for

  • Organizations standardizing access, security, and lifecycle management across multiple APIs.
  • Teams publishing API products to partners or developers with a managed portal and analytics.
  • Enterprises that need API management while keeping runtime traffic in their Kubernetes environment.

Sources