Cellar is very simple to use. Enter your text and set an expiration. Cellar will then generate an ID for your secret and securely encrypt and store it. After the expiration you have set, the secret is automatically deleted.
Cellar was inspired by the popular Private Bin but has a few key differences.
The primary difference is that Cellar integrates with existing systems to securely handle secrets. For example, it does not handle any encryption itself. Rather, it relies on an existing encryption as a service platform to encrypt your text. That way, you can use whatever system you have in place to encrypt your secret. Cellar also doesn’t do any sort of polling for expiration. Instead, it publishes each secret with a set expiration and relies on the datastore to remove expired data automatically.
Cellar is a quick way to share secrets without the need to authenticate or manage access lists. It’s a great option if you want to quickly share information with someone without the need to create any kind of account.
For example, when your friend needs your address for a wedding invitation. Or maybe your family in another country needs a code to pick up something you sent them. Perhaps, your boss needs the password to a zip file you sent them.
These are all great uses of Cellar. Because Cellar relies on data expiration, access count limits, and randomly generated IDs to restrict access, you know that your data stays safe in transit and is only available as long as you want it to be.
Cellar is not intended to replace proper password manager or authenticated secret sharing practices. If you are looking to permanently share passwords or files, a password manager or a cloud provider may be a better option.
Cellar uses long, randomly generated IDs to access data without authentication or authorization. That means that anyone with the ID that can access your installation of Cellar can read your data. So make sure to set proper expirations and access limits.
Note
If my data is only hidden behind an ID, couldn’t some just guess the ID?
Theoretically, yes. Since there is no authentication, anyone who has the right ID can get to the password. However, the IDs are 32 bytes of randomly generated data. That means there are approximately 6.334028666297328 × 10 ⁴⁹ different IDs. Basically, if a computer could attempt 10 trillion IDs in a second, it would take approximately 2 octillion years to try all IDs.
