A secure, self-hostable service for sharing secrets, passwords, and files with end-to-end encryption and one-time URLs.
Yopass is an open-source web service for securely sharing secrets, passwords, and files. It solves the problem of transmitting sensitive information through insecure channels like email or chat by encrypting data in the browser and providing ephemeral, one-time links for access.
Developers, system administrators, and security-conscious teams who need a simple, secure way to share credentials, API keys, or configuration files without relying on third-party cloud services.
Developers choose Yopass for its strong security model (client-side encryption), ease of self-hosting, and simplicity—no accounts or complex setup are required. It provides a trustworthy alternative to plaintext sharing with full control over data and infrastructure.
Secure sharing of secrets, passwords and files
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Secrets are encrypted in the browser using OpenPGP before transmission, ensuring the server never handles plaintext, as explicitly stated in the description and README.
Links can be configured for single-use viewing with automatic destruction, reducing the risk of unauthorized access, a core feature highlighted in the key features.
Designed without user registration or management, making it quick to deploy and use for ad-hoc sharing, as emphasized in the philosophy and features.
Offers detailed guides for Docker, Docker Compose, and Kubernetes deployments, providing full control over infrastructure, which is a key selling point in the README.
Maximum file upload is capped at 1MB by default, requiring additional configuration for S3 or disk storage, as noted in the server configuration section.
Relies on external services like Memcached or Redis for secret storage, adding deployment complexity and potential scalability issues, as admitted in the setup instructions.
The built-in file cleanup scans all objects on each sweep, which is resource-intensive at scale, prompting the recommendation to use S3 lifecycle rules instead, as detailed in the file storage section.
Lacks built-in user authentication or role-based permissions, making it unsuitable for environments needing audit trails or multi-user management, a limitation implied by the no-accounts design.