December 19, 2019


David Klein @dakl

Sneak peek


✅ Domain purchase completed

✅ Hosting setup completed (3core, 8gb, 256gb NVMe, 2x GTX Titan, fully autoscaling to up to 4 additional same-spec machines) -> omfg, this is expensive!

✅ SSL completed

✅ Hash API completed

✅ Verification API completed (for Argon2, BCRYPT, etc.)

✅ Output in JSON and JSONP completed

✅ API documentation completed

✅ Legal content completed (Legal notice, privacy policy, cookie notice)

✅ Stresstest completed (it can handle about a gazillion hashes per second ;) )

✅ MailChimp newsletter setup completed


🔳 Output in XML and plain dump

🔳 Developer kit with composer

🔳 Pre-hashed verification API

SaaS specific unfinished

🔳 Login area

🔳 User specific salts/peppers

🔳 User hashing history

🔳 Payment model

🔳 Stripe integration


🔳 Launch

For this project, I will deliberately not have any form of tracking in place due to the sensitive material that could be hashed. So no Google Analytics, Remarketing tags, GTM, Facebook Pixels, etc. Not even server logs! The only measurement being tracked is revenue in form of subscribed accounts and the total amount of hashes/verifications being made on the platform as a number. That's it.

  1. 1

    Hey David, Have you looked at opentimestamps or any other service? absolutely love the idea.
    I know this is a sideproject but would you add timestamps as a feature?
    You might also want to look at

    1. 1

      Hi Naveen, ok. Sound very interesting. Can you give me an example on how that would work with That would be great! looks awesome! Love it!

      1. 1

        i dont know what the output would look like but I am assuming its a hash(whatever input). What are the uses of just hashing something other than messaging? It would be really valuable if you included a timestamp so I can say "here, I made a prediction at this timestamp, included in the hash, So I am a genius" or something along these lines.
        also check out for some lolz.

        1. 1

          Love your input... but I am pretty blank about how you'd like timestamps integrated? What does is this (warning fake code upcoming):

          GET /hash/myweakpassword1
          OUTPUT ("8473z9roiutzw4oqrzdijqw4it75zdu3i")

          I can add more stuff to the output, that that would just increase request size and make integration harder. I fail to see the benefit of adding timestamps, since the hashes are generated on the fly anyway. I want to store the hash history in each user's account dashboard... there a timestamp does make sense. What we'll not do is to save input & output in the database. Just outputs.

          1. 1

            totally get it, love what you are doing. I might use your apis to post hashes to twitter. let me know when you can share access. Onwards and Upwards.