I didn't wake up one day and decide to start a studio. What actually happened is that I kept having ideas faster than I could build them, and every one of them died in the same place — not in execution, in the gap between having the idea and having the first working version of it. By the time I'd scoped it properly, half the excitement was gone, and the thing I eventually shipped, if I shipped it at all, was a watered-down version of what I'd actually wanted to make.

Sarv is my answer to that gap. Not one product — a handful of them, plus the tooling and taste it takes to make more of them without starting from zero every time. Kiln, the AI copilot, came directly out of watching myself do this over and over: rough idea in, shippable first version out, so the only thing left to spend real time on is the part that actually needs a human's judgment.

The name matters to me more than it probably should to anyone reading this. Sarv is short for Sarvagya, which means all-knowing, but I didn't pick it because I think any of this is all-knowing — I picked it because it's a standard to keep failing to meet. Software that reasons instead of just executing, that learns instead of staying static, that gets out of your way instead of demanding you learn its interface first. I'm nowhere near that with any single product. I'm just building toward it, one small thing at a time.

Sarv sits under Elysium, the studio I started first. Kiln, SarvTrack, Aura, DropHaus, Velo, and the rest of the smaller tools all live under that name — built because I wanted them to exist for myself first. I don't think the org chart matters much from the outside. What matters is that everything here got made because I couldn't stand having the idea and not the thing.

I write these posts for the same reason I build the products — because working through it in public keeps me honest about whether I'm actually solving something or just shipping to feel productive. Most weeks it's a bit of both. I'm trying to get better at telling the difference.