We built the KYC orchestration layer we wished existed
Founded in 2025. Philadelphia, PA. Independently funded. Building the compliance infrastructure that fintechs and regulated platforms actually need.
The origin
Adrian Koslov and his co-founder spent three years building compliance infrastructure at fintech companies before IDPylon. They kept running into the same problem: KYC vendors sold static pipelines. Every applicant got the same passport-plus-selfie flow, regardless of whether they were a low-risk returning customer or a newly created account trying to pass a high-value transaction.
The manual review queues grew. The real users dropped off. IDPylon was built to fix the routing layer, to make the check fit the risk, not the other way around.
The team
Previously built KYC compliance tooling at two fintech companies. Studied computer science at Drexel University.
Machine learning engineer focused on document classification and fraud signal extraction.
Former BSA officer. Brings regulatory examination experience to the product design process.
How we build
No false compliance claims
If we have not earned a certification, we do not claim it. This is a compliance product, we hold ourselves to the same standard.
Friction is a cost
Every unnecessary verification step has a dollar cost and a drop-off cost. We measure both.
Audit-ready or don't ship
Every decision IDPylon makes for your users is logged, timestamped, and explainable. If we cannot defend a verification decision to a regulator, we will not make it.