Agent-native application cloud

Your agent builds.
OpenCloud runs.

Give Codex, Claude Code, or another coding agent a production platform it can understand: database, auth, files, realtime, functions, scheduled jobs, observability, HTTPS, and safe rollbacks—through connected OpenCloud tools or a verified CLI fallback.

View CLI quickstart

MCP or verified CLIPrivate by defaultBrowser-approved login

A complete runtime your agent can inspect, deploy, verify, and operate.

01Postgres

02Auth

03Storage

04Realtime

05Functions

06Telemetry

From idea to HTTPS

A handoff both humans and agents can trust.

You stay in control of the product and identity. Your agent gets a narrow platform contract and enough access to build, deploy, verify, and iterate.

Copy the prompt

Paste one focused instruction into Codex, Claude Code, or another coding agent with OpenCloud tools or a terminal.

Shape the product

The agent asks what to build, who it serves, and what the first useful workflow should be.

Connect safely

The agent uses connected OpenCloud tools when present, or verifies the pinned CLI fallback and connects only the selected app.

Deploy, then review

The agent verifies in isolated dev, deploys the exact passing revision, checks production, and then gives you the private app.

One integrated platform

The full stack, without the glue work.

OpenCloud gives generated applications durable primitives and a deterministic release model instead of a pile of disconnected services.

DBpostgres + rest

Data with real boundaries

PostgreSQL schemas, append-only migrations, REST APIs, and row-level security give every app durable data that remains understandable after the first prompt.

IDcentral auth

One identity, app-scoped access

One-time email access, central sessions, private app admission, and owner-aware policies keep identity tokens outside generated frontend code.

FSobjects

Files

App buckets and owner prefixes for uploads, evidence, and media.

RTwebsocket

Realtime

Private channels for presence, updates, and collaborative workflows.

FNedge

Functions

Server-side code with authenticated invocation and secret delivery.

OPoperate

Observe

Logs, metrics, backups, cron history, health checks, and rollbacks.

Start in your agent

One agent prompt. A complete build loop.

The copied prompt tells your coding agent to read the current OpenCloud instructions, use the verified CLI when a terminal is available, resolve the right app, build in isolated dev, and deploy the exact verified revision.

Designed for Codex, Claude Code, and other terminal agents, with the hosted OpenCloud connector for supported no-terminal clients. Read the quickstart.

Starts by asking what you want to build Uses the verified CLI when a terminal is available Uses the hosted connector only without a terminal Keeps credentials in browser-approved, protected flows Verifies the exact revision before production

opencloud-build-prompt.txt

Build and deploy the app I describe next using OpenCloud.

Before acting, read and follow the current OpenCloud builder instructions at https://plan-implementation.ocd.dev/SKILL.md. Treat them as authoritative. Use the verified OpenCloud CLI when you have a terminal; use the hosted OpenCloud connector only when no terminal is available. Never invent or bypass APIs, credentials, IDs, URLs, or verification results.

If I have not described the app yet, ask me what I want to build. Then:

- Clarify only decisions that would materially change the product; make sensible defaults for everything else.
- Reuse an existing app only when it clearly belongs to this project. Otherwise create a new private app unless I explicitly request a public one.
- Build a complete, polished, mobile-friendly product with every requested capability.
- Never ask me to paste passwords, cookies, tokens, email links, credentials, or secret values. Use OpenCloud’s browser approval and protected secret-entry flows.
- Validate each coherent revision, test it in isolated development with synthetic data, fix failures, obtain an exact-revision verification receipt, promote that receipt, wait for deployment, and run production verification.
- Do not stop after generating code, validating, or creating a preview.

I authorize production deployment only for the exact revision that passes OpenCloud’s isolated verification for this request. This does not authorize deleting, restoring, rolling back, exposing private data, or changing unrelated apps or platform resources.

Finish by giving me the canonical live URL, a concise summary of what was built, and the final validation, deployment, and production-verification results. If blocked, explain the exact blocker and the smallest action I need to take.

Your next app

Describe it. Deploy it. Review it.

Start with the prompt now. Your agent can use connected OpenCloud tools or the verified CLI fallback, select or create the right private app, build in isolated dev, and promote the exact passing revision before handing you the live app.