Encrypted at rest

One place for every .env, config, and secret your projects need

Konvoy stores your project files in an encrypted vault, then hands them back through a web editor or a single CLI command — no more emailing .env files or copy-pasting secrets between machines.

1
2
3
4
5
6
Sync ActiveUTF-8
Line Count: 6
How it works

Three steps, no shared spreadsheets

01

Sign in once

Authenticate from the web app or the CLI. Your session is tied to your account, not a machine.

02

Keep files in a project

Group related .env files, configs, and templates under a project. Edit them from the web IDE whenever you need to.

03

Pull them anywhere

Run konvoy projects on any machine, pick a project and a file, confirm the destination, and it's written to disk.

What's here today

Built for the config files you actually deal with

One CLI command to sync

konvoy login, then konvoy projects. Pick a project, pick a file or pull the whole thing, confirm the path, done.

Encrypted at rest

File contents are encrypted before they're stored, and decrypted only when you fetch them for editing or download.

A web editor when you need one

Open any project in the browser to read, edit, and save files without touching a terminal.

Projects, not one giant bucket

Every file belongs to a project. Switch projects to switch context — nothing leaks between them.

The CLI

Pull a file, or an entire project, in one flow

Every step asks before it touches your disk. Select a project, choose whether you want everything or a single file, confirm the exact path, and Konvoy writes it there — nothing runs silently in the background.

No write happens without confirmation
terminal
$ konvoy login
✔ Logged in successfully
$ konvoy projects
✔ Projects fetched
? Select a project » envs
✔ Project selected
? What do you want to create? » A particular file
? Select a file » shahjeeenv
? Create file "shahjeeenv" at ./shahjeeenv? » Yes
✔ File created
Coming next

What we're building after this

01

Team workspaces

Share a project with teammates instead of copy-pasting secrets into chat.

02

File version history

See what changed in a file and roll back to an earlier version.

03

CI/CD tokens

Scoped, read-only tokens so a pipeline can pull files without a user login.

04

Secret scanning on upload

Flag things that look like leaked keys before they're stored.

Stop passing .env files around

Create an account, add a project, and pull it from your next machine with the CLI.

Create your vault