Apigee
by Google Cloud · API Management
Full-lifecycle API management platform on Google Cloud, with SAP ERP and SAP Gateway connectors.
Updated August 2026 · By the ERP Research Editorial Team · Independent and vendor-neutral.
- Works with
SAP- Deployment
- Cloud, Hybrid
- Pricing
- Consumption-based (pay-as-you-go) and quote-based subscription tiers
- Founded
- 2004
- Headquarters
- San Jose, California, United States
Overview
Apigee is a full-lifecycle API management platform now operated as part of Google Cloud, used to design, secure, publish, analyze and monetize APIs. The product originated as Sonoa Systems, founded in Santa Clara, California in 2004 by Raj Singh and Ravi Chandra; the company released a public beta of an API management tool called Apigee in 2009, rebranded entirely to Apigee in 2010, and went public on NASDAQ in April 2015. Google announced its acquisition of Apigee in September 2016 for approximately 625 million dollars, completing the deal in November 2016.
An Apigee API proxy sits between clients and backend targets, built via the management UI, YAML, XML policy files or OpenAPI Specification import. Policies attach to the proxy request/response flow for security (OAuth2, API key validation, SAML, Google Cloud IAM-based authentication, data masking), traffic management (SpikeArrest, rate limiting and quota policies, load balancing across target servers) and mediation (message transformation, response and general-purpose caching, key-value maps, CORS support). A developer portal lets external developers discover published APIs, register apps and try calls, and the platform includes API monetization and built-in analytics dashboards for proxy and endpoint performance alongside custom reports.
Apigee X runs fully within Google Cloud as a managed service; Apigee hybrid keeps the control plane in Google Cloud but lets the runtime plane run on Kubernetes on-premises or in another cloud for teams that need to keep API traffic off Google infrastructure. Apigee Edge, the original architecture, reached end-of-life in March 2025. For ERP connectivity, Google Cloud Integration Connectors, usable from Apigee Integration, include a dedicated SAP ERP connector that exposes SAP tables as views and BAPIs/RFCs as callable stored procedures, plus a separate SAP Gateway connector.
Screenshots & demo
Demo video from the vendor's YouTube channel.
Features & capabilities
API Proxy and Gateway
Core proxy layer between API clients and backend services.
- API proxy creation via UI, YAML, XML configuration or OpenAPI Specification import
- Message transformation and mediation between REST, SOAP and backend formats
- Load balancing across backend target servers
- Response and general-purpose caching
- Key-value maps and property sets for configuration data
- CORS support
Security Policies
Policies attached to proxy request and response flows.
- OAuth2 (client credentials, authorization code and password grant types)
- API key validation
- SAML-based policies
- Google Cloud IAM-based authentication
- Data masking and content-based security checks
- SpikeArrest and rate-limiting/quota policies to throttle traffic
Analytics and Monitoring
Built-in visibility into API traffic and performance.
- API proxy performance dashboards
- Target and endpoint performance dashboards
- Custom reports for deeper analysis
- Environment- and proxy-level traffic monitoring
Developer Portal and Monetization
Self-service access for external API consumers.
- Developer portal for external developer discovery, access requests and API trials
- API catalog and documentation publishing
- App registration and API key issuance for developers
- Monetization and rate-plan capabilities for subscription or usage-based billing
Deployment and Connectivity
Architecture options and ERP-adjacent connectivity.
- Apigee X: fully managed, Google Cloud-native runtime
- Apigee hybrid: Google Cloud-hosted control plane with a self-managed runtime plane on Kubernetes
- Google Cloud Integration Connectors for SAP ERP (tables, BAPIs, RFCs) and SAP Gateway
- Terraform and API-based CI/CD for proxy deployment
Common use cases
- Fronting SAP ERP or SAP Gateway systems with a governed API layer via Google Cloud Integration Connectors
- Composing multiple backend services into a single external-facing API proxy
- Publishing internal APIs to external developers through a self-service developer portal
- Enforcing OAuth2, API key and rate-limiting policies on legacy SOAP or REST backends
- Running a hybrid deployment where the control plane stays in Google Cloud but API traffic is proxied on-premises for data residency
- Monetizing APIs with usage-based or subscription rate plans
Strengths & considerations
Strengths
- Native Google Cloud Integration Connectors for SAP ERP (tables, BAPIs, RFCs exposed as callable operations) and SAP Gateway, beyond generic REST/SOAP proxying
- Hybrid architecture separating a Google Cloud-managed control plane from a self-managed runtime plane for data-residency-sensitive deployments
- Integrated developer portal and API monetization alongside the gateway rather than as separate add-on products
- Long operating history as a dedicated API management platform, originating in 2009 and backed by Google Cloud infrastructure since 2016
ERP integrations
SAP ERP connector exposes SAP tables as views and BAPIs/RFCs as callable stored procedures; available to both Apigee Integration and Application Integration
Pricing
Google Cloud offers a 60-day free Apigee evaluation sandbox. Production usage runs under Standard, Enterprise and Enterprise Plus subscription tiers; Google publishes tier entitlements but not full list pricing, so production costs are quote-based. Get an independent shortlist with pricing guidance below.
Technical & security
- Hosting
- SaaS (Apigee X, Google Cloud native) or hybrid, with the control plane in Google Cloud and a self-managed runtime plane on Kubernetes
About the vendor
- Founded
- 2004
- Headquarters
- San Jose, California, United States
- Ownership
- Subsidiary of Google LLC (Alphabet Inc.); acquired by Google in November 2016 for approximately 625 million dollars
Alternatives to Apigee in API Management
Apigee — frequently asked questions
Does Apigee integrate with SAP ERP?
Yes. Google Cloud Integration Connectors, usable from Apigee Integration, include a dedicated SAP ERP connector that exposes SAP tables as views and BAPIs/RFCs as callable stored procedures, plus a separate SAP Gateway connector.
What is the difference between Apigee X and Apigee hybrid?
Apigee X runs fully within Google Cloud as a managed service. Apigee hybrid keeps the control plane in Google Cloud but lets the runtime plane run on Kubernetes on-premises or in another cloud. Apigee Edge, the original architecture, reached end-of-life in March 2025.
Can external developers self-serve access to APIs published on Apigee?
Yes. Apigee includes a developer portal where external developers can discover published APIs, request access, register apps and try calls, separate from the internal proxy-management interface.
How is Apigee priced?
Google Cloud offers a 60-day free evaluation sandbox. Production deployments run on Standard, Enterprise or Enterprise Plus subscription tiers; Google publishes what each tier includes but final pricing is quote-based.
Who owns Apigee?
Apigee began as Sonoa Systems, founded in 2004, rebranded as Apigee in 2010 and went public in 2015. Google acquired it in November 2016 for approximately 625 million dollars, and it now operates as part of Google Cloud.
Evaluating API Management?
Tell us your ERP and requirements and we'll send an independent shortlist — including Apigee and the best-fit alternatives — with honest pros and cons.