I build data systems, AI and blockchain products for work where mistakes are expensive — and I'm building my own ventures alongside it.
Before the case studies, the part you actually buy: how a job goes from a conversation to a system your business runs on. Five steps. Keep scrolling.
You describe the business, not the software. Where the time goes, what gets typed twice, which number nobody trusts. I leave that call able to explain your work back to you.
Every screen and every step is drawn and agreed while changing it still costs nothing. You see the product before it exists — and say no to the parts you don't want.
Data model, integrations, security and the load it has to survive — decided up front. A system that only works at today's size is a rebuild with a delay on it.
Deployment is a written command, not a person clicking through a panel. Updates ship the same way, so a fix reaches your users the day it's written.
Sales, usage, stock, whatever matters — live, in one place, on your phone. Not a report someone prepares on Monday: the actual state of the business, right now.
Projects I worked on at the companies I've been part of — all live today. Each one carries the single decision it stands on.
A shared photo album for an event. Guests upload straight from their phone, and face recognition files every photo under the people in it — so everyone downloads their own set without chasing a Drive link or waiting on AirDrop.
Next.js · face recognition · Python · S3 · no login
live ↗A board-game and arcade platform: quick HTML5 titles built on a reels-style loop, played head to head. Tournaments, ladders and prize pools that settle on-chain.
Next.js · HTML5 Canvas · Solana Web3.js · Anchor · WebSocket · Redis
live ↗Crypto wallet risk assessment for compliance teams: real-time scoring across chains, fund-flow tracing, mixer detection and sanctions screening.
React · Node.js · Python · PostgreSQL · Blockchain APIs · Machine Learning
live ↗The game portal for the OXS ecosystem — design, frontend and the fullstack work behind it: player accounts, wallet-linked assets and the dashboard where each game and its economy is watched.
Next.js · TypeScript · ethers.js · PostgreSQL
live ↗Corporate site for an international food distributor: product catalogue, multi-language content and an animation layer that stays out of the way.
Next.js · Framer Motion · Tailwind CSS · Vercel
live ↗Years of keeping other people's products running. These days I'm doing the same for my own ventures — and I can do it for your business.
A new venture, currently under construction. The domain is ready; the product is not — yet.
Numbers you can actually trust, reports that write themselves, a process that stops needing a person. Tell me what you do by hand every week and I'll tell you what it takes to stop. There is very little that can't be automated.
Let's talkFour years from someone else's dashboard to my own product company. The direction is the point.
OXS Games Dashboard and Rudolph — the first production systems where a wrong number on screen meant a wrong balance in someone's wallet.
GameCup.io settles prizes on-chain; oxs.games becomes the portal for the ecosystem; OXS KYT scores wallet risk live for compliance teams; Mako Food ships as a fast, near-maintenance-free corporate site.
As the systems grew I wrote the tooling that installs and updates them — a command instead of a dashboard. A dashboard hides what actually ran; a command leaves a record.
helindogu.erayucar.com is live — a face-recognition photo album people fill themselves. saznak.com is registered and under construction.
What working with me looks like before the first invoice — three habits that decide whether a system survives its second year.
Every non-obvious decision carries a comment saying what breaks if you undo it. Six months later that comment is the only thing standing between the codebase and a silent regression.
Deletions, payouts, migrations: if a step can't be verified, the operation stops rather than reporting success. A swallowed error in an irreversible path is a bug you hear about from a user, months late.
After writing a test I break the thing it covers and check that it actually goes red. A green suite that never fails is a comfort, not a signal.
Short version: engineer who can be trusted with the expensive parts, founder who has shipped and sold the whole thing.
I graduated in Computer Engineering from Çukurova University in Adana. Today I work as a fullstack and blockchain engineer, and build my own ventures alongside it.
I like the parts of software that don't forgive mistakes: payment flows, systems that can't lose a single record, dashboards that have to answer instantly. The work below is what I built at the companies I've worked with; these days I'm putting the same experience into my own ventures.
I take on work where correctness matters more than shipping the first version fast — payments, data pipelines, anything where a silent failure costs more than a delay.
Built with Next.js, deployed on Vercel
