for development and automation

Secrets for scripts, CI and AI tools — without .env files.

Secrets for scripts, CI and AI tools often end up in .env files, repositories and command history. Anyone who reaches the file can see them.

How we help

01available

Store the secret in a Vault

Keys, tokens and passwords stay encrypted on your device, not in a file next to the code.

02available

Hand it to a script through the Geslar CLI

The read, inject and run commands give the secret to a command, and the output is masked.

03available

Give AI tools only what you approve

MCP for AI tools works with approvals. The GitHub Action gives secrets to CI.

Today, soon, planned

today · available
  • Geslar CLI: read, inject and run with output masking
  • GitHub Action
  • MCP for AI tools, with approvals
  • Machine identities (20 per organization with Škrinjar Teams)
  • Decrypted on your computer

Geslar cannot see your content. Your company's administrators can access the company's Vaults. Data in the EU.

Frequently asked questions

Do I need a .env file?

No. The Geslar CLI gives secrets from the Vault straight to the script or command.

What does an AI tool see?

MCP for AI tools works with approvals: you decide what the agent may use.

Where are secrets decrypted?

On your computer. Geslar cannot see your content.

Want this at your company?

Prices and the package comparison are on the Pricing page.

Guide: Passwords and access in a small business · Free, sent by email.