OS·itself
The 31-agent infrastructure that runs this entire studio.
What it is
The product is the team. Eva talks to clients, Morpheus plans, Neo + Trinity ship code, Tester gates, Zero secures, Max bills. NATS event mesh, persistent agents, on-demand workers. Eats its own dog food every day.
What the client asked for
Internal goal: build a software studio that operates as a multi-agent system instead of a team of humans. Each role is a dedicated AI agent. Stefan supervises but doesn't execute. The studio must be able to take a client from first message to invoice without human intervention.
Scope delivered
Every project ships with its full scope. No phase-2-promises, no 'foundation laying' invoices for empty product.
- 31 specialized agents (Eva, Morpheus, Neo, Trinity, Prism, Tester, Zero, Doc, Hunter, Midas, Max, Creator, Herald, Mesmer, Augur, Saul, Prophet, Fury, Dev, Atlas, Forge, Athena, Closer, Helm, Nexus, Worker, Oracle, Vitruv, Argus, Cerberus, Aegis)
- NATS event mesh for inter-agent communication
- Persistent agents (always-on) + on-demand workers (heavy lifts)
- Werkstattmappe: per-order workspace with brief, decisions, deliverables
- Cockpit dashboard for Stefan (live agent activity, queue, costs)
- Closed-loop self-improvement: Dev agent watches for capability gaps and proposes new agents to Fury (HR)
- Audit log of every decision
- Cost tracking per agent, per order, per LLM call
Stack chosen for this build. Each pick has a one-line ADR (Architecture Decision Record) in the order folder.
How it shipped
What happened
Live infrastructure. Real revenue. Real shipped products (LinkHopp, NabuLingo, EVA Voice, YA Music). The studio is its own best proof.
Want a build like OBHOLZ?
No sales calls. No 6-step funnel. Just an inbox you can actually email.