alonp99

https://twitter.com/_akhaliq/status/1607410840562458624

Stay tuned, It's just the beginning of it ;)

Thanks! I guess…

One of the things we’d like to achieve with it being open source is actually a community that will contribute and collaborates on new practices that are best for both the companies and their customers and less for criminals.

Thats an amazing feedback Dan, I would love to have a short call to pick your brain if you're up for it. ill reach on linkedin

Again, good points! this is exactly what we want to take off of the dev/CTO shoulders when going into the CRO’s office, we might need to do a better job communicating what the project is about.

- You can choose where to store the data, you can either keep it in the vendor's hand if it's more comfortable for the CRO or use your own AWS and GCS for specific geographies (e.g. GDPR). for those who have access to the data we have RBAC built-in into the back office, we’ve seen that most companies are actually building their own back office since identity verification providers usually won't give something operational for manual approvals - so getting one that is built with best practices in mind and maintained by a community is a big benefit in a security aspect.

- Each company that deals with such processes have its own regulatory framework they are under and they are obliged to assign personnel to build and maintain a policy and make sure the company acts according to it it.

- You can orchestrate that entirely, using whatever data source you need, by using an existing integration or adding a new one.

- This is a big plus for having a community that is spread across multiple geographies and can help build local solutions that will make the system global (stuff like which data you need to collect, how much time data should be stored, in what area it should be stored, and which vendors works best with specific data).

Solid points. from what we’ve seen it defers between different companies.

Each company has its own preferences, some find it less optimal to send IDs to a 3rd party, and some don’t want to host it themself, and this is why we built it to be entirely modular. It means you can either use a vendor in the backend (for fraud, file storage, AML, or anything else) or do stuff on your own, we want to make sure the underlying infrastructure won't break when you mix and match those. we do it by standardizing the data and how all modules talk with each other.

From what we’ve seen it really depends on what service the company is giving, who are the customers, and sometimes the size of the company.

We used Onfido for quite a while, we think you guys are great. I think the solutions you're comparing here are different in more ways than where it is hosted.

For example, This project is about not being tied to a specific vendor, all modules are completely vendor agnostic.

let’s say that you start with one vendor and after a while, you either are not satisfied with the results and want to switch a vendor without changing your internal operations workflow or maybe you have a new geography to cover and you need another vendor for it that will fit the rest of the tools you are using, with this project you can use the same tools to send your document to whichever vendor you want.

We built it for customization from the ground up, and since it's open source - it's at the code level. we expect to see UI packs, flow and vendor compositing, liveliness challenges, etc all developed in the community and for the community to use.

Hey, thanks for the comment.

Its true, a document and a selfie are not enough in some cases. there are a couple of technics to make a better guess if the selfie was live but they are not good as liveliness checks.

We already started to work on a liveliness step with a customizable challenge, meaning the developers can configure what action the user should perform in this step (like turning the head in a specific direction, perform hand gestures, and more).

The mobile SDK's will have more sophisticated tools to detect fraud, we will write about it soon.

They are all migrated into “web-sdk”

We will remove ui-components for now to avoid confusion, thanks for the heads up

Thanks! We are trying to take those stuff away from developers and have it built in the infrastructure - such as built-in RBAC, access logs in the backoffice, and integrations to s3 and GCS that are controllable at per-user level.

Thanks, yeah you’re right, we’ll add it to our GitHub readme page. And for the rest, I’ll just add here that KYC/B stands for “Know your customer/business” and it is common in the onboarding process of financial services, healthcare, gambling, education, etc. in which a company is gathering information/documents and verifying who they give service to.

We how are focused on giving a complete solution for identity and risk management, that is open-source and free.

For monetization, we have a few methods: 1. Aside from the ability to bring your own vendor and use us for free, we do offer a fast way to start verifying users by using vendors we have commercial agreements and pre-set integrations with. 2. Enterprise features common in other OSS companies.

Thanks alot!

Thanks ! we are on it!

Thanks! that was part of our motivation behind it. you can read this blog post about KYC UX from our experience previously working together at a Neobank, by Nitzan who is leading the Product on this project: https://vaulted-law-a70.notion.site/Creating-the-perfect-KYC...

The front end was the first part that we open-sourced and we are working to migrate the rest, we are planning to make a complete identity and risk stack a commodity.

Hey, thanks for the comment. you’re right, eKYC is definitely the future of identity verification and after building the basic identity stack, we plan to add eKYC methods like verification using only the phone numbers and ID numbers. eKYC is not in a solution that is not globally supported though, yet.

Part of our vision is to standardize this data to allow companies to partner and “vouch” for verified users - so users won’t need to send their documents all over and by doing so we may reduce leakage exposure.

About the automation part, the flows are vendor agnostic and can be connected to any vendor. we are in the process of open-sourcing a backend where you can orchestrate IDV, Risk, Fraud, Document classification, and OCR vendors.

I miss counter-strike

Is there any benchmarks that includes deno delpoy?