Docs
Remoco docs.
A neocloud for agents. Sixteen resource kinds, composed into stacks via blueprints, driven by humans through the console or by LLMs through MCP. This page is the table of contents.
Resource kinds
The control plane exposes one polymorphic surface, POST /v1/resources, that creates any of the sixteen kinds below. Each kind is a thin wrapper around a native cloud SDK; spec shapes are documented per-kind in the API reference.
| Kind | Backed by | Use |
|---|---|---|
workstation | Cloud Workstations | persistent agent dev box (your shell, idle-suspended) |
cloud-run | Cloud Run | serverless HTTP endpoint for agent-shipped services |
cloud-sql | Cloud SQL Postgres | managed Postgres instance, per-org |
memorystore | Memorystore Redis | managed Redis for cache / pub-sub |
bucket | GCS (or S3) | object storage for artifacts, datasets, checkpoints |
secret | Secret Manager | API keys, certs, credentials with versioned access |
vm | Compute Engine | raw VM when you need a long-running daemon |
k8s | GKE Autopilot | full Kubernetes when serverless is the wrong shape |
pubsub | Pub/Sub | topic + subscription for event fan-out |
tasks | Cloud Tasks | HTTP queue with rate limits and retries |
scheduler-job | Cloud Scheduler | cron in the cloud, hits any URL on a schedule |
workflow | Restate | durable, idempotent agent workflows with replay |
vector | Turbopuffer | vector store for RAG, low-latency ANN |
llm | Baseten | self-hosted model endpoints (open-weights) |
network | VPC + Cloud NAT | private network for resources that need egress control |
domain | Cloudflare | custom hostname → backend with cert + access policy |
Stacks
A stack is a named bundle of resources rendered from a blueprint plus parameters. Three layers: blueprint (the recipe), stack (an instance owned by an org), resources (the children, dependency-ordered). Catalog blueprints today: rag-stack, agent-fleet, web-app. Deploy from the console Stacks tab or via POST /v1/stacks.
Quick jumps
Getting started
Sign up, get a workstation, clone a repo, and go live in under five minutes.
Install
The remoco CLI on macOS, Linux, and inside Cloud Workstations.
Architecture
How the API, control UI, Restate, Cloudflare tunnels, and the workstation image fit together.
CLI reference
Every remoco subcommand with flags, examples, and return schemas.
Workstations
Lifecycle, idle-suspend, persistent home, the agent runtime image.
Worktrees
Run several Claude Code sessions in parallel on the same workstation.
Publishing URLs
Wire a service running on the workstation to a public hostname with WorkOS gating.
Skills
What an agent skill is, what ships with remoco, and how to write your own.
Artifacts
Publish HTML reports to a short URL, attach metadata, control visibility.
Control-plane API
HTTP endpoints for resources, stacks, events, billing. Bearer or session JWT auth.
Billing
Per-resource hourly rates, monthly burn, credits, plan tiers.
Design systems
Geist tokens, components, and the shared style sheets agents render against.
For agents
The control plane is also exposed as MCP tools. Install @doss-labs/remoco-mcp and any LLM that speaks MCP can list resources, deploy stacks, invoke workflows, and read events directly. See the API reference for the equivalent REST surface.