Documentation

SnapPwd creates one-time, expiring links for passwords, secrets and files. These pages cover running it yourself, calling the API, using the CLI, and how the encryption works.

Self-Hosting

Run the open-source API, Redis and the static web client with Docker Compose. Covers every environment variable, the HTTPS requirement, abuse protection and what the self-hosted client cannot do.

API Reference

Four REST endpoints for creating, peeking at and retrieving one-time secrets and files. Request and response fields, limits, status codes and curl examples run against a local instance.

CLI Tool

Encrypt and share secrets and files from a terminal with @snappwd/cli, then peek at or retrieve them. Works with the hosted API or your own instance.

Security Architecture

How a secret is encrypted in the browser, why the key stays in the URL fragment, and how the reveal step keeps link scanners from consuming a one-time link.

The API (snappwd-service), the self-hosted web client (snappwd-web), the CLI (snappwd-cli) and the agent skill (snappwd-skill) are open source under the MIT license. The hosted app at snappwd.io is not.