Sovren Software

Sovereign computing infrastructure spanning operating systems, identity, and autonomous agents.

**Esver OS · Visage · Mr Haven**

[Sovren Software @sovren_software]

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.

[cCross @TheCesarCross]

Running a hard live-web workflow on our substrate, a cold prompted browser agent succeeded 8 out of 10 times at a median ~390s.

After we compiled it into an executable skill, the same task hit 28/30 on a fresh local iGPU at ~58s median.

The bottleneck wasn't the model. 🧵

[Sovren Software @sovren_software]

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

[Sovren Software @sovren_software]

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.

[Sovren Software @sovren_software]

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.

[Sovren Software @sovren_software]

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.

[cCross @TheCesarCross]

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. 🧵

[Sovren Software @sovren_software]

Sovereignty is the baseline. Not the premium tier. Not the enterprise add-on. The baseline.

[Sovren Software @sovren_software]

The question is not whether you need privacy. The question is whether the systems you use structurally guarantee it or merely promise it.

[Sovren Software @sovren_software]

Every piece of software you run on someone else's terms is a decision you made. Sovereignty is choosing to make a different one.

[Sovren Software @sovren_software]

At what point does "convenient" become "dependent"? The answer is wherever you stopped being able to leave.

[Sovren Software @sovren_software]

Convenience and dependence look the same until you try to leave.

[Sovren Software @sovren_software]

The cost of sovereignty is complexity. The cost of dependence is everything else.

[Sovren Software @sovren_software]

The system that helps you build is governed by the system you build. Self-compounding infrastructure. Not a pitch. A proof that runs continuously.

[Sovren Software @sovren_software]

The constraint shapes the product. One founder. Sovereign infrastructure. Three domains.

If the system multiplies capability enough, team size stops mattering.

[Sovren Software @sovren_software]

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.

[Sovren Software @sovren_software]

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.

[Sovren Software @sovren_software]

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.

[Sovren Software @sovren_software]

Correctness is not optional in trust infrastructure. The safety verifier, the identity system, and the knowledge engine cannot afford undefined behavior.

[Sovren Software @sovren_software]

Security as a property of architecture, not a product you install. The difference is whether it can be circumvented.