explaingit

burnerpad/burnerpad-lite

Analysis updated 2026-05-18

12ElixirAudience · developerComplexity · 3/5LicenseSetup · moderate

TLDR

A one-time secret sharing tool that encrypts in your browser and destroys each secret after a single view, with no accounts or database.

Mindmap

mindmap
  root((repo))
    What it does
      One time secret links
      Burn on read
      No accounts
    Tech stack
      Elixir
      Bandit
      JavaScript
    Use cases
      Share passwords
      Self host privately
      Temporary credentials
    Audience
      Developers
      Ops teams

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Share a password or API key with a coworker without leaving a permanent record.

USE CASE 2

Send a one-time link for sensitive personal information that should not be stored anywhere.

USE CASE 3

Self-host a private, short-lived secret sharing service instead of relying on a public one.

USE CASE 4

Build a small internal tool for temporary credential sharing.

What is it built with?

ElixirBanditJavaScriptDocker

How does it compare?

burnerpad/burnerpad-liteelixir-vibe/vibe_kitgabrielperales/phoenix-email
Stars121618
LanguageElixirElixirElixir
Setup difficultymoderateeasyeasy
Complexity3/52/52/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires Elixir 1.18+ and pulling in a git submodule for the browser crypto library.

You can use, modify, and self host this freely, but if you run a modified version as a network service you must share your source changes under the same license.

In plain English

Burnerpad is a simple, no accounts tool for sharing a secret one time. You paste text you want to send, like a password or a private note, and the tool gives you a link. When the person you send it to opens that link, the secret is shown once and then destroyed. There is no account to create and nothing is saved to a database. The encryption happens in your browser before anything is sent, so the server never sees the plain text of what you shared. The key needed to unlock the secret never reaches the server either. Everything is kept only in memory while the app runs, with a countdown until it expires automatically, and it disappears completely if the server restarts. The project is built with Elixir and a small web library called Bandit, with no database and no JavaScript framework. The browser side uses a few small handwritten scripts plus a separate, audited encryption library that is pulled in as a pinned dependency. To run it yourself you need Elixir 1.18 or newer, and you can start it for development, package it for production, or run it in Docker. Since it only serves plain HTTP, you would put something like Caddy in front of it to add HTTPS. There is a small API for creating and retrieving secrets by script, plus a public status page showing overall usage numbers like how many secrets are currently stored, without revealing anything about individual secrets. A terms and acceptable use page is included too, filled in with the operator's name and contact details through environment variables, so anyone running their own copy needs to update those settings and should have a lawyer check the wording before using it publicly. Testing includes an Elixir test suite along with checks for the browser encryption code, and an optional browser based test that walks through a real user flow. The whole project is small by design: one main dependency, no accounts, no persistence beyond a short lived timer. The code is licensed under AGPL 3.0 or later, while the separate crypto library it depends on uses the more permissive Apache 2.0 license.

Copy-paste prompts

Prompt 1
Help me set up Burnerpad locally with Elixir 1.18 and run it in development mode.
Prompt 2
Show me how to deploy Burnerpad in Docker behind a reverse proxy for HTTPS.
Prompt 3
Explain how Burnerpad's one-time secret API works so I can call it from a script.
Prompt 4
Walk me through configuring the operator name, abuse email, and jurisdiction settings for my own Burnerpad instance.

Frequently asked questions

What is burnerpad-lite?

A one-time secret sharing tool that encrypts in your browser and destroys each secret after a single view, with no accounts or database.

What language is burnerpad-lite written in?

Mainly Elixir. The stack also includes Elixir, Bandit, JavaScript.

What license does burnerpad-lite use?

You can use, modify, and self host this freely, but if you run a modified version as a network service you must share your source changes under the same license.

How hard is burnerpad-lite to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is burnerpad-lite for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.