One workspace
Use one operating surface for DevOps, PM and office work, Clanker Secretary, agent handoffs, and hosted sandbox runs.
Canonical definition
What is Clanker Cloud?
Clanker Cloud is a workspace and cloud runtime for putting AI agents to work. Teams use it for DevOps, office work, full computer control, hosted sandboxes, workflow automation, and reviewed handoffs from agents back to people.
The product has two main shapes: a Clanker Cloud workspace for work that needs local context, approvals, computer control, and live systems; and a hosted Sandbox API for agents that need a clean cloud runtime, workflow state, traces, memory, and hosted outputs.
Clanker Cloud is where a Clanker gets context, uses tools, asks for approval, runs in a sandbox when it needs a real runtime, and hands back work that a person can inspect.
Full computer control
Clanker Secretary can operate a worker computer across apps, browsers, files, SaaS tools, internal systems, research, data entry, and follow-ups.
Hosted agent sandboxes
Agents can start hosted sandboxes, run commands, keep workflow records, request approvals, write traces, store memory, and publish outputs.
Built around review
The default operating model is context first, plan second, approval before side effects, and clear handoff when the work is ready.
Supported providers
Works across the environments teams already run
The current product positioning covers cloud providers, Kubernetes, GitHub, and bring-your-own AI keys from one local operating surface.
Supports ->AWSGCPAzureOracle CloudTencent CloudKubernetesCloudflareHetznerDigitalOceanVercelGitHubBYOK
What it includes
The current Clanker Cloud product surface
Clanker Cloud is not one chat box. It is a set of work surfaces for people and agents that need context, tools, approvals, and a place to run.
Workspace
Clanker Cloud Workspace
A shared workspace for cloud work, office work, and agents. It keeps context, tools, approvals, and reviewable output in one place.
DevOps
Clanker DevOps
A provider-agnostic workspace for infrastructure operations, incidents, deploys, cost reviews, security checks, Kubernetes, GitHub, and reviewed changes.
Computer use
Clanker Secretary
A full computer-control assistant that can work across apps, websites, files, SaaS tools, internal systems, spreadsheets, research, and recurring admin tasks.
Runtime
Cloud for Agents
Hosted sandboxes for agents that need a shell, files, workflow records, approval gates, traces, memory, hosted outputs, and a clean place to run.
API
Sandbox API
Create anonymous or account-owned sandboxes, run commands, send agent messages, preserve workflow state, publish outputs, and integrate sandboxes into your own agent stack.
Automation
Workflow Automation and FDE
Turn repeatable office, DevOps, security, cost, reporting, and handoff workflows into hosted automations, with embedded engineering help when teams want onboarding and training.
How to choose
Which part of Clanker Cloud should you use?
| Need | Use | What happens |
|---|---|---|
| Operate infrastructure | Clanker DevOps | Ask questions, inspect live context, review plans, and move from evidence to approved action. |
| Automate office work | Clanker Secretary | Operate a real computer across apps, browser pages, files, SaaS tools, sheets, portals, and internal systems. |
| Give an agent a runtime | Sandbox API | Start a sandbox, run commands, keep state, record traces, request approval, and delete it when the job is done. |
| Host repeatable work | Workflow Automation | Turn a recurring process into a hosted workflow with inputs, approvals, outputs, and ownership. |
| Roll out with help | Clanker Cloud FDE | Embed an engineer for onboarding, enterprise platform integration, team training, and workflow design. |
Agent runtime
What the hosted sandbox layer adds
Sandboxes are for work that needs a real shell, files, tool calls, or a clean execution boundary instead of only chat.
- Anonymous sandboxes let an agent start quickly for short-lived work.
- Account-owned sandboxes connect work to a user or agent token.
- Active Clanker DevOps and Clanker Secretary accounts get larger, longer-lived Standard sandboxes and hosted outputs; Secretary Pro protected and separately contracted sovereign creation remains blocked until activation.
- Workflow records, approvals, traces, memory, and hosted artifacts keep the run understandable after the prompt is gone.
- The agent-readable API docs and Markdown runbook make it easier for LLMs and agents to use the API correctly.
Trust model
What stays under user control
Clanker Cloud is designed for useful automation without hiding the important boundary between suggestion and side effect.
- Cloud credentials and cluster contexts stay on the operator machine when the desktop workspace is using local infrastructure access.
- Computer-control workflows use review, approval, and handoff patterns for side effects.
- Sandbox work is isolated from the user machine and can be deleted when the job is done.
- Hosted outputs and paid Standard-plan features are explicit product surfaces rather than background behavior.
- The open-source Clanker CLI remains available for teams that want the terminal engine directly.
Best fit
When it fits and when it does not
Best fit
- Teams that want one workspace for DevOps, office work, computer-control tasks, and agent handoffs.
- Builders and AI agents that need a hosted sandbox before touching a real environment.
- Operators who want evidence, plans, approvals, traces, and outputs instead of unreviewed automation.
- Companies that want repeatable workflows hosted in Clanker Cloud or deployed as a private enterprise solution.
- Teams that want FDE help for onboarding, enterprise platform integration, engineer training, and automation design.
Not a fit
- Teams that only want generic chat with no tools, runtime, approvals, or workflow state.
- Organizations that want agents to make production changes with no review, audit, or owner boundary.
- Single-purpose use cases where a narrow point tool already solves the whole job.
Related pages
Next reads
Workspace
See how Clanker Cloud brings DevOps, office work, computer control, and agents into one workspace.
Cloud for Agents
Understand sandboxes, workflow records, approvals, traces, memory, and hosted outputs.
API Docs
Use the Sandbox API with copyable examples for humans, agents, and LLMs.
Clanker Secretary
See the full computer-control assistant for apps, websites, files, and office work.
Clanker Cloud FDE
Bring in embedded engineering for onboarding, training, enterprise platform rollout, and workflow automation.
FAQ
Common questions
Is Clanker Cloud only for DevOps?
No. Clanker DevOps is one product surface. Clanker Cloud also includes Clanker Secretary for full computer control, Cloud for Agents for hosted sandboxes, the Sandbox API, workflow automation, and FDE onboarding.
Do I need the desktop app to use Clanker Cloud?
Use the desktop workspace when the job needs local context, local credentials, computer control, or live systems on your machine. Use the Sandbox API when an agent needs a hosted runtime for commands, files, workflow state, traces, approvals, and outputs.
Can agents create sandboxes without an account?
Yes. Anonymous sandboxes are available for quick, short-lived work. Free Standard accounts support longer sessions, while active Clanker DevOps and Clanker Secretary plans support larger persistent or hosted-output workflows. Secretary Pro protected and sovereign creation fails closed until activation.
What is Clanker Cloud FDE?
FDE means field deployment engineering. It is embedded engineering help for Clanker Cloud onboarding, enterprise platform integration, engineer training, workflow automation, and custom agent workflow design.
Next step
Choose the right starting point
Start with the Workspace if you want the product view, or open the API docs if you want an agent to create and use hosted sandboxes.