KrypticKryptic

One daemon. Every project on your machine.

Install the Kryptic daemon, sign in once in your browser, and every project you have access to injects its secrets at startup - macOS, Linux, and Windows.

Latest release

OSArchitectureArtifact
macOSApple Siliconkryptic_darwin_arm64
macOSIntelkryptic_darwin_amd64
Linuxx86-64kryptic_linux_amd64
Linuxarm64kryptic_linux_arm64
Windowsx86-64kryptic_windows_amd64.exeTray app: kryptic-tray_windows_amd64.exe

Every release ships a checksums.txt - shasum -a 256 -c before running, and kryptic update verifies it automatically. All releases: GitHub.

Three commands to a running daemon

macOS

curl -LO https://github.com/dev-kryptic/daemon/releases/latest/download/kryptic_darwin_arm64
chmod +x kryptic_darwin_arm64
./install.sh kryptic_darwin_arm64   # installs CLI + login-time daemon (LaunchAgent)
kryptic login

Runs at login via LaunchAgent. Session token lives in the Keychain.

Linux

curl -LO https://github.com/dev-kryptic/daemon/releases/latest/download/kryptic_linux_amd64
chmod +x kryptic_linux_amd64
./install.sh kryptic_linux_amd64    # installs CLI + systemd user service
kryptic login

Runs at login via a systemd user service. Install secret-tool (libsecret) so the session token lives in your keyring.

Windows

# PowerShell
Invoke-WebRequest https://github.com/dev-kryptic/daemon/releases/latest/download/kryptic_windows_amd64.exe -OutFile kryptic_windows_amd64.exe
powershell -ExecutionPolicy Bypass -File install.ps1   # CLI + tray on login
kryptic login

The tray app runs the daemon and starts at login. Session token lives in Credential Manager.

Your workflow does not change

  1. kryptic login - approve the code in your browser, once.
  2. Add the Kryptic package for your language and a kryptic.json to the repo.
  3. npm run dev, dotnet run, F5 - secrets are just there.