Built under one name,since 2011.
Fourteen years engineering protocols, AI systems, and developer infrastructure — shipping them as products under our own name.
How We Work
We build and run our own products end-to-end — designed, engineered, and operated in-house, not handed off. Today that's AgentKarma, Navola, and Servel; over fourteen years it's been a lot of things.
The work lives where it's hardest to fake: protocol engineering, AI systems, and the infrastructure underneath them. We write the code, ship it under our own name, and stay on it through the launch and the year of edits that follows.
The team is small by design — small enough that everyone touching a product would put their own name on it. Nothing leaves the building before someone here would run 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.
Three things, mostly: protocol engineering, AI systems, and the developer infrastructure that holds them up. Right now that looks like AgentKarma (a reputation layer for autonomous on-chain agents), Navola (AI-assisted on-chain trading), and Servel (a distributed deployment orchestration platform) — but the products change. We design, build, and operate each one end-to-end.
Different domains, one method: sit with the problem until it's understood, write the code ourselves, ship under our own name, and stay on it — through the launch, the first real users, and the year of edits that follows. The stack changes; the standard doesn't.
What We Don't Do
We're not a services shop. We don't do staff augmentation, take open RFPs, or bill by the hour against someone else's roadmap — that's hard to reconcile with shipping under our own name. We'd rather build less of the right thing than more of the wrong kind.
The Long Story
Notes from 2011
Kerem Noras
Founder ' Executive
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.
Different work every year. Same bar.
Kerem Noras
Founder ' Executive, 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 keep building and operating our own products — protocols, AI systems, infrastructure — with a team small enough that everyone on it would put their name on what ships.
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