Set up a CLI profile
Copy page
Create a CLI profile and authenticate with Inkeep Cloud
Profile setup is only required when pushing or pulling to a remote deployment (Inkeep Cloud or a self-hosted instance). If you're pushing or pulling locally, you can skip this step.
A CLI profile tells the CLI where to connect and how to authenticate with a remote deployment. This tutorial walks you through creating a profile and logging in.
Prerequisites
- Access to Inkeep Cloud or a self-hosted deployment
- The Inkeep CLI installed globally:
Step 1: Create a profile
Profiles let you manage multiple environments (cloud, local, staging) from the same CLI. Create a profile for Inkeep Cloud:
The CLI prompts you to configure the profile:
- Remote type:
- Select Inkeep Cloud if you have an Inkeep Cloud account (URLs are configured automatically)
- Select Local for local development (localhost defaults, no authentication required)
- Select Custom for self-hosted deployments, then enter your API and Manage UI URLs
- Environment name: Enter
production(or your preferred name) - Credential reference (Cloud and Custom only): Enter a name for your credential (defaults to
inkeep-<profile-name>)
You can verify the profile was created by running inkeep profile list.
Step 2: Set the active profile
Set the profile you created as the active profile:
Confirm which profile is active:
Step 3: Log in
Authenticate with your active profile:
The CLI will:
- Open your browser to the Inkeep authentication page
- Display a device code (e.g.,
ABCD-1234) - Wait for you to complete authentication in the browser
Once authenticated, you'll see confirmation:
Your credentials are securely stored in your system keychain. You only need to log in once per profile.
Managing multiple profiles
You can create profiles for different environments and switch between them:
To authenticate a specific profile without switching:
To remove a profile you no longer need:
For a full list of profile commands, see the CLI Reference.