Ferrum Editor
Code editor
A small, hackable code editor in the spirit of Atom, written from scratch in Rust and configured in plain TOML.
Learn more about Ferrum EditorA password-locked vault for your projects' environment variables, with encrypted sharing between developers.
Your projects' environment variables in one encrypted file instead of loose .env files. Share them with a teammate as an encrypted bundle, sealed with a key you exchange once.
shop · development · Locks in 29 min
What the encryption protects, and what it can't. Both lists come from FerrumEnv's own documentation. The security page has the details.
The encryption, bundles and .env parsing are unit-tested; the window is covered by headless tests.
The master password is asked on every start, and nothing is decrypted before. The vault locks after 30 minutes without activity (or 5, 15 or 60), and ⌘L locks it at once.
A project links to a folder and starts with development, staging and production. Each variable has a key, a value, an optional comment and a secret flag.
Reveal one value or all of them. A copied value is cleared from the clipboard after 30 s if it's still there, and at once when the vault locks.
Share all or chosen environments as encrypted text or a .fenv file. Before an import, you see what will be added, changed or removed, by key name only.
Each project has a 256-bit key shown as fek1_…, with a checksum that rejects typos and a short fingerprint to compare out loud. Rotate it to cut someone off from future bundles.
Import .env, .env.local, .env.production and the rest from a project folder. Write an environment back to a .env file with mode 0600, copy it as text, or compare two environments.
FerrumEnv is in alpha. Its tests are automated; the app hasn't been clicked through by hand yet.
A forgotten master password can't be reset. Keep it somewhere safe.