Quickstart

Updated August 16, 2026

Get Kryptic running locally in four steps. Total time: about three minutes.

1. Install the daemon

Download the binary for your platform from the download page, or grab it straight from GitHub releases. The install scripts register the daemon to start at login (LaunchAgent on macOS, systemd user service on Linux, tray app on Windows).

# macOS (Apple Silicon)
curl -LO https://github.com/dev-kryptic/daemon/releases/latest/download/kryptic_darwin_arm64
chmod +x kryptic_darwin_arm64 && ./install.sh kryptic_darwin_arm64

Then sign in - a browser opens, you approve a device code, done:

kryptic login

The rotating session token is stored in your OS credential store (Keychain, Credential Manager, or libsecret). Access tokens live in daemon memory only.

2. Add kryptic.json

Commit a project config to your repo root. It contains no secrets - safe for version control. Your project's exact file is on the project page in the dashboard, one click to copy.

{
  "projectId": "proj_a1b2c3d4e5f6",
  "defaultEnvironment": "development"
}

3. Add the package for your language

One dev dependency, one line at startup. Every package is a thin MIT-licensed client that asks the daemon for your secrets over a local socket - see the per-language pages for .NET, Node.js, Python, Java, Go, Ruby, and C++.

npm install --save-dev krypticdev

// top of your entry point
require('krypticdev').inject();

4. Run your app

npm run dev

That's it. Secrets are in process.env (or IConfiguration, os.environ, ENV, …) before your code reads them. Existing environment variables are never overwritten, and in production the package is a no-op.