qikenv-cli

Secure .env sync and environment variable management from your terminal.

qikenv is a CLI for managing environment variables, syncing .env files, and sharing development secrets across teams without copying credentials through Slack, email, or issue trackers. It connects your local project to a Qikenv workspace so you can pull encrypted environment variables, push local changes, detect drift, and keep development, staging, and production configuration in sync.

Keywords

environment variables, .env sync, dotenv, secrets management, env file manager, CLI secrets, secure environment variables, team secrets sharing, encrypted .env, development secrets, staging environment variables, production environment variables, config management, secret sync, env vars, doppler alternative, dotenv alternative env variables manager for teams

Why developers use qikenv

• Sync .env files across local machines, teammates, and environments.
• Manage secrets for development, staging, production, and preview apps from one workspace.
• Pull environment variables into a local .env file with one command.
• Push new local variables back to your team when configuration changes.
• Detect drift between local .env values and the remote workspace.
• Avoid insecure secret sharing over chat, email, screenshots, or copied files.
• Keep project and environment links in a small .qikenv.yml manifest.

Installation

Install the environment variable CLI globally with npm, pnpm, or Yarn:

npm install -g qikenv-cli

pnpm add -g qikenv-cli

yarn global add qikenv-cli

After installation, the qikenv command is available in your terminal:

qikenv --help

Quick start

1. Log in

Authenticate your device with your Qikenv account:

qikenv login

Use --server if you are connecting to a self-hosted or custom API:

qikenv login --server https://your-qikenv-api.example.com

2. Link a project

Run link inside the repository that needs environment variables:

cd my-project
qikenv link

The CLI fetches your organizations, projects, and environments, then creates a .qikenv.yml file for the selected workspace target.

3. Pull environment variables

Fetch remote variables and write them to .env:

qikenv pull

Inspect values without writing to .env:

qikenv pull --inspect

Overwrite an existing .env without a confirmation prompt:

qikenv pull --force

4. Check for drift

Compare your local .env file with the remote environment:

qikenv status

You will see which variables are synced, missing locally, new locally, or different from the workspace.

5. Push local changes

Publish new or changed local .env variables to the remote environment:

qikenv push

Delete remote variables that are no longer present in local .env:

qikenv push --prune

Skip confirmation prompts in automation or trusted workflows:

qikenv push --force
qikenv push --prune --force

Common workflows

Onboard a new developer

npm install -g qikenv-cli
qikenv login
qikenv link
qikenv pull

Update local secrets after a teammate changes them

qikenv status
qikenv pull

Share a new API key with your team

echo "STRIPE_SECRET_KEY=sk_test_example" >> .env
qikenv push

Files qikenv uses

• .qikenv.yml: links the current repository to a Qikenv project and environment.
• .env: the local environment file that qikenv pull, qikenv push, and qikenv status read or update.
• ~/.qikenv/credentials.json: stores your authenticated CLI session.

Commands

| Command | Description | | ----------------------- | ------------------------------------------------------------------------ | | qikenv login | Authenticate your local device with Qikenv. | | qikenv link | Link the current directory to an organization, project, and environment. | | qikenv pull | Download environment variables and write them to .env. | | qikenv pull --inspect | Preview variables without modifying files. | | qikenv pull --force | Overwrite an existing .env without prompting. | | qikenv push | Upload local .env changes to the remote workspace. | | qikenv push --force | Push creates/updates without a confirmation prompt. | | qikenv push --prune | Delete remote variables that are missing from local .env. | | qikenv push --prune --force | Prune remote-only variables without a confirmation prompt. | | qikenv status | Report drift between local .env and remote variables. |

Security

qikenv is built for safer secret management workflows. It helps teams replace manual .env file sharing with authenticated CLI access, encrypted variable sync, project-level configuration, and clear local drift checks.

Never commit .env files to source control. Commit .qikenv.yml only when you want teammates in the same repository to link to the same Qikenv project and environment.

Platform

Manage organizations, projects, environments, team access, billing, and audit history in the Qikenv dashboard.

Documentation: https://qikenv.com/docs