Many Ninja: Putting a Name on the Pile

I put up a new site: many.ninja.

What it actually is

For a few years now I’ve been building a lot of things that are all, quietly, the same thing. A Rust platform for ROM and emulator management. A Go runtime behind Emugate. A browser portal. An admin SPA that half a dozen surfaces mount into. Realtime video pipes. Auth gates. Orchestration for worker processes that need to launch, get tracked, and resume.

Individually they’re just repos. Side projects with weird names. Every one of them made sense on its own and none of them added up to anything you could point at.

Many Ninja is me pointing at it.

It’s an umbrella — a name for the body of work, so I can stop explaining each repo separately and start talking about what the whole pile of it demonstrates. Custom web platforms. Admin and operations tooling. Realtime delivery. Runtime orchestration. Backend architecture. Written across Rust, Go, Zig, and whatever the browser needed that week.

Built backwards on purpose

The thing I care about most: the site is assembled from what the code actually does, not from what I’d like to claim it does.

I’ve read enough software company websites. They all sound the same. Passionate team, cutting-edge solutions, we partner with you on your digital journey. Nobody writes that because it’s true, they write it because it’s the shape the page is supposed to be.

So I did it the other way around. I went through the repos, wrote down what capabilities kept showing up, and built the site from the ones I could back with something you can open and read. Where the proof is thin I said so — the capability map has a “strong” column and an “emerging” column, and I put things in the honest one.

Turns out when you build a company site out of evidence instead of adjectives, you end up with something closer to a map than a brochure.

The ninja joke made it in

There’s a comic on the site of a ninja holding two magnets, asking how they work.

This does not belong on a professional software company website. That’s exactly why it’s there. If I’m going to build the thing, it should feel like a real thing with a point of view — not a sterile template pretending to have one. I’d rather it be a little weird and actually mine.

Aiden, the mascot, is on the site too. He’s now at the bottom of every page here as well, which is the whole point of an umbrella.

Where things stand

janes.co — this site — stays personal. Blog posts, the résumé, whatever I’m thinking about.

many.ninja is the work. drezdin.com is where my internet persona lives. labs.drezdin.com is the labs page. emugate.org is the new home for Emugate.

The company story is still in progress and the site says so on the front page. I’d rather ship it honest and unfinished than sit on it until it’s polished into meaninglessness.

Go look: many.ninja