Cloud|

Operations

Develop and operate an independent Cloud application through the shared gateway.

1 min read Updated 2026-09-07 #operations#deployment#runtime

Cloud runs each application as an independent Bun service.

The gateway is the only public entry point. Applications, Postgres, Valkey, and supporting services share a private network.

For a third-party app, the normal unit of ownership is its own repository, version, image, and release cycle. The public application contract is the same inside the Cloud monorepo, but repository scripts and workspace aliases are not part of that contract.

Choose the development shape

Shape Use it when
Standalone development Your application consumes the published package
Monorepo development You maintain Cloud itself or a built-in application

Both shapes use the same application contract. They differ in dependency and container ownership.

Deployment workflow

  1. Choose apps and their deployment requirements.
  2. Build the application.
  3. Set infrastructure configuration.
  4. Configure application values through Settings.
  5. Scale and stop services safely.
  6. Use Observability for health and failure.
  7. Use Troubleshooting when the registry, gateway, or dependencies disagree.

FreeIPA is optional. See FreeIPA only when the deployment uses it.

Connect a coding agent

The Cloud skill provides compact working instructions. MCP supplies exact current documentation when details matter.

CLI command
bunx skills add https://docs.example.com

This command installs the working instructions published by this website in the selected coding agent.

For exact, current details, also connect the MCP server through one of the agent tabs.

Installation uses the open-source Vercel Skills CLI.

The skill and MCP complement each other: the skill describes workflows, while MCP supplies current documentation.