> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/p/public-cloud.md).

# Public Cloud

A cloud computing model that provides services over the public internet and shared across organizations.

A public cloud is a cloud computing environment where infrastructure and services are owned and operated by a third-party cloud provider and shared across multiple organizations (tenants). Resources are delivered over the public internet and billed on a pay-as-you-go basis, allowing organizations to avoid upfront capital expenditure on hardware.

Major public cloud providers include Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform, and Cloudflare. Public clouds offer a wide range of services including compute, storage, databases, networking, AI, and serverless platforms. Multi-tenant resource sharing enables economies of scale that drive down costs for individual customers.

Public clouds are the most common hosting environment for APIs and serverless applications. API gateways deployed on public cloud infrastructure benefit from the provider's global network, built-in security features, and managed services. Serverless API gateways on public clouds eliminate capacity planning entirely, scaling automatically to handle any traffic volume and charging only for actual usage.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.serverlessapigateway.com/glossary/p/public-cloud.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
