# The Cloud Developer Platform



> Build an app on The Cloud, or connect your app as a tool in The Cloud. Two golden paths, hosted and governed, each reachable from one page.



## The Cloud Developer Platform

The Cloud is a workspace any AI can read and write over MCP, and a runtime that hosts real apps. There are exactly two things a builder does here. Pick your path.

## Build ON The Cloud

**“I want an app or widget in The Cloud.” **Build a Studio app — described or coded — that The Cloud hosts, sandboxes, and scopes by manifest, then lists through the share gate. From idea to installable without owning a server.

- [Start the Build path →](/docs/build-on-the-cloud) — quickstart, manifest and scopes, the dev loop, hosting, listing.

## Connect INTO The Cloud

**“I want my app usable as a tool in The Cloud.” **Connect any MCP client to one endpoint and it acts in the workspace with consent — or bring your own service in through the curated catalog and, once containment ships, the open tier.

- [Start the Connect path →](/docs/connect-into-the-cloud) — connect every client, auth, the generated tool reference, the safety model.

## Reference

- [Tool reference](/docs/tool-reference) — every tool, generated from the same registry that serves llms.txt.
- [Safety classes & the consent law](/docs/safety-and-consent) — the governance that makes the platform trustworthy, documented as a feature.
- [Open connect tier](/docs/open-connect-tier) — the superhighway, and the containment gate it waits on, stated honestly.

> **Every page is also machine-readable** — Append /index.md to any docs URL for the clean-markdown version of that page — the same content an AI reads natively. The tool reference is generated from the live registry, so the docs can never drift from what the server actually serves.