The simplest way to add passwordless auth to websites & apps

DID is the fastest and simplest way to get authentication done on your website. DID authenticates with a key pair stored on the user’s device. Authentication is instant and passwordless. DID is an identity provider compatible with Oauth and Open ID Connect.
Would you recommend this product?
6 Reviews5.0/5
Hi everyone, We are Peter and Richard and we are excited to share DID with you. DID was created so that we could all stop using passwords. Most of us have too many passwords and we don't like using them. Not wanting to remember the details of another account is often the reason I don't sign up for a new service. Creating DID has show us there can be a better way to handle authenticating for a service. We really like it and hope you do to. Let us know what you think, and we are of course happy to answer any questions. Cheers
Genuine paradigm shift - this can do wonders for conversion rates by reducing friction.
@duarteosrm Thanks Duarte. I think there is certainly potential for supercharging conversion rates, particularly once a DID user who already has already trusted a device visits a new website using DID, they can sign in with just one click. There is such a lot of friction with asking a user to choose a username and password. Our challenge is evidencing that improvement in conversion rate in order to sell that as a feature. Hopefully in time, working with our community of users, we'll be in a position to evidence significant improvement in conversion rate.
@richardesigns I look forward to implementing it!
@duarteosrm wonderful! Please let me or Peter know if you would like any help.
I've been impressed whilst trialing this. I thought the first site I visited with DID was almost frictionless but it just get's better with each site after that. I've not tried jumping between devices, how is that handled?
@lewisea thanks for the kind comments. We handle recovery of accounts via email. It is also possible to use you email to add multiple devices to the same account. All of this is handled by DID and when building a website or app you will just have a single identifier for the user to work with
@lewisea Hi Lewis, thanks for your question. If you signed up using your mobile phone, for example, and then wanted to sign in on your laptop DID issues a link to your email which you use to authenticate on the new device. You can choose to authorise multiple devices, a phone, a laptop, a tablet for example. DID then provides you, the end user, with a list of all the devices you have authorised so you can easily manage them. This is slightly easier, we've found, than trying to use a password manager across multiple devices. Does this answer your question?
I've previously liked the idea of using social accounts, which prevents the user from having to deal with yet another password. Plus you can rely on that social network's security measures. However, I've always hated that you're essentially locking your users into a 3d party company. With DID's approach, you have the same benefits, without the lock-in!
@almarklein cheers. Another problem that we aim to fix vs those social login solution, is that we don't have a business model that relies on tracking our end users as the sign in to different services
Super interesting, as passwordless login has been a friction point for us, in finding the right "balance" of pleasing users. (Some love passwordless, some want passwords, some want SSO via social, but having all of these would be ultra confusing and result in multiple accounts). I actually inadvertently have multiple PH accounts due to bouncing between their SSO options. Brutally-honest nitpick - your explainer video comes across as very amateurish with the low-budget, animate-a-doodle stuff. This is a big step in the right direction for user experience and tech, and should be treated as such in that video. I'd recommend dropping the goofy music and doodles and focus on a clean video that shows exactly what the end user would see/experience using DID, as well as a few points addressing security measures taken. Hope that helps, and good luck!