Introducing BurnLink CLI

Developers weren't meant to share secrets through email, Slack, or cloud storage.

Yet we've all emailed ourselves a .env file, pasted API keys into chat, or uploaded sensitive files to services that keep copies indefinitely.

We built BurnLink CLI to provide a better way.

BurnLink CLI lets you send files directly from your terminal as one-time, self-destructing links.

The recipient downloads the file once, it decrypts locally, and the encrypted copy is permanently removed from the server.

How it works

burnlink send ./secrets.zip

Encrypts the file locally, uploads it, and returns a secure one-time link.

burnlink receive <code>

Downloads the file, decrypts it on the recipient's machine, and permanently deletes the server copy.

Why we built it

We wanted a file-sharing workflow that feels native to developers:

• Client-side encryption before upload

• One-time downloads with automatic destruction

• No accounts

• No tracking

• No permanent storage

• Simple terminal-first workflow

Whether you're sharing .env files, SSH keys, deployment configs, certificates, or sensitive archives, BurnLink keeps the process fast and private.

The web app is already live, and we're putting the finishing touches on the CLI. The waitlist for early access is now open.

Join the waitlist: Waitlist

BurnLink is open source and built with one goal: making secure file sharing as simple as running a command.

We'd love your feedback, feature requests, and ideas as we continue building.