Hosted catalogs

Everything on this page is optional. The catalog is a file in your project and every command works without an account; hosting removes the setup work, not a feature.

What it does

Keeps a copy of your sealed catalog, so a new machine has it after envs login instead of after a file transfer.
Lets you share one catalog with your team, and take that back the moment someone leaves.

What the server cannot do

It stores bytes it cannot open. Your key never leaves your machine, so there is no search, no diff, and no page anywhere that shows a value — not to us, and not to anyone who reaches the storage.

A free account can do all of it on your own S3 or R2 instead: envs backup --to s3://your-bucket. That is the same sealed snapshot, in a bucket you own.

Sharing with a team, and the part people miss

An invitation gives a teammate access to the sealed bytes. It does not give them the key, because the service does not have your key to give.

So a teammate needs two things from you, and only one of them travels through us:

What	How it reaches them
Access to the catalog	the invitation code you send them
The key that opens it	you hand it over yourself — your password manager's sharing, or any channel you would trust with the values themselves

Give them ENVS_KEK, or one of the recovery codes envs init printed. A teammate who has joined but has no key can fetch the catalog and will not be able to read it, which is the design working rather than something broken.

When someone leaves, remove them and their access stops at once. Rotate the key as well — they may still have the copy they already opened. envs rotate --key does that and keeps every value.

Command	What it does
`envs team invite`	prints a one-use code on stdout; it expires, and it is not stored anywhere you can read it again
`envs team join <code>`	accepts it on their machine
`envs team ls`	who has access, and whose catalogs you can reach
`envs team remove <member>`	ends their access at once

Price

Plan	Price	Includes
Monthly	USD 3 / month	Synced catalogs and team sharing. No seat pricing — the subscription covers your team.
Yearly	USD 30 / year

Both renew until you cancel. If a subscription lapses your local catalog keeps working exactly as before — only syncing stops. Nothing locks.

Getting started

envs login
envs whoami
envs backup --to envs://

envs login prints a short code to approve in a browser, so it works over SSH. Your catalogs and team are listed on your account page.