agents apologize. they don't explain. janus fixes that.
The infrastructure layer for your agents and agentic workflows. You can already see what your agents did. janus is what happens when you need to change your mind about it
The other day, an agent of ours kept a shared config doc updated, small edits, maybe a dozen in a week. Then something broke, and the fix was in there somewhere. We just couldn't tell which edit caused it, or how to undo that one without losing the eleven that were still right. So we rebuilt it by memory, best guess, piece by piece. It worked. But we weren't fixing anything, we were reconstructing something that already existed, just not anywhere we could actually see or use it. That's the real gap. Not knowing what an agent did. Knowing which one thing to undo, and undoing just that.
janus solves this exact gap. The missing infrastructure layer for your agents. Not another way to watch what your agents do, or a way to get accountability from them, but a way to step in and fix it, without starting over.
early beta access
Fill the form to get into our waitlist for trying out the beta version of janus. Access would be granted on a rolling basis
Infrastructure for agents and agentic workflows, a layer that sits underneath your workflow
We want janus to be local-first. Thats the reason we would roll out the beta version with byok cli + tui/localhost web interface
janus is completely local-first byok cli. You control your own data and nothing ever goes to us.
Not right now. We are currently building in full stealth mode. That decision comes later.
We're in early development. Early access is the fastest way to get in as things open up no fixed date yet, we'd rather ship it right than ship it on time.
Pricing isn't finalized. If that matters to you, early access is the best way to have a say in it before it's locked.
Behind janus are 2 college students who encountered a problem and wish to solve it not just for themselves but for all us