Active
MVM
A strict, cross-platform microVM runtime for safely executing AI agents and untrusted workloads.
Founder · Technologist · Systems Builder
I build technical companies, technical leverage, and technical trust.
I’m Ari Lerner. I work where systems software, AI infrastructure, security, and product meet—turning difficult technical ideas into things people can actually use.
Currently building secure execution infrastructure for AI agents. What I’m doing now
Selected systems
Building below the interface
Runtime boundaries, content-addressed systems, and infrastructure that makes powerful software safer and simpler to operate.
Research
Hologram
An object-first runtime exploring deterministic execution, portable artifacts, zero-copy data paths, and compute that travels with its guarantees.
Research
UOR
Research into semantic, content-addressed object identity and a topology where software can address meaning rather than storage location.
Working thesis
Power is useful when its boundaries are legible
The systems I care about make capability explicit, complexity containable, and trust inspectable.
01
Compute should be containable
Powerful workloads need hard machine boundaries, attenuated authority, and a blast radius the operator can understand.
02
Interfaces should hide the right complexity
The best infrastructure does not expose every mechanism. It exposes the guarantees people need to build with confidence.
03
Trust should be verifiable
Policy, identity, provenance, and auditability should travel with the system—not live in an operator’s memory.
Writing
Notes from the work
Essays about secure AI systems, Rust, infrastructure, learning, and the human reasons we build.
How to Build Around an Open Theorem Without Claiming It
Ambitious mathematical software can formalize the missing object, prove surrounding machinery, and record evidence while keeping the unresolved crux mechanically open.
A Registry Is a Graph, Not a Bucket
Once objects have stable identities, a registry has to preserve namespace state, relationships, atomic changes, reconciliation, and reachability—not just blobs.
A Program Should Be Able to Resume Somewhere Else
A portable suspension needs addressed state, addressed dependencies, explicit host contracts, and fresh authority when execution moves.
The long arc
Builder, teacher, operator.
I’ve built companies and systems, authored and co-authored nine technical books, taught engineers around the world, worked inside AWS innovation, and kept returning to the same question: how do we make powerful technology usable without making it careless?
The longer story- 9
- technical books authored or co-authored
- 3×
- Stripe capture-the-flag competitions
- ∞
- curiosity for systems from hardware to semantics
Open channel
Working on something technically ambitious?
I’m always interested in hard systems problems, serious open-source work, and people building new leverage without ignoring trust.