Built under one name,since 2011.
Fourteen years of building software, infrastructure, and products — across e-commerce, finance, AI, and on-chain systems.
How We Work
Noras Technologies works selectively. The team is small on purpose, the standard is high on purpose, and the work moves slowly enough to be worth signing.
We don't take open project proposals and we don't run on a quota. We work with a small group of operators we've come to know — partners and clients who care about the work the way we do — and we say no to almost everything else.
Most of what we ship lives inside artificial intelligence, distributed systems, and financial infrastructure. None of it leaves the building before someone here would be willing to use it themselves.
Core Values
Three things we don't compromise on — written down so we have to keep them.
Integrity
Honesty is the cheap version of integrity. We do the harder part: tell clients what they don't want to hear, ship code that explains itself, and refuse to leave decisions ambiguous to look better. The short conversation now saves the long one later.
Collaboration
Most of what we ship couldn't have been built alone. We work with operators and partners we already trust, treat their constraints as our own, and stay in the room when things go sideways. Distance from the problem is how bad work gets shipped.
Continuous Learning
Fourteen years in, the work that worked five years ago doesn't anymore. We treat that as a feature, not a threat — read what's new, drop what's stopped paying off, and pay the team to spend time on things without an obvious return yet.
What We Do
End-to-end software products, built and maintained in-house.
We design, build, and maintain software products end-to-end. That means sitting with the problem long enough to understand it, writing the code ourselves, shipping it under our own name, and staying around afterward — through the launch, the first wave of real users, and the year of edits that follows.
Most of what we work on lives inside artificial intelligence, distributed systems, and financial infrastructure. The stack changes; the standard doesn't.
What We Don't Do
We don't do staff augmentation. We don't take open RFPs. We don't run agency-style turnkey delivery, and we don't bill by the hour for engineers working on someone else's roadmap.
The reason is the same as everything else: we ship under our own name, and that's hard to do honestly at outsourcing scale. We'd rather do less of the right work than more of the wrong kind.
The Long Story
Notes from 2011
Kerem Noras
Founder & CEO
I started Noras Technologies in 2011 — under my own surname. It's been personal since.
Back then nobody was calling it artificial intelligence or distributed systems. It was just whatever the next problem worth solving happened to be — a marketplace here, a trading system there, a brand identity, a piece of infrastructure that still runs today. Some of it I'm proud of. Some of it I'd rather not be reminded of. Either way, my name was on all of it, and the standard followed from there.
Fourteen years later, the company is wider. We've shipped products across e-commerce, finance, AI, on-chain infrastructure, and a handful of things I still can't talk about publicly. The thread connecting them isn't a sector or a stack — it's a refusal to ship work I wouldn't put my own name behind.
Every project we take on is one I'd be willing to have my own name attached to for the rest of my life — because in practice, it already is. That's the filter. That's why we say no more often than we say yes, and why the things we do ship tend to outlast the trends they were built into.
The work has changed many times. The standard hasn't.
Kerem Noras
Founder & CEO, Noras Technologies
Vision & Mission
Where we're going, and how we work to get there.
Vision
The technology cycle gets faster every year — the tools that defined the last five become commodity. We're not building Noras Technologies to ride a wave. We're building it to be standing when the next one breaks.
Long-lived companies are made by teams that keep showing up after the conference circuit moves on. That's the category we're competing in. Not the loudest, not the biggest — the one still in the building in twenty years.
Mission
To build software products under our own name that we'd be proud to be associated with two decades from now.
To stay close to a small number of operators who care about the work, and say no to the rest. To keep the team small enough that every person on it would still ship under their own name if they ever left.
Working on something specific?
We don't take open project proposals — but if you're building something we'd be the right team for, we want to hear about it.
Tell us what you're building