Introduction

packshell keeps your .envfiles in sync across a team without a secret ever leaving a developer's machine in plaintext. Encryption happens locally; the server only ever stores ciphertext it cannot read.

Sharing environment variables is one of the messiest parts of working on a team. They end up pasted into chat, attached to tickets, or copied between machines by hand — and once a secret has been seen by a server, it has to be trusted with it. packshell removes that trust requirement entirely. Your.env is encrypted with a project key on your own machine, and only the resulting cipher blob is uploaded. Teammates who hold the project key decrypt it locally when they pull.

What you get

• End-to-end encrypted sync. Push and pull encrypted environment versions from any machine with the CLI.
• Per-member key wrapping. The project key is wrapped individually for each teammate with their public RSA key, so access is granted without ever exposing the key itself.
• Versioned history. Every push is a new immutable version with a checksum, so you can see what changed and when — without the server seeing values.
• Team controls. Companies, projects, roles, invites, and an audit log of every push, pull, invite, and key share.

The 30-second version

# install the CLI$ npm install -g packshell# connect this machine to your account$ packshell auth# link a project in your repo, then push your .env$ packshell init$ packshell push

How the pieces fit

A company is your workspace. Inside it you create projects, and each project has one or more environments (like development orproduction). You work with all of this from the CLI in your repo, and manage people, plans, and history from the web dashboard.

packshell is built by Acadable Labs and is open source under the MIT license. Ready to set it up? Continue to installation.