NEW Configuration contracts and signed snapshots →

Your configuration has a working tree.

Jnana versions, resolves, and safely delivers every environment variable and config file—across branches, developers, CI, and production.

See how it works ↓
✓ Browser-side encryption✓ Git-aware environments✓ No credit card
atlas-commerce / feature/billingUnlocked
EFFECTIVE CONFIGURATION

One validated plan for this checkout.

01
developmentBase · 18 values
+
02
joseph/localPersonal · 4 values
+
03
stripe/testOverlay · 7 values
◇
Policy check passedNo production resources referenced.
42 ready
DATABASE_URLAWS Secrets ManagerReady
STRIPE_SECRET_KEYJnana · stripe/testReady
REDIS_URLEncrypted Jnana vaultReady
◫
Snapshot signed43 settings · 4 sources
just now

Stop passing .env files through Slack.

Stop rebuilding config from memory.

Stop wondering what production received.

THE CONFIGURATION WORKSPACE

Everything between Git and your secrets manager.

Keep values encrypted, keep structure reviewable, and make every checkout reproducible.

⌘

Branch-aware resolution

Map branches to environments and compose personal, team, and feature overlays without copying files.

Explore feature →
≡

Configuration contracts

Scan code to discover required settings, types, consumers, and gaps before runtime.

Explore feature →
◫

Signed snapshots

Create value-free receipts proving exactly which versions and providers produced a deployment.

Explore feature →
↔

Provider-agnostic

Resolve from Jnana, AWS Secrets Manager, 1Password, Git defaults, and your own adapters.

Explore feature →
◇

Policy before exposure

Block production values on unsafe branches and require approvals for sensitive environments.

Explore feature →
↗

CLI, containers, everywhere

Hydrate local checkouts, CI jobs, Docker services, mobile approvals, and desktop workflows.

Explore feature →
ZERO-KNOWLEDGE BY DESIGN

The vault password never leaves your device.

Values are encrypted with AES-256-GCM in your browser before upload. Your account password authenticates you; a separate vault passphrase controls your configuration.

✓ HTTP-only, same-site sessions

✓ Keyed fingerprints for safe deduplication

✓ Isolated environments and databases

✓ Keychain-backed local CLI agent

J
Your values

encrypted locally

Plaintext→AES-256-GCM→Ciphertext
Only ciphertext reaches Jnana infrastructure.
BUILT FOR THE TERMINAL

One command from clone to configured.

The dashboard and CLI use the same versioned API. Start visually, automate when ready.

$ jnana init
$ jnana contract scan --write
$ jnana unlock --ttl 30m
$ jnana hydrate

✓ 42 settings resolved from 4 sources
✓ .env written with 0600 permissions
SIMPLE FROM DAY ONE

Start alone. Bring the team later.

Developer

Free

For personal projects and local workflows

  • ✓3 projects
  • ✓Unlimited versions
  • ✓CLI + web workspace
  • ✓Browser-side encryption
MOST POPULAR

Team

$15/ user / month

For engineering teams shipping together

  • ✓Unlimited projects
  • ✓Policies and approvals
  • ✓Provider connections
  • ✓Audit history

Enterprise

Custom

For regulated and complex organizations

  • ✓SSO and directory sync
  • ✓Workload federation
  • ✓Dedicated deployment
  • ✓Security review support
Configuration should be infrastructure.

Give every checkout the right values—without giving away the keys.