Who I am
I'm Janrau, an electronics and software engineer in Helsinki and a graduate of 42, a peer-driven school that turns out builders, not theorists. I ship production software for a living, including a GDPR-compliant scheduling product used in Finnish healthcare. The engineering behind Nurho isn't a side hustle or a course I took. It's the same discipline I apply to real systems every week.
What I'm actually good at is wiring. Give me two systems that were never meant to talk to each other and I'll find the path between them, connect them, and watch the thing come to life. That's the part I love: understand the problem, wire it up, see the bulb light up. Most of what I've built has been full systems from scratch, in code, including an AI pipeline that produces video end to end. Nurho points that same range at the boring, expensive work inside a business.
How I work
I borrow the discipline of the best engineering teams: question every requirement, delete the steps that shouldn't exist, simplify what's left, make it faster, and only then automate. Automating a broken process just makes the mess run faster. Optimize first, then build the system that removes the constraint.
And automation doesn't always mean AI. Sometimes it's a model doing real work. Often it's just a process, engineered to run itself, with no AI anywhere near it. I use AI where it earns its place and plain engineering everywhere else. The goal is the outcome, not the buzzword.
I work to a deadline. Give me a clear picture of the problem and I move hard and fast. I like direct communication, straight to the point, no guessing games. That tends to be what people remember about working with me.
Who it's for
The client I do my best work for is someone buried in work they never wanted to do, spending the day on necessary but draining tasks instead of the part of the business that actually matters to them. My job is to hand that work to a system, so you get to do more of what you love and let the machine handle the rest.
What you walk away with
I believe you should own your data and your own tools. So the system is treated like production code: branched, reviewed, tested against real data, deployed on infrastructure you own. When it's done, you get the keys: the code, the credentials, and the documentation in a repository that's yours. You can walk away anytime and keep everything running. You're not renting access to me. You own the system you run on.
Why I do it
I get inspired by great things. When I see something built really well, I want to build something that good. But what actually keeps me in this work is simpler: I like solving a problem for someone and seeing their face when it finally just works. Away from the screen I play instruments, follow sports, and stay curious about most things.
Nurho is built for service businesses in the United States, Canada, the United Kingdom, and Europe. Helsinki-based and GDPR-aware by default. A trust signal, not a limitation.
See if we're a fit or read the field notes.