Skip to main content
Your Inkly account ties together your hub, your published demos, and the tools that can publish on your behalf.

​
Sign in

Sign in from the hosted Inkly app. Your account gives you access to the dashboard, editor, settings, analytics, and connected hub. The sign-in options available to you depend on your workspace setup. Common options include GitHub, Google, and email.

​
API keys

The CLI and browser capture extension use API keys so they can publish, sync assets, and manage previews without asking you to sign in for every command. Open Settings → API keys to review and revoke keys.
You rarely need to create a key by hand. inkly login and the capture extension connection flow create and store keys for you.
Treat API keys like passwords. Revoke a key if you lose a device, rotate credentials, or no longer use an integration.

​
Connect the CLI

Run inkly login to connect the CLI to your account. 
inkly login
The command opens a browser approval flow. After you approve access, the CLI saves a local key for future publishing commands. Use inkly status to check whether the CLI is connected. 
inkly status
Use inkly logout to remove the saved key from your machine. 
inkly logout
For command flags and automation options, see Publish a demo.

​
Connect the capture extension

The Chrome capture extension connects from the Inkly app when you choose a Chrome extension capture flow.
1

Start a Chrome extension capture

In Inkly, choose the Chrome extension path when you create or add to a demo.
2

Install or connect the extension

If the extension is not installed, Inkly opens the install prompt. If it is installed, Inkly detects it and connects your browser profile.
3

Capture and upload

After connection, the extension can upload captured demos and assets to your account.
If a machine is shared, lost, or compromised, revoke the extension key from Settings → API keys and connect again when needed.

​
First-time setup

The first time you sign in, Inkly asks you to create or connect a hub. You choose a hub slug and connect the GitHub repo that backs the hosted site. After setup, your hub has a hosted URL, and publishing flows can update it from your repo or create standalone snapshots. See Hosting and publishing.