Mathew James

When we launched, Wallie was an open-source AI streamer that watches your screen, hears your audio, and reacts in character.

Now it does something I'm genuinely excited about: it PLAYS.

Wallie plays Minecraft survival live and unscripted it mines, hunts for iron, crafts, fights, and tries to survive the night, all on its own. No human at the controls, no script. And it talks the whole way through, in character, reacting to what's actually happening.

Two things make it special:

Hi Product Hunt. I am Elitza and I am the founder of own.page. We launched on Product Hunt 20 days ago, and since then, it has brought us more than 1,900 signups.

I waited a long time before launching own.page here. Not because I didn t want to, actually, I wanted it a lot. But Product Hunt always felt like one of those big platforms where, if things go well, it can really change the momentum of a product. And because of that, I kept delaying it. For more than 6 months. I was thinking too much. What if the day is too competitive? What if nobody cares? What if we launch and nothing happens?

On X, I often saw people saying Product Hunt is dead. That it doesn t bring traffic anymore. That launches don t matter like they used to. But still, I wanted to do it no matter what people are saying. Before this, I had launched own.page on smaller launchpads. And yes, they helped. They brought some users, some traffic, some attention. I m grateful for that. But honestly it was nothing like Product Hunt.

Something I have been thinking about in the AI governance space that I do not see discussed enough: provenance capture is not like most tooling categories.

With most observability or audit tooling, the reasoning is "we should have this so we're better positioned going forward." You can turn it on when the need becomes clear. You lose some history, but the tooling from that point forward is complete.

AI code provenance does not work this way.

The prompt a developer submits to Claude Code exists for a few hundred milliseconds in transit. After the model returns its response and the editor applies the change, that prompt is gone. Git records the diff. Nothing else records the origin by default. There is no reconstruct operation.