The current VivoKey Identity platform is centered around the idea of chip scan authenticated identity services. Our vision was to enable partners who wished to develop services around our identity APIs. We had several partnerships in motion, and some were even developing services. The problem was that none of these services materialized, and under the pressure of the pandemic, partners and partnership arrangements vaporized.
VivoKey is now considering re-developing a new service platform that still enables chip scan based authentications, but is built in such a way that it will be centered around services VivoKey deploys directly for our members. Before we set about developing such a platform however, we wanted to create a limited access proof of concept program to test several assumptions about how such a platform would work.
There will be several key differences between how the two platforms will work, but the two biggest differences include the use of handles and the introduction of services under a subscription fee.
The current VivoKey Identity Platform does not use “handles” or usernames. That’s because the entire premise was that we would be doing away with account names and passwords and instead authenticating you based on “you” (you upgraded with a chip implant of course). The entire platform was based around this premise, and extending identity and your ability to prove your identity (authentication) was how it was built. Unfortunately, the Internet is not built that way and there is only so much we can deviate from the norm before our efforts begin hindering themselves. The absence of account names was one of these problems. So, the new service platform will actually require the registration of an account name or handle.
As a service platform provider, we intend to roll out multiple services directly to members ourselves. These services will often come with direct hard costs as well as operational costs for servers, storage, bandwidth, etc. It will not be possible to deploy any direct service offerings unless those services are funded by subscription fees. Our goal however is to maximize the number of services deployed under a base level subscription, and not “nickle and dime” our members.
For certain services however, there will be an a la cart approach, and activating certain specific services will carry additional recurring subscription charges. This is because some of the service we intend to deploy carry a significant direct per-user cost from the 3rd party providers we intend to license those services from. However, the primary difference between the Service Platform approach to deploying these 3rd party services and the current Identity Platform approach to 3rd party services is that under the Service Platform model, VivoKey will be the customer of the 3rd party, coming to license services as a group. Under the current Identity Platform model, each VivoKey member would need to sign up as an individual customer of each 3rd party service that has enabled the VivoKey Identity Platform.
There are several services VivoKey has already identified which could be deployed for VivoKey members, however we will only be testing a single service within the boundaries of the proof of concept program. The service we’ve chosen for this PoC is, Google Workspace. Deploying Google Workspace accounts to test participants will allow all the features of Google Workspace (formerly GSuite) such as email, Google Drive, and many other Google services.
That might seem like a pretty soft offering for a PoC test service, but there is an extremely interesting feature that you’ll be able to use once you have your Workspace account activated. You will be able to use your Google Workspace account to do passwordless authentication with VivoKey chip scan authentication for any 3rd party website or service which offers a “Log in with Google” feature. You simply sign up and sign in “with Google”, enter your Google Workspace email address as the username, and then you will immediately be taken to authenticate with VivoKey chipscan. No password.
• Must be a VivoKey member with active profile in current VivoKey Identity Platform.
This means you must have a Spark and have active access to your profile within the VivoKey Identity Platform. You must know your PIN code and be able to access your VivoKey app. This also means your email address must be validated within the VivoKey system.
• The PoC test program will be subscription based like the Service Platform intends to be.
We have not decided yet on a base subscription fee yet, but current thinking is around the $20/mo range. Yes this is quite steep for a single service as part of a test program, but this is also part of the validation process, so we want to ensure as the test program continues to run past the first few weeks that people will see enough value in it to continue with the subscription. Also this base level subscription fee will, as part of a properly developed Service Platform, cover multiple services, not just Google Workspace.
• The PoC environment will be temporary. Migration of data will not be possible.
Because this is a PoC test program built on some bubble gum and toothpicks, we cannot make any claim that the exact accounts you will be setting up with 3rd parties or data you will be storing on your VivoKey licensed Google Workspace accounts will be accessible after the PoC test program is closed. Please bear this in mind when creating accounts with service providers, giving out your VivoKey email address, or storing data on your Google Workspace account drive. We do plan to give ample notice before the PoC test program is closed down, but we cannot guarantee there will not be technical issues which may cause loss of access to these accounts and data. Therefore we suggest only using the PoC test accounts and service as exactly that - a test.
• Limited number of participants
At this time we are only going to consider a very small number of people for the PoC test program. We need to manage an entire manual process of creating accounts, setting up handles, linking things together, etc. and interacting closely with participants to ensure we maximize the program’s value - namely identifying pain points and validating user experience. To do that properly, we’ll need to keep in close communication with each participant.