Frequently Asked Questions - Clanker Cloud

Clanker Cloud is cloud for agents and agents for humans. It combines Clanker Secretary for computer work, hosted sandboxes and workflows for agents, and Clanker DevOps for infrastructure operations in one workspace.

No. Clanker DevOps is one product path. Clanker Secretary handles office and business work across apps, websites, files, and internal systems, while Cloud for Agents provides hosted runtimes and workflow infrastructure.

It is for individual operators, founders, teams, and businesses that want agents to complete real work, plus builders, DevOps and SRE teams, AI researchers, and developers building agent workflows.

Use Clanker Secretary for work that needs a real computer, Workflow Automation for repeatable office and business processes, Cloud for Agents for hosted sandboxes and agent runs, and Clanker DevOps for cloud and Kubernetes operations.

Yes. You can explore the Clanker Secretary, Workflow Automation, Cloud for Agents, Clanker DevOps, examples, demo, and pricing pages before creating an account.

Clanker Secretary is the computer-use agent inside Clanker Cloud. It can work across approved browsers, desktop apps, files, SaaS tools, internal systems, spreadsheets, research, data entry, reports, and follow-ups on an enrolled computer.

Good fits include reconciling records, updating CRM fields, preparing reports, checking vendor or admin portals, organizing files, researching options, drafting follow-ups, moving data between systems, and returning exceptions for review.

Yes. You can use the web or phone-sized portal when the enrolled desktop app is online and Remote Connection is enabled. Turn remote access off when it is not needed.

Start with the real worker flow, identify the repeatable steps and approval points, then move the stable parts into a hosted workflow with run records, traces, outputs, monitoring, and failure feedback. Work that still depends on a desktop UI can continue through Clanker Secretary.

No. Use Clanker Secretary when the job depends on a browser session, desktop app, local file, or internal screen. API-first and command-based work can run directly in Clanker Cloud sandboxes or hosted workflows.

Teams can keep sends, purchases, deletes, publishes, account changes, production changes, and other high-impact steps behind explicit human approval while low-risk research and preparation continue.

Cloud for Agents gives agents hosted sandboxes with a shell, workspace, lifecycle, workflow records, approval gates, traces, memory, persistent sandbox data, and hosted outputs.

Anonymous users can try short sessions, free accounts can run account-owned work sessions, and active Clanker DevOps or Clanker Secretary accounts get larger Standard sandboxes with no preset expiry. Idle compute can still sleep.

Active Clanker DevOps and Clanker Secretary accounts can publish public, simple static reports, status pages, and compatible previews. Current hosted pages run in an opaque-origin browser sandbox and are not a general replacement for full application hosting.

Yes. Use the Sandbox API, Clanker CLI, MCP tools, or custom Python and Node.js agents to create runs, execute commands, store non-secret workflow state, request approvals, and hand work back to people or other agents.

Do not place secrets in sandbox memory, traces, prompts, or published outputs. Use the local desktop boundary, Clanker Cloud settings, or a separately approved customer-controlled secret path for a contracted deployment.

Teams can combine enrolled worker computers, Clanker Secretary, hosted workflows, agent sandboxes, approvals, and Clanker DevOps in one operating layer. Stable processes can be shared as repeatable workflows instead of living only in one person's browser history or checklist.

Clanker Secretary Pro is the tailored path for organizations with data-governance, privacy, retention, residency, identity, access, audit, and protected-data requirements. It begins with a fit assessment and a separately defined environment.

Customer-cloud, on-premises, protected, and sovereign deployments are separately contracted. They must be scoped, delivered, verified, and activated in writing before private or regulated data is used; they are not current self-service features.

In the normal desktop provider path, cloud credentials and bring-your-own AI keys stay on the local machine. Hosted sandboxes, inference, remote Secretary, and cloud workflows have separate service and data boundaries, so only use data appropriate for the active plan and environment.

No. A plan name, selected region, configuration check, or onboarding step is not a SOC 2, HIPAA, CJIS, CIS, GDPR, or other compliance certification. Required agreements, controls, provider eligibility, and activation must be reviewed for the organization's use case.

Both include a 7-day free trial. The current pricing page shows Clanker DevOps at $9.99 per month and Clanker Secretary at $19.99 per month during the displayed 50% promotion. Clanker Secretary Pro is a custom quote after a free fit assessment.

Clanker DevOps is the infrastructure workspace for deployments, cloud maintenance, incidents, cost checks, security scans, Kubernetes, GitHub, live context, MCP agents, and reviewable change plans.

Clanker Cloud supports AWS, GCP, Azure, Oracle Cloud, Tencent Cloud, Kubernetes, Cloudflare, Hetzner, Railway, GitHub workflows, and more over time. Ansible and Slurm are planned rather than current support.

Yes. Connect the relevant repository and provider context, let Clanker Cloud inspect the current state, review the deployment plan, and approve the execution path before production changes.

Yes. Clanker Cloud supports bring-your-own keys, local models, and OpenAI-compatible endpoints so users and teams can choose the model path that fits the workflow and data boundary.

Yes. Kubernetes support includes EKS, GKE, and AKS for inspection, troubleshooting, live context, cost and security checks, and reviewed operational plans.