Share.env
FeaturesUse casesPricingCLI
Log inStart for free

Your team's secrets deserve better than Slack

Upload your first .env file and see what secret sharing looks like with real access control.

Product

  • CLI
  • API documentation
  • Service status

Legal

  • Privacy policy
  • Terms of service
  • Cookie policy
  • Security
Send an email

share.env

© 2026 share.env. All rights reserved.

Built for teams who take secrets seriously.

Pricing Free .env Sharing for Up to 3 Environments

Start free with up to 3 environments. $2 per environment per month after that, billed monthly, with unlimited team members on every plan.

share.env Pricing: Simple, Pay for What You Use

Every team starts free. Only pay when you add environments beyond the first three.

Free

$0/ month

For individuals and small teams getting started.

  • Up to 3 environments
  • Unlimited team members
  • AES-256 encryption at rest
  • Expiring share links
Start for free
Most teams

Pay as you go

$2per environment / month

For teams that outgrow the free tier. The first 3 environments always stay free.

  • First 3 environments free
  • Billed monthly per environment above that
  • Same encryption and access control
  • Cancel anytime
Get started

How much will you actually pay?

Drag the slider to match your team's environments and watch the bill update instantly.

First 3 are free. 3 additional environments billed monthly.

Estimated bill$6per month

Stop pasting secrets into chat

The way most teams share environment variables today creates a permanent, unencrypted, unrevokable copy of your secrets.

Slack, email, or a shared doc

  • API keys sit in searchable chat history forever
  • Anyone in the channel can read them, no access control
  • No way to know who copied a secret or when
  • Rotating a leaked key means guessing who still has it

share.env

  • Files live encrypted in a workspace, never in a chat log
  • Owner, editor, and viewer roles enforced by the database
  • Every access and change is recorded with a timestamp
  • Revoke a link or a member's access in a single click

Security enforced at the database, not the UI

Every table in share.env has Row Level Security turned on. A hidden button in the interface is not a permission boundary. A policy is.

Row Level Security on every table

Postgres policies decide who can read or write a row before your application code ever runs, so a bug in the UI can't leak another team's secrets.

create policy "workspace_members_select"
on public.env_files for select
using (is_workspace_member(workspace_id, auth.uid()));

AES-256 encryption at rest

File contents are encrypted in Supabase Storage. Nobody, including us, reads a .env file outside of an authorized request.

High-entropy share tokens

Links are generated with cryptographically secure tokens, always carry an expiry date, and can be revoked the moment access should end.

Full audit trail

Every change to a file is recorded with who made it and when, so security reviews take minutes instead of days.

Fits into the pipeline you already have

Pull the current environment straight into local development or a CI/CD run, without anyone copying secrets by hand.

  • Official CLI for local development and scripts
  • Drop-in step for GitHub Actions, GitLab CI, and Vercel
  • Scoped tokens per project, never your personal login
  • Every pull is logged like any other file access
$ envshare login  ✓ authenticated as marta@acme.dev$ envshare pull --workspace api --env production  ✓ decrypted 14 variables into .env.production$ envshare link create --env production --expires 24h  ✓ https://share-env.app/l/9f2a1c...  expires in 24h

Billing questions

What counts as an environment?+

Any distinct .env file you upload to a workspace, for example production, staging, or a per-branch preview file. Re-uploading the same file doesn't create a second one.

Do the first 3 environments ever expire?+

No. The free tier is permanent for up to 3 environments, not a trial. You're only billed once you add a 4th.

Can I remove an environment to lower my bill?+

Yes. Deleting an environment removes it from that month's count immediately, and the next invoice reflects the change.

Is there a limit on team members or storage?+

No. Team members are unlimited on every plan; pricing scales only with the number of environments you store.

Stop pasting secrets into chat

Create a workspace, upload your first .env file, and share it with your team in under two minutes.

Create an account