lot of feedback from them. We’ve transacted about a half a million licence keys during that process. And then at the same time we’ve started to build out our own front end for the platform. The API functionality


is great and it’s important to have it because large


companies will want to continue to use their existing systems and to connect them in a way that does not create any additional work. But smaller publishers may not have the systems, so they will have to have a platform that they can use where they can set up these items without requiring API access or API functionality. So that’s essentially the idea. And that also means that the shift from being a small publisher to going to a large scale enterprise is not a problem within the system, because it’s able to handle everything either manually with the platform itself, or, fully automated to API, or anywhere in between.


WHO IS SIGNED UP? We’ve been, as I said, working with a bunch of different partners that includes publishers, distributors and storefronts. We’ve had very good discussions and we’re now looking to demo and provide sample access to a lot of these partners to really play with the system. Some of them have been playing with it during the API stage. Some of them will now start playing with it. And some of them we’ve already had very in depth feedback and that’s been very helpful. We’re hoping that by the end of Q3, early Q4, we’ll actually see them transacting on the live environment, with real partners and real traffic. Before then, at gamescom specifically, we’ll be providing access to our sandbox environments so that we can do tests with these guys on a larger scale. In terms of the partnerships, it’s really a big range.


We’ve had a bunch of different triple A publishers, smaller publishers and a few indies as well. We’ve been having discussions with a lot of different storefronts.


WHAT WILL VAULTN LOOK LIKE TWO, THREE, FOUR MONTHS FROM NOW? So what we’re looking to expand in the future is the capability of DRM. So allowing publishers to manage DRM better inside the platform, even without requiring a specific DRM solution that they have in place maybe already. We’re also looking very specifically at mobile and we believe that with mobile slowly opening up, with the walled gardens of Apple and Google slowly


40 | MCV/DEVELOP September 2022


being regulated, this will provide a lot of opportunity for third party distribution in the coming years. We’ve seen this already in play in Southeast Asia, to some extent in Japan and Korea. But for now, the first part is to get the product to


market, to learn from the feedback. And then, based on the feedback from all of our partners, work very closely with them to understand what they need, why they need it, how it’s helping their process so that they can maximise the use of the platform. That will really help them to automate and standardise their processes and distribution and thus grow their revenue.


FINALLY, YOUR LINKEDIN PROFILE SAYS THAT YOU ARE “BUILDING A STANDARD FOR NFT AND BLOCKCHAIN GAME DISTRIBUTION ACROSS METAVERSES”. WHY IS THERE NO MENTION OF NFTS OR THE METAVERSE ON THE VAULTN SITE? When we started the project we thought it would be a good chance to be based on NFT/blockchain technology, but realised that it’s not the right time yet to launch the service based on those components. There have been scams and dubious practices with the technology that’s left a lot of people doubting it, ruining the potential advantages. We still believe blockchain might play an interesting role in distribution (e.g. to enable decentralised en/decryption), but we believe the core benefits of VaultN for our users and partners are making their life easier and that’s what we focus on: bringing digital B2B distribution to the 21st century.


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64