Sovereign computing infrastructure spanning operating systems, identity, and autonomous agents. **Esver OS · Visage · Mr Haven**
Joined December 2025
- Tweets1.3K
- Following90
- Followers64
- Likes274
Pinned Tweet
Our founder on the benchmark that defined our wedge:
Repeated company workflows compiled into local executable skills; verifiable, auditable, customer-owned execution.
Reliable agents need more than bigger models. They need substrate.
Sovren Software now maintains two flagship public OSS repositories.
Visage
Linux face authentication through PAM.
Rust. v0.3.0.
Mr Haven V1
Programmable time vault infrastructure on Base.
Solidity. v1.0.2.
Different domains.
Same engineering discipline.
System architecture:
• Per-user vaults deployed as EIP-1167 minimal-proxy clones
• Shared yield routing through Aave V3
• User-defined distribution plans
• Scheduled and inactivity-triggered execution flows
• Beneficiaries specified by wallet or email via hash-locked escrow
852+ tests passing.
Vendored dependencies are pinned to deploy-time trees to support deterministic recompilation and bytecode reproducibility.
For DeFi auditors:
the source is now public.
SECURITY.md defines the disclosure workflow.
For protocol builders:
MIT-licensed interfaces and libraries are designed for composability and vendor-friendly integration.
For the Base ecosystem:
this is what production-grade digital-asset protection infrastructure looks like.
@base @CoinbaseDev @baselatam
Voice surface: @openhome | Action surface: Esver OS
Both local. Reliable computer-use agents need substrate and executable skills, not bigger models.
$0 marginal model cost. Deterministic workflows. Private context that never leaves the machine.
Design-partner conversations open.
Voice request to an @openhome speaker. A local AI books a real Delta flight end to end on a fresh Minisforum X1 iGPU. No human clicks. No cloud agent. 73 seconds. The video is the demo.
Numbers below. 🧵
The question is not whether you need privacy. The question is whether the systems you use structurally guarantee it or merely promise it.
Every piece of software you run on someone else's terms is a decision you made. Sovereignty is choosing to make a different one.
At what point does "convenient" become "dependent"? The answer is wherever you stopped being able to leave.
The system that helps you build is governed by the system you build. Self-compounding infrastructure. Not a pitch. A proof that runs continuously.
The constraint shapes the product. One founder. Sovereign infrastructure. Three domains.
If the system multiplies capability enough, team size stops mattering.
The bottleneck is not smarter agents or better models. It is the layer between them.
One person hits a ceiling not of talent but of coordination. The solution is structural, not more effort.
You own data you can delete. You control systems you can audit. You are sovereign over infrastructure you can replace. Everything else is a lease.
We do not compete on features. We compete on trust assumptions. Every piece of the stack runs on hardware you own, with keys you control.
Correctness is not optional in trust infrastructure. The safety verifier, the identity system, and the knowledge engine cannot afford undefined behavior.