Inspirations
Static content — a single HTML page, a deck, a doc, a Claude artifact, a PDF. Instant to publish, served at a path URL, ephemeral by default (30-day expiry unless pinned).
What is CloudGrid
Put your apps and agents on the grid. One command to deploy, one place to discover.
CloudGrid is a runtime for AI-built work. It lets anyone on a team — a developer, a PM, a marketer, or an AI coding agent — ship work into shared infrastructure and get a live URL back. Databases, a cache, an AI gateway, secrets, cron, TLS, and sign-in are wired in by default.
The command-line tool and the MCP tools are both named grid. You build
something, you grid plug it, and it is live in about 30 seconds.
The two realms
Section titled “The two realms”Everything on the grid is one of two things:
Runtimes
Running services — apps and agents defined by a cloudgrid.yaml. Built into a
container and deployed, served at a subdomain, persistent. Can use a database,
a cache, cron, and the AI gateway.
An app and an agent are the same kind of entity. An agent is just an app
with an agent: block (a purpose and a schedule). There is no separate registry
or deploy path — graduating an app to an agent is a metadata change.
Get going
Section titled “Get going”QuickstartInstall, sign in, and take something live.
Install the CLInpm or Homebrew, plus the MCP server.
CLI referenceEvery grid command, its flags, and examples.
MCP referenceConnect an AI client and use the grid_* tools.
cloudgrid.yamlThe full manifest schema for apps and agents.
ConceptsGrids, visibility, plug/pickup/fork, and more.
The vocabulary
Section titled “The vocabulary”CloudGrid has its own small vocabulary. You plug something in to put it on the grid, and unplug it to take it off. A thing that is deployed and serving is live. A brand-new entity that has been registered but not yet built is charged. Your org’s home on the platform is a grid. See the concepts for the full picture.