The nNode Story

We came from different places, but we ended up in the same one—building something we believed should exist.

Dylan was coding during reserve duty. Between missions, often in the field, using a rugged hotspot to pull signal from places that barely had any. Over a year of service. And in the middle of that, he started building what would become nNode. When others slept, he opened his laptop. Not because anyone asked him to. Because he couldn't stop thinking about the problem.

Yonah grew up in the U.S., went to university there, and spent four years at Microsoft building products used by millions of people. It was stable. Challenging. Exactly the kind of job you're supposed to work toward.

In March 2024, Yonah was staffing a Taglit-Birthright trip when an attacker struck. Without thinking, he reacted and tackled him to the ground. Afterward, life didn't fit the same way. He couldn't go back to normal. A few months later, he made aliyah.

Dylan's path was different, but it carried the same weight. He grew up in Jersey and moved here in 2020 after finishing up his first startup, oCaptain. He didn't grow up knowing the army was part of his story—he chose this country and served it.

There's one more connection we didn't understand at first. Dylan didn't grow up religious. Part of his journey toward becoming religious was guided by Yonah's father, a rabbi. We didn't know each other then. But before we ever met, our lives had already been shaped in ways we couldn't see.

We met in Tel Aviv. When Yonah saw what Dylan had built, he wasn't just impressed by the quality of the code. He understood the why behind it. Autonomous systems shouldn't be reserved for companies with massive budgets and engineering teams. They should be accessible. Foundational.

On January 1st, we went full-time on nNode. Forty days later, we had an MVP in the hands of two real customers. It wasn't perfect. It worked. That was enough. We didn't spend months debating positioning. We didn't chase pivots. We built the thing we believed should exist and put it in front of someone who needed it.

nNode is a programming language and an execution engine. It runs autonomous business workflows. Instead of stitching together APIs and hoping nothing breaks, you define your logic once and let it run—reliably, repeatedly, without constant oversight. It's not a chat interface. It's not a thin AI wrapper. It's infrastructure.

We didn't start nNode under ideal conditions. We started it because the problem wouldn't leave us alone. We both walked away from stable paths to be here. And we built something we're proud of—not in spite of that, but because of it.

That's how we work.