Where to Find Dotenvx Installation, Quickstart, and Pricing Information

Updated

The Dotenvx website (dotenvx.com) is the entry point for all three: the homepage carries Install and Quickstart links, the Usage section shows the core encrypt/commit/run commands, and a Pricing link points to https://dotenvx.com/pricing for plan details. Use the homepage if you want to evaluate the tool and get running; use the pricing page only if you need plan specifics, since the homepage itself doesn't state prices.

Installation and Quickstart

The homepage presents two adjacent entry points, Install and Quickstart, aimed at getting Dotenvx onto your machine and running a first encrypted .env. The site describes Dotenvx as "a secure dotenv–from the creator of dotenv," so the quickstart assumes you already have a .env file and a project that loads environment variables.

What the page does not spell out is the exact install command or supported package managers; those details sit behind the Install link rather than on the homepage. Expect the quickstart to walk you from an existing .env to an encrypted one and then to running your app with the decrypted values injected.

The Three Commands You'll Actually Use

The Usage section is the most concrete part of the site. It reduces the workflow to three commands:

Step Command What happens
Encrypt dotenvx encrypt Values in .env become ciphertext; only your private key can unlock them
Commit git add .env then git commit -m "encrypt .env" The encrypted .env travels with your code in git
Ship dotenvx run -- node index.js Your private key decrypts and injects secrets just-in-time into the process

The run example reports injected env (2) from .env, which tells you how many variables were loaded — a quick way to confirm the step worked. The same pattern applies to other runtimes: swap node index.js for your framework's start command.

What the Design Section Tells You Before You Commit

Before adopting the commit-your-.env workflow, the Design section explains the tradeoff you're accepting. Dotenvx is built on three primitives: Git for distribution, .env as the open standard for loading secrets, and secp256k1 (the curve behind Bitcoin) for encryption. The stated goal is to let secrets travel with code "without becoming part of the code" — the decryption key stays on your infrastructure, separate from the repository.

The practical consequence: anyone with repository access can read the ciphertext but not the values, and your deployment needs exactly one private key set in the environment. That single-key model is presented as the alternative to async secret coordination and centralized secret stores, so weigh it against your team's key-rotation and access-control needs.

Pricing

A Pricing link in the site navigation leads to https://dotenvx.com/pricing. The homepage excerpt does not include plan names, prices, or whether a free tier exists, so treat the pricing page as the only authoritative source and check it directly rather than inferring cost from the open-source framing.

Suggested Path

  1. Open dotenvx.com and follow Install for your platform.
  2. Run the Quickstart against a test .env in a scratch repository — not production secrets — to see the encrypt/commit/run cycle end to end.
  3. Confirm injection with the injected env (N) output from dotenvx run.
  4. Visit the Pricing page if you need plan details before rolling it out beyond a trial.