About
Artem Okhten · Miami, Florida
I am an applied mathematics student in Miami. I moved here from Kyiv at seventeen because of the war, which is the short version of why I care more about systems that keep working than about systems that look finished. This site is where I keep my work: a resume, a portfolio of projects, and a set of twelve tools I built because I needed them and did not want to upload my files to a stranger to use them.
The tools, and the one design decision behind all of them
Every tool on this site runs inside your browser. When you drop a PDF into the PDF workspace, the file is read by your own machine, edited by your own machine and saved back by your own machine. It is never sent anywhere. The same is true of the image tools, the favicon generator, the ebook reader, the QR generator and the text tools.
That is not a policy I could change my mind about later — it is the architecture. There is no upload endpoint to point at a different server, because there is no upload. It also means the site genuinely cannot recover a file for you, cannot scan one, and cannot be compelled to hand one over. The trade is real: very large files are limited by your device rather than by a server farm, and a few operations that need serious compute are simply not offered.
I wrote these because the free alternatives mostly monetise the upload. A converter that takes your passport scan to a server you know nothing about is not free; it is paid for in a currency nobody quotes. The full detail is in the privacy policy, which is short and says the same thing in the language a policy has to use.
What I actually work on
My degree is applied mathematics, and the parts I keep going back to are statistical and stochastic modelling — the problems where the answer is a distribution rather than a number, and where being confidently wrong is the normal failure mode. Alongside that I build software: this site, tooling, and client work through Okhten Group LLC.
What ties them together is a preference for things I can take apart. I would rather understand a system at a structural level than treat it as a box that usually behaves. In practice that means I write down the measurement rather than the conclusion, and I leave the reasoning in the code where the next decision will be made. Several files in this repository carry comments recording an assumption that turned out to be wrong and what the number was that disproved it, because the alternative is making the same mistake again in six months with more confidence.
Outside that: I train, I play collegiate chess, and I repair physical things. Same instinct, cheaper feedback loop.
How this site is run
It is a Next.js application deployed on Vercel, and I pay for the hosting. Advertising on the tool pages is there to cover that cost; it is not the reason the tools exist, and no tool is gated behind it. The pages that exist to be read rather than used — this one, the privacy policy — carry no advertising at all.
Everything here is written by hand — the portfolio, the resume, the policy and one page per tool. Nothing on this site is generated in bulk, and nothing is published because a template made it cheap to publish.
Getting in touch
Email is best and reaches me directly — the address, along with the other ways to reach me and what I am currently open to, is on the contact page. If you found a bug in one of the tools, that is a message I will always answer; knowing which browser and which file broke it saves us both a round trip.