Keep encrypted, reviewable environment configuration with your code. Ghostable gives developers, agents, and CI the right values—without accounts, usage limits, or a hosted secrets server.
$brew tap ghostable-dev/ghostable && brew install --cask ghostable
No account required · Unlimited environments · Free forever
How Ghostable works
Configuration travels with the code. Plaintext doesn't.
Ghostable stores encrypted values and signed access records in .ghostable/. Git moves them; approved devices decrypt only the environments they can use.
Safe in Git
Encrypted records live with the project.
The directory is designed to be committed, reviewed, branched, and merged with the application.
Each key has its own encrypted value record. The environment, key name, version, and encryption method stay visible while the value remains ciphertext.
Ghostable runs where your code runs and keeps encrypted project state with the repository. There is no account to create, hosted secrets service to trust, subscription to renew, or provider-specific setup to migrate.
$0 forever
No subscription.
∞Unlimited environments.
∞Unlimited encrypted variables.
∞Unlimited team members.
No account
Install and go.
Install with Homebrew or npm, initialize the repository, and start in minutes. No workspace or tenant to provision.
No hosted vendor
One less service to trust.
Your plaintext secrets never reach a Ghostable service. There is no additional vendor to audit, approve, or place in your runtime path.
Belongs to the repository
Take it anywhere your code goes.
Ghostable travels with the repository, not the hosting provider. Change clouds, tools, or runtimes without migrating your secrets workflow.
Local machines
The same workflow on macOS, Windows, and Linux.
Agents and worktrees
Encrypted project state follows every development context.
CI/CD runners
Validate and decrypt inside the authorized job.
Any hosting provider
AWS, Azure, Vercel, self-hosted, or whatever comes next.
Works with your stack
If it’s configurable, it’s Ghostable.
Framework-agnostic and native on macOS, Windows, and Linux. If your project reads environment variables, Ghostable fits.
Yes. Ghostable commits encrypted values, signed access records, and reviewable metadata. Keep plaintext .env files and private device identities out of Git.
No. Cloning the repository is not enough. Decryption requires an authorized device identity with access to that environment, or a scoped automation credential.
Each person joins with their own project-scoped device identity. An authorized owner or grantor can approve reader, writer, or grantor access for the environments they need.
Yes. Give CI its own scoped automation credential instead of a human device identity, then grant only the environment and reader or writer role that job needs.
Yes. Revoking a device removes its grants and rotates the affected environment keys. It cannot erase secrets that device had already seen, so rotate those underlying provider credentials when necessary.
Yes. Start from an existing environment file, then move each value into an encrypted record that is safe to review and commit.
Yes. Commit shared validation rules with the project, then run the same checks locally and in CI before a configuration change ships.
The CLI is the primary repository-native workflow for developers and CI. It handles encryption, access, validation, review, and running authorized processes from the terminal.
No. Ghostable Desktop is the optional paid app for people who want a focused visual workflow alongside the CLI. Personal licenses start at $49 one-time.
Yes. Ghostable fits environment-driven workflows across Laravel, Node, Python, Ruby, Go, and similar stacks.
Ghostable Desktop
Take Ghostable to your desktop.
Review environments, validation, and access in a focused visual app. Choose the build for macOS, Windows, or Linux.
