Wickr

» see wickr.com as it lived, on the wayback machine

~ the last words ~

wickr sat in the part of internet history i can read about but cannot personally remember using. encrypted messaging in 2012 was something i was aware of as a category, but the specific app i was on in turkey was whatsapp from 2010 onwards (everyone in my contact list was already there) and then telegram from 2015 onwards once whatsapp's facebook acquisition made some friends nervous. signal arrived in my orbit around 2017 as the activist-and-journalist pick, the one you installed for one specific conversation and then forgot about. honestly, wickr was a name i saw in security blog post tags and never installed.

wickr was founded in january 2012 in san francisco by a team led by nico sell and dr. robert statica, with a public launch in june 2012 on iOS. the pitch was end-to-end encryption with message-expiry timers down to a few seconds, plus screenshot detection on the apple side. the snowden disclosures in 2013 gave the category a real moment, and wickr was one of the named alternatives in the wired and guardian explainers that followed. by 2014 the company had taken $30 million in series b funding including a $1.6 million check from in-q-tel, the cia's venture arm. erik prince showed up on the cap table around the same time. the eff gave the app a 5 out of 7 on the 2015 secure messaging scorecard, with deductions for closed source code and limited security documentation.

amazon web services acquired wickr on june 25 2021 with the announcement framed around enterprise customers and the us department of defense, which had a wickr contract for tactical communications. the consumer wickr me app continued to operate for about eighteen more months. the shutdown announcement came in october 2022, with new signups closing on december 31 2022 and the full service ending on december 31 2023. aws kept wickr enterprise as a paid b2b product under the amazon brand, used by government agencies and large corporations for compliance-friendly encrypted communications. the consumer brand is the part that died, the enterprise sku is the part that survived.

~ the record ~

~ what it was ~

the product was technically real. wickr used a custom protocol with curve25519 key exchange and aes-256 message encryption, with the keys generated locally on the device and never transmitted to the server. the message-expiry timer let you set messages to disappear anywhere from a few seconds to several days after read. the ios app would detect screenshots and notify the sender, the android app could not because of platform restrictions. the company published technical white papers and submitted to outside cryptographic review by kevin paterson and matt green, which was more transparency than most consumer crypto apps offered at the time. honestly, the feature set was solid, the brand never crossed over.

~ the funny part ~

in-q-tel money in a privacy app was the joke that stuck. the agency invested $1.6 million in 2014 and the wickr team explained that the cia wanted secure communications for its own analysts, not back-door access to other users' messages. that explanation was technically defensible but the meme had already formed. nico sell defended the funding in interviews and pointed out that no investor had product access or special privileges, which was true under the architecture but unconvincing to the part of the security community that had read every reuters story about the agency's prior dealings with rsa security. erik prince's involvement as a personal investor a year later did not help the optics either. honestly, the people who needed pure-paranoia encryption moved to signal or session, the people who needed business-compliant ephemerality stayed on wickr until aws bought it.

~ what came after ~

aws wickr enterprise is the product that continues as of 2026, sold as a b2b sku for government and defense customers plus regulated-industry clients. the consumer story is what ended. signal absorbed the cohort that had wanted free encrypted ephemeral messaging. telegram absorbed the cohort that did not care about end-to-end as much as it cared about feature breadth, and the in-between layer that wickr had carved out simply did not have enough mass to justify a free consumer tier inside amazon. there is no consumer migration path, the wickr me servers were turned off on the last day of 2023 and the message data went with them. honestly, that is the right behavior for a product that had promised ephemerality from day one. the final consumer-side wickr team had already mostly rotated out by mid 2023, the announcement was administrative more than anything else.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »