Quickstart - Infisical

Every Infisical product that has a CLI workflow starts the same way: install the CLI, log in, and check that the CLI can reach your Infisical instance. This page covers those steps, then links to the command reference.

Prerequisites

An Infisical account on Infisical Cloud or on a self-hosted instance

Step 1: Install the CLI

Install the CLI with the package manager for your operating system.

brew install infisical/get-cli/infisical

winget install infisical

scoop bucket add org https://github.com/Infisical/scoop-infisical.git
scoop install infisical

npm install -g @infisical/cli

curl -1sLf 'https://artifacts-cli.infisical.com/setup.deb.sh' | sudo -E bash
sudo apt-get update && sudo apt-get install -y infisical

curl -1sLf 'https://artifacts-cli.infisical.com/setup.rpm.sh' | sudo -E bash
sudo yum install infisical

apk add --no-cache bash sudo wget
wget -qO- 'https://artifacts-cli.infisical.com/setup.apk.sh' | sudo sh
apk update && sudo apk add infisical

yay -S infisical-bin

Check that the installation worked:

infisical --version

Step 2: Log in

Log in with your own account when you run the CLI yourself, such as on your laptop during local development. Log in as a machine identity when the CLI runs without you, such as in a CI/CD pipeline, a container, a scheduled job, or a script on a shared server.

If your Infisical instance is behind a service that requires its own headers, such as Cloudflare Access, set those up first.

Your own account
Machine identity

Authenticate the CLI with your Infisical account.

infisical login

The prompt asks which instance you want to use. Select Infisical Cloud (US Region), Infisical Cloud (EU Region), or Self-Hosting or Dedicated Instance, then finish signing in through your browser.

On a machine with no browser, such as a remote SSH session, WSL 2, or Codespaces, run infisical login -i to log in from the terminal instead.

The CLI saves the instance you select with your login, so later commands use it without asking again.

Follow the Universal Auth guide to create a machine identity and get a Client ID and Client Secret for it.

If you use EU Cloud, a dedicated instance, or a self-hosted instance, set INFISICAL_DOMAIN to the address of your instance. A machine identity login doesn’t save the instance, so without INFISICAL_DOMAIN every command goes to US Cloud (https://app.infisical.com).

export INFISICAL_DOMAIN="https://your-domain.infisical.com"

setx INFISICAL_DOMAIN "https://your-domain.infisical.com"

On Windows, setx saves the variable for new sessions only, so restart PowerShell before you run the next command.To set the instance another way, such as with the --domain flag or in .infisical.json, see Set the Infisical instance.

export INFISICAL_TOKEN=$(infisical login --method=universal-auth --client-id=<identity-client-id> --client-secret=<identity-client-secret> --silent --plain)

--plain prints only the token, and --silent hides update and tip messages, so the command’s output is just the token. The CLI reads INFISICAL_TOKEN automatically, so every later command in the same shell is authenticated.

Step 3: Check that you’re logged in

infisical login status

The CLI asks your Infisical instance whether your login is valid. If it is, the output starts with the account or machine identity you’re logged in as, followed by the instance the CLI connected to:

✓ Authenticated as <your-email-or-identity-name>
  - Domain: https://app.infisical.com

The lines after Domain include when your login expires and which organization it belongs to. If the output says You are not authenticated, log in again. If it says Failed to authenticate, check that the Domain line shows your instance, then log in again.

You successfully installed and logged into the Infisical CLI.

Next steps

Now that you’ve installed the CLI and logged in, you can start using its commands.

Command reference

See every CLI command, with its arguments, flags, and examples

​Prerequisites

​Step 1: Install the CLI

​Step 2: Log in

​Step 3: Check that you’re logged in

​Next steps

Command reference

Prerequisites

Step 1: Install the CLI

Step 2: Log in

Step 3: Check that you’re logged in

Next steps