Monogram logo
Sharing69 uses in the last 30 days

Keys and passwords, kept per project

Paste a .env, store it per project, reveal on a timer.

Store credentials encrypted, scoped to the project they belong to. Only the people on a project can reveal its secrets, and every reveal is recorded.

How it works

  1. Open a project. Secrets belong to a project. One with no member list is the whole workspace’s.

  2. Paste and store. Add one value or a .env block. The list shows names, never values.

  3. Reveal when needed. The value appears with a copy button and hides again after 45 seconds.

Examples

Real inputs, and what comes back from each of them.

  • You have

    A .env file for a new project

    You get

    One secret per key, named and stored in one step.

  • You have

    A production key for two people

    You get

    A project with just those two. Admins see it exists but cannot open it.

Use cases

Out of chat
Keys live in a vault, not in a thread that keeps them forever.
Scoped to the work
A project’s secrets are visible to its people, and nobody else.
Paste a whole .env
Each line becomes its own named secret.

At a glance

Stored in
Supabase Vault, encrypted, per project
Who can reveal
The people on the project
On screen for
45 seconds
Recorded
Every store, reveal and delete

View all tools
Link ShortenerBranded short links with click analyticsRead moreOne-Time NoteShare a secret on a link that opens onceRead moreEmail CampaignsSend email campaigns and track opensRead more