We are the Sniptt team and we believe there should be a better way for engineering teams to manage secrets.
We are building tools that bring easy and secure secret management to the fingertips of developers and development teams. The Snip CLI allows users to create, manage, and share end-to-end encrypted secrets with others straight from the terminal. Say hello to Vaults, one-time self-destructing URLs, and more.
P.S. Yes, you can finally say goodbye to password managers! 😎
- 🔐 End-to-end encryption: Secrets are encrypted using OpenPGP, the most widely used messaging encryption standard.
- 👾 For developers, by developers: Protect and share secrets directly from your terminal.
- 🔗 Immutable and cryptographically verifiable (coming soon): Stay comforted knowing that every secret has a complete and verifiable history of changes over time. Powered by Amazon QLDB.
- Little to learn - Sniptt should be easy to learn and use as the API is quite small. Not having abstractions is better than having the wrong abstractions, and we don't want users to have to hack around the wrong abstractions. Mandatory talk - Minimal API Surface Area.
- Zero knowledge architecture - We take a "trust no one" approach to your security—we never trust any server, code, or person with access to user data in order to give you the best protection.
We believe that as developers, knowing how a library works is helpful in allowing us to become better at using it. Hence we're dedicating effort into explaining the architecture and various components of Sniptt with the hope that users reading it will gain a deeper understanding of the tool and be even more proficient in using it.
If you find issues with the documentation or have suggestions on how to improve the documentation or the project in general, please file an issue for us.