Web Sign-In

Clonit Cloud has a small landing site hosted at your cloud deployment’s public URL (for example, https://clonit.ai). From there you can sign in to confirm your account and reach the connect page, which walks you through downloading the CLI and linking it to the cloud.

Web sign-in is for confirming who you are and getting set up. The day-to-day work — building, sanitizing, pushing, and pulling snapshots — happens in the Clonit CLI and its local web UI, not on the cloud landing site.

Note

Clonit Cloud is optional. Every core Clonit operation works standalone with no cloud account. Web sign-in only matters once your team uses Clonit Cloud for shared snapshots and cross-device access. See the Clonit Cloud overview.

Where to sign in

Open your cloud deployment’s public URL in a browser. The landing page describes what Clonit Cloud does and shows two buttons:

• Sign in — start the browser sign-in flow (see below).
• Download CLI — jump to the latest CLI release.

If your account is brand new, use the Create an account link beneath the buttons first. There’s also a Manage account link for updating your profile.

Caution

If you don’t see a Sign in button — only guidance to install the CLI and run clonit login — then web sign-in isn’t enabled on that particular deployment. That’s a deployment configuration choice made by whoever runs the cloud. You can still sign in from your terminal with clonit login; see Sign In & Login.

How browser sign-in works

Clonit Cloud does not store your password or run its own login form. Identity is handled by a separate auth service, so signing in always happens there:

1. You click Sign in on the cloud landing page.
2. Your browser is redirected to the auth service, where you authenticate (including single sign-on, if your organization uses it).
3. After you approve, the auth service redirects your browser back to the cloud.
4. The cloud confirms your session and lands you on the connect page.

You never type an API key or password into the cloud landing site itself — the auth service owns that. From your point of view it’s a normal “sign in with your identity provider” round-trip.

Note

Single sign-on (SSO/OIDC) and account creation are managed entirely by the auth service and your identity provider — not by Clonit Cloud. If your company uses Okta, Google, or another SSO provider, you’ll sign in through it during step 2.

The connect page

Once you’re signed in, you land on the connect page. This is the page to come back to whenever you want to set up a new machine. It has three parts.

1. Signed-in confirmation

A “Signed in” badge confirms your session, along with:

• Organization — the Clonit Cloud organization you’re signed in to.
• Role — your role in that organization (for example, owner, admin, member, or viewer). Your role determines what you can do; see Organizations & Teams.

2. Download the CLI

A Download the CLI box links to the latest Clonit release. The page detects your operating system and offers a Download for your platform button, plus a View all releases link if you need a different platform.

The CLI is the binary you actually run to snapshot, sanitize, push, and pull databases. Install it before moving on. See the Installation guide.

3. Connect your agent

A Connect your agent box gives you the exact steps to link the CLI you just installed to this cloud — using the same browser-based login, with no API keys to copy or paste.

The steps it shows are:

1. Point the CLI at this cloud. Run clonit config edit and set cloud.url to your deployment’s URL:

   cloud:
     url: https://clonit.ai

2. Sign in from your terminal:

   clonit login

   A browser window opens for you to approve the login — the same approval you did on the landing page. Clonit discovers the auth service from the cloud automatically, so cloud.url is the only value you have to set.

3. Confirm you’re connected:

   clonit whoami

Tip

This is the same flow documented in detail under Connect Your Agent. The connect page is just the fastest place to copy the exact cloud.url for your deployment.

What happens after you sign in

Browser sign-in confirms your identity and points you at the CLI — it doesn’t move data on its own. Once your agent is connected with clonit login, you can:

• Push & pull snapshots through the cloud with the --cloud flag.
• Share sanitized snapshots with your organization.
• Use the Cloud section of the local web UI (clonit serve) to browse shared snapshots, targets, and organization settings.

Note

Signing in through the browser and running clonit login are two separate sessions. The browser session lives in your browser; the CLI session is stored on your machine in ~/.config/clonit/credentials.json and is refreshed automatically. Signing out of one does not sign out the other — use clonit logout to clear the CLI session.

Web sign-in vs. CLI login vs. API keys

Clonit Cloud has three ways to authenticate. Pick based on what you’re doing:

Method	Who it’s for	When to use it
Web sign-in (landing page)	A person in a browser	Confirm your account, download the CLI, copy the connect steps
clonit login	A person at a terminal	Link an interactive workstation to the cloud (OAuth device grant)
API key (cloud.api_key)	Automation	CI/CD and other headless agents that can’t open a browser

Tip

Use a browser (web sign-in or clonit login) for your own machines, and reserve API keys for CI/CD and other non-interactive automation.

See Also

• Clonit Cloud overview — What the optional cloud extension adds
• Sign In & Login — How browser-based login works end to end
• Connect Your Agent — Link the CLI to the cloud in detail
• login command — Reference for clonit login
• whoami command — Show the current Clonit Cloud login
• API Keys — Authenticate CI/CD and headless automation
• Installation — Install the Clonit CLI