Sharable self-destruct messages

About Instapass

Security is unnecessary hard and time-consuming

And, when it is hard and time-consuming, it is often not taken care of. It is so much easier to email a password than setting up a secure system. But, then when emailing anyone gaining access to your email forever will have the password. It is easier to send a email or instant message with a token than to setup some fancy encryption. In other words, it is frustrating to do the right thing.

What to do instead?

Use Instapass.

Why is Instapass Secure

Instapass automatically encrypts your message on the client-side with industry standard algorithms (using the Stanford Javascript Crypto Library). The encrypted message is sent to the Instapass server. Due to the fact that Instapass only receives encrypted data, we are not able to read the message. Afterwards, a link is generated on the client-side and the password is added as an anchor to the url. Anchors are designed not to be sent to the server, but only used locally by the browser. After the link expires or has been used the encrypted message is deleted from the server. This helps to increase the protection from hackers, NSA and other curious people, as they cannot access passwords by just hacking your email, Slack server, or Git service.

Inhouse hosting

Maybe you want or are required to host Instapass inhouse? We can help you host Instapass inhouse using Docker Compose or Kubernetes. Fill in the following form to and we can have a meeting about a solution for your company.


If you like this, have suggestions, or you are in need of a quality and security minded developer, please contact me either by email or by the form below

Found a bug?

Please contact me below or by email. I will be happy to receive any feedback and I will not charge you of any crime if what you do is to merely show a bug or vulnerability.

What is next

Currently I am developing new premium features. To get news about this subscribe on the index page.