Your env vars,
locked and shared the right way.

Jex aide les équipes à exploiter leur propre vault de secrets chiffré. Auto-hébergez l'API, le tableau de bord et la base de données, puis récupérez ou injectez les secrets avec la CLI Go.

Open-source et auto-hébergé · Chiffrement AES-256-GCM · RBAC · Journal d'audit

Pangolin mascot guarding encrypted secrets
The problem

Your secrets are scattered.

Every team develops workarounds. None of them are secure. Jex fixes the root cause.

No more Slack DMs

Sharing secrets over chat is a security incident waiting to happen. Jex gives every team member the exact keys they need, with no message history to audit.

No more stale credentials

One vault, one source of truth. When a secret changes, every developer and every environment gets the update automatically, with no manual sync.

No more accidental commits

jex run injects secrets at process launch: in memory, never to disk. No .env file, no accidental git add, no exposure in your repository history.

Comment ça marche

Trois étapes. Démarrez en cinq minutes.

De la configuration au déploiement : une commande par étape, et rien en clair entre les deux.

01
Vault

Stockez vos secrets, chiffrés

Ajoutez vos secrets au vault via le tableau de bord ou la CLI. Chaque valeur est chiffrée avec AES-256-GCM avant d'atteindre la base de données.

02
CLI

Récupérez ou injectez à la demande

Utilisez jex secrets pull pour écrire un fichier .env atomique, ou jex run pour injecter directement dans l'environnement de votre processus.

03
Exécution

Votre application, avec ses secrets

Votre processus démarre avec les secrets dans son environnement. Chaque membre, pipeline CI/CD et environnement reçoit exactement les clés autorisées.

jex workflow
$jex secrets set DATABASE_URL=postgres://...
Set DATABASE_URL in dev.
$jex run -- node server.js
12 secrets injected · no disk write
$cat .env
cat: .env: No such file or directory
Features

Everything a team needs.

Built for developer teams who take security seriously without sacrificing developer experience.

AES-256-GCM Encryption

Every secret is encrypted before it reaches the database. The server never holds plaintext values — your keys, your control.

Role-Based Access Control

Project admins, developers, and read-only roles. Scope CI/CD tokens to a single environment. The last project admin can never be removed.

Environment Segmentation

dev, staging, prod — each environment is isolated. A member scoped to dev cannot read prod secrets, by design.

Append-Only Audit Trail

Every read, write, and delete is recorded atomically alongside the secret operation. Immutable. Filterable. Always consistent.

CI/CD Tokens

Create scoped tokens for pipelines with read-only access to a single environment. Revoke them instantly — no cache, no delay.

Self-Hostable

Run the full stack with docker-compose up. Open-source, MIT licensed. No vendor lock-in, no data leaving your infrastructure.

Self-host first

Run Jex on your infrastructure.

Deploy the stack, then install the CLI and point it at your team's Jex API.

$ npm install -g jex-secrets
# After your self-hosted instance is running
$ jex login --api-url https://jex.yourcompany.com
$ jex init
$ jex secrets pull
$ jex run -- npm run dev
Jex — Secrets Manager for Developer Teams · Jex