The people behind Aikin.
A lean team that punches well above its weight — founders with 20+ years shipping software for large financial institutions, paired with blockchain-native engineers and AI-orchestrated delivery.
Meet the team
Based in the Netherlands, with a distributed team across the UK and Turkey.
Nick Oneill
Product — Co-founder / CEO
Originally from Australia and now based in the Netherlands with his wife and two sons, Nick brings over 20 years of experience building software products. His brutally transparent approach to product management cuts through inefficiencies and waste to deliver impactful products. As a leader, his goal is to build an elite team that creates world-class software.
Paul Kemp
Engineering — Co-founder / CTO
With three decades of software expertise across investment banks and insurance companies, Paul brings deep knowledge of designing and delivering high-impact solutions for complex financial systems. His career has been defined by precision, adaptability, and getting things right where failure isn't an option. Based in London, Paul also has a deep love of music — the piano in particular.
Baran Ulcar
Engineering
Baran Uçar — from Turkey — combines a deep curiosity for science and mathematics with meticulous technical expertise in software engineering, primarily focused on backend development. Experienced in blockchain technologies, particularly ICP, Rust, Motoko, and TypeScript/React, he also has practical expertise in designing tokenomics. He enjoys bridging theory and practice through thoughtful, deliberate engineering.
Ilyas Unar
Engineering
A dedicated software developer from Turkey with a passion for turning complex challenges into elegant, user-friendly solutions. He has built a diverse background in both front-end and back-end development on the Internet Computer, pairing his academic pursuit of computer science with a deep curiosity about the fundamentals of computing. He believes decentralised applications benefit humanity.
Want to work with us?
Every engagement begins with a conversation about your problem, your architecture, and what the right next step actually looks like.