Clonit Cloud
Clonit Cloud extends the Clonit CLI with team collaboration: a snapshot catalog your whole organization can reach from any device, snapshot sharing, managed storage, and cloud-side AI sanitization analysis. Clonit Cloud builds on the standalone CLI — connecting changes nothing about your local workflow, and you can disconnect at any time without losing local data.
What Cloud adds
Section titled “What Cloud adds”When you connect Clonit to Clonit Cloud, you gain:
- A snapshot catalog you can reach from any device. Register an agent on each machine, and your organization’s snapshots, targets, and storage profiles show up everywhere you sign in — laptop, CI runner, or a teammate’s workstation.
- Team sharing. Mark a sanitized snapshot as shared and the rest of your organization can pull it. Share originals only with the people who need them, and distribute clean, sanitized copies to everyone else.
- Organization and team management. Invite members, assign roles (owner, admin, member, viewer), and organize access through SSO groups synced from your identity provider.
- Managed storage via presigned URLs. Push and pull through the cloud without configuring S3 or R2 credentials on every machine. The cloud hands the agent a short-lived presigned URL, and the agent uploads or downloads directly to managed storage.
- Cloud-side AI sanitization analysis. Run sensitive-column detection server-side, per organization, so a shared analysis and generated sanitization query are available to your whole team — using either a per-organization Anthropic key or the deployment’s shared key.
Works alongside standalone
Section titled “Works alongside standalone”Cloud-aware commands only do anything when cloud is configured. Until you set a cloud URL and credentials, those commands explain that cloud is not configured and exit cleanly.
The two storage pathways live side by side. Plain push/pull use a
local storage profile (your own bucket). Adding the --cloud flag opts a
single command into the cloud pathway instead:
clonit push mydb # → your S3/R2 via the target's local storage profileclonit push mydb --cloud # → your org's managed storage via a cloud presigned URLSigning in: humans vs. automation
Section titled “Signing in: humans vs. automation”Clonit Cloud separates interactive human sign-in from headless automation:
- Humans run
clonit login, which signs you in through your browser using an OAuth 2.0 Device Authorization Grant (RFC 8628). Clonit prints a short code and a URL, you approve in your browser, and the session is stored locally and refreshed automatically. No API key or password is ever typed into the terminal. Identity, SSO, and single sign-on are owned by an external auth service — Clonit runs no login form of its own and stores no passwords. - CI/CD and other automation authenticate with a Clonit Cloud API key instead. The key is a machine credential that scopes everything it does to one organization, ideal for unattended pipelines.
A typical cloud workflow
Section titled “A typical cloud workflow”clonit login # sign in through your browser (humans)clonit cloud register # register this machine as an agentclonit cloud sync # publish target names/types to the catalogclonit build mydb # capture a snapshot locallyclonit sanitize mydb # strip sensitive dataclonit push mydb --cloud # upload the sanitized snapshot to managed storageA teammate on another machine then signs in, finds the shared snapshot, and pulls it:
clonit pull mydb --cloud --snapshot-id <id>See Push & Pull via Cloud for the full upload and download flow.
Where to go next
Section titled “Where to go next”- Sign In & Login — interactive browser sign-in
with
clonit login, sessions, andwhoami/logout. - Web Sign-In — sign in to the cloud landing site in a browser.
- Connect Your Agent — configure the connection, register a machine, and sync targets.
- Push & Pull via Cloud — move snapshots through
managed storage with
--cloud. - Sharing Snapshots — share sanitized snapshots with your organization.
- Organizations & Teams — members, roles, and SSO groups.
- API Keys — machine credentials for CI/CD and automation.
- Service-User CI — run pipelines as a least-privilege
service user with a
cak_key. - Cloud AI Analysis — server-side, per-organization sanitization analysis.
See also
Section titled “See also”- cloud command — manage the Clonit Cloud connection and resources from the CLI.
- serve command — the web UI’s merged Targets / Snapshots / Storage Profiles views and Settings → Organization manage all of the above in a browser.
- Cloud Storage guide — set up your own S3/R2 storage profiles for the standalone push/pull pathway.