Google Cloud Endpoints
cloud.google.com
- Free plan
- macOS
- Linux
- Web
- API
- Self-hosted
What Google Cloud Endpoints is
Google Cloud Endpoints manages APIs with tools to secure access, monitor activity, analyze usage, and set request quotas. It accepts API descriptions in OpenAPI 2.0, OpenAPI 3.x, or gRPC and provides its proxy through ESP or ESPv2. Documented backends include Google Kubernetes Engine, Compute Engine, Kubernetes, App Engine, Cloud Run, Cloud Run functions, and Knative serving; proxy availability differs by backend. The service is optimized for Docker and can host an API anywhere Docker runs, provided it can reach Google Cloud over the internet. API keys can be required and validated to identify a Google Cloud project for quota, billing, and monitoring. User authentication options include Firebase Authentication and Auth0, with JWT validation by ESP. Logs and metrics are viewable in the Google Cloud console. Quotas regulate call rates, though the feature is Beta and may have limited support. Pricing depends on calls to Service Control: the listed tiers are free, $3 a month, and $1.50 a month, with stated call-volume thresholds.
Who it suits
It suits teams that need API access controls, usage monitoring, and lifecycle management across documented cloud or Docker-based deployments. Teams considering quotas should note that the feature is Beta and requests need an API key for caller identification.
Good to know, and what to watch
- Supports OpenAPI 2.0, OpenAPI 3.x, and gRPC.
- API keys can identify projects for quota and billing.
- Logs and metrics appear in Google Cloud console.
- Documented deployments include several Google Cloud backends.
- Quota feature is Beta and may have limited support.
- Proxy availability varies by backend.
Plans
Every plan and priceFree usage tier
Standard usage tier
High-volume usage tier
Usage-based
Free plan
Getting started
- Open the Google Cloud Endpoints website
- Choose a supported API description format: OpenAPI 2.0, OpenAPI 3.x, or gRPC
- Select a documented backend or another Docker-supported host with Google Cloud access
- Deploy the Extensible Service Proxy or ESPv2 where supported
- Configure API keys for project identification and quotas
- Set up Firebase Authentication or Auth0 if JWT validation is needed
- Review logs and metrics in the Google Cloud console
Limits to check
The Free usage tier covers 1,999,999 API calls at no cost. Standard usage is $3 a month for 2,000,000 to 1,000,000,000 calls, while High-volume usage is $1.50 a month from 1,000,000,000 calls and above.
The Club's review
Google Cloud Endpoints is an API management system for teams that need to secure and monitor APIs across cloud and Docker-based deployments. It is strongest for organizations already building around Google Cloud services. The trade-off is that quota controls are Beta, and using them requires API keys on every request.
Overview
Endpoints manages API access and lifecycle through Google Cloud Service Infrastructure, with logs and metrics available in the Google Cloud console. It accepts API definitions in OpenAPI 2.0, OpenAPI 3.x, or gRPC, and uses the Extensible Service Proxy (ESP) or ESPv2 to manage traffic.
Its hybrid deployment model is useful for teams with varied runtimes: documented backends include Google Kubernetes Engine, Compute Engine, Kubernetes, App Engine, Cloud Run, Cloud Run functions, and Knative serving. Proxy availability depends on the backend. Docker support broadens deployment further, as an API can run wherever Docker is supported if the host can connect to Google Cloud over the internet.
Key features
- API keys and caller identification: Endpoints can require and validate API keys. Keys identify a Google Cloud project for quota, billing, and monitoring, which makes project-level attribution part of the access setup.
- User authentication: Firebase Authentication and Auth0 are documented options, with ESP validating their JWTs. This is useful for teams using either service, but does not imply support for other identity providers.
- Logs, metrics, and analytics: Service Infrastructure reports logs and metrics for viewing in the Google Cloud console. API analytics and lifecycle management are supported, giving teams operational visibility alongside API administration.
- Quotas: Rate controls can help limit excessive application calls, but the feature is Beta and may have limited support. Requests also need API keys so Endpoints can identify the caller's project; teams unwilling to require keys should not depend on quotas.
Pricing
Endpoints uses freemium, call-based pricing. Charges depend on calls to Service Control, so traffic volume directly affects cost; the per-million figures below make the high-volume tier cheaper at scale, but teams should account for their expected call band.
- Free usage tier: free, for up to 1,999,999 API calls. This is the sensible starting point for small workloads or evaluation, but it does not cover larger traffic.
- Standard usage tier: $3 a month, billed at a price per million API calls, for 2,000,000 to 1,000,000,000 calls. It fits workloads beyond the free threshold; the stated band means costs are tied to call volume rather than a fixed seat count.
- High-volume usage tier: $1.50 a month, billed at a price per million API calls, for 1,000,000,000 calls and above. Its lower per-million rate favors very high-volume services, but is irrelevant to most smaller deployments.
- Usage-based: free, with 1,000,000,000 API calls and above at $1.50 per million. This expresses the high-volume rate in usage-based terms; no seat limits or trial period apply in the stated pricing.
The plan labels and billing units make it important to map projected calls to the applicable tier before budgeting, especially near the threshold between standard and high-volume rates.
Platforms
Endpoints is available for API, Linux, macOS, self-hosted, and web environments. Its Docker-oriented hosting and hybrid deployment approach suit teams that need to place APIs across supported backends, though proxy availability varies between them.
Who it's for
Choose Endpoints if your team operates APIs on Google Cloud or Docker-capable infrastructure and wants API key validation, monitoring, analytics, lifecycle management, and quota controls in one management system. It is less compelling for a team that needs mature quota support today, does not want API keys on quota-bearing requests, or needs a runtime without a documented proxy option.
Pros and cons
- Pro: OpenAPI 2.0, OpenAPI 3.x, and gRPC support accommodates several API description approaches.
- Pro: Documented Google Cloud, Kubernetes, and Docker deployment paths offer flexibility across managed and self-hosted environments.
- Pro: API keys can serve validation and project-level quota, billing, and monitoring identification.
- Con: Quotas are Beta and may have limited support, weakening their suitability as a dependable core control.
- Con: Requiring API keys for quota identification adds an access requirement that may not suit every API design.
- Con: Proxy availability varies by backend, so deployment choice can constrain whether Endpoints fits.
Alternatives
For broader comparison, browse API Management Software or API Gateway Software.
- Kong Gateway is worth considering if a 30-day trial with no Gateway limits and 30 days of analytics retention better fits your evaluation needs.
- DreamFactory may suit teams seeking a self-hosted API platform with a free PostgreSQL connector or a paid Linux Lite plan.
- Gravitee API Gateway offers a free Apache 2.0 Community Edition for teams looking for a community option without numerical limits stated for that plan.
- Algolia is a search-focused option, with a free tier capped at 10K search requests/month and 50K records.
- Apiman is a free, self-hosted Apache-2.0 community edition with no features hidden behind paywalls.
- Hasura may fit teams that want a free plan capped at 2 databases per project, 100MB data passthrough/month, and 3M API requests/month.
- Apigee API hub is an option for eligible Apigee organizations in supported regions that need its API hub at no additional cost.
- Fusio is another free, open-source API management platform.
Verdict
Google Cloud Endpoints is a strong fit for teams building APIs on Google Cloud and Docker-based infrastructure that value project-linked API key controls and centralized monitoring. Its broad deployment choices and call-based tiers are compelling, but teams that require dependable quota enforcement should look elsewhere until the Beta limitation and API-key dependency align with their needs.
The verdict
Google Cloud Endpoints combines API security, monitoring, analytics, and quota controls. Check backend proxy availability and the call-volume pricing tiers against your deployment needs.
Questions people ask
Is Google Cloud Endpoints free?
Yes. The Free usage tier is free for 1,999,999 API calls. Paid tiers are based on API-call volume.
What are the listed paid prices?
Standard usage is $3 a month for 2,000,000 to 1,000,000,000 calls. High-volume usage is $1.50 a month for 1,000,000,000 calls and above.
Which API formats are supported?
Endpoints supports OpenAPI 2.0, OpenAPI 3.x, and gRPC.
Where can an API be deployed?
Documented backends include Google Kubernetes Engine, Compute Engine, Kubernetes, App Engine, Cloud Run, Cloud Run functions, and Knative serving. Docker-supported hosts with internet access to Google Cloud are also supported.
What authentication options are listed?
Firebase Authentication and Auth0 are documented options, using JWT validation by the Extensible Service Proxy.
How are quotas identified?
Requests must pass an API key so Endpoints can identify the caller’s Google Cloud project for quota features.
What the maker publishes
- API access
- Endpoints can require and validate API keys, and API keys identify a Google Cloud project for quota, billing, and monitoring. source
- API formats
- Endpoints supports APIs described with OpenAPI 2.0 and OpenAPI 3.x, as well as a gRPC option. source
- Authentication
- Documented user authentication options include Firebase Authentication and Auth0, which use JWT validation by ESP. source
- Deployment options
- Documented backends include Google Kubernetes Engine, Compute Engine, Kubernetes, App Engine, Cloud Run, Cloud Run functions, and Knative serving, with proxy availability varying by backend. source
- Hosting
- Endpoints is optimized for Docker and can host an API anywhere Docker is supported if it has internet access to Google Cloud. source
- Logs and metrics
- Endpoints uses Service Infrastructure to manage APIs and report logs and metrics viewable in the Google Cloud console. source
- Maker founding
- Google Inc. was officially born in August 1998. source
- Maker headquarters
- Google's company story identifies its current headquarters, the Googleplex, as being in Mountain View, California. source
- Pricing basis
- Endpoints pricing depends on the number of API calls, and Endpoints charges by calls to Service Control. source
- Proxy
- Endpoints provides API management through the Extensible Service Proxy (ESP) or ESPv2. source
- Purpose
- Cloud Endpoints is an API management system for securing, monitoring, analyzing, and setting quotas on APIs. source
- Quota identification
- To use features such as quotas, each request must pass an API key so Endpoints can identify the caller's Google Cloud project. source
- Quotas
- Quotas control the rate of application calls and help protect APIs from excessive requests, but the documented quota feature is Beta and may have limited support. source
Checked against the maker's pages on 9 Oct 2026.