The IP Ledger: a clear line between proprietary power and community growth.
DOSFI's defensible core is closed. The node client, SDKs, and ABI are open. This is the boundary that lets DOSFI stay sovereign while the ecosystem grows on top of it.
Closed / Proprietary
8 Crown Jewels · The Defensible Core
- DOSFI RuntimeCategory Ownership
- DOSFI SchedulerDefensibility
- DOSFI RouterPerformance Moat
- DOSFI ProtocolSafety & Integrity
- DOSFI Readiness EngineReliability Moat
- DOSFI Privacy ModelTrust & Safety
- DOSFI Power/Thermal ModelDevice Safety
- Mesh-Native App RuntimeMonetization
These components are closed-source for defensibility, safety, monetization, and category ownership. They form the proprietary core that DOSFI operates — never the surface developers build against.
Open Source
Community Surface · Built In The Open
- MeshInfer Device Client (Android/iOS)Trust
- MeshInfer SDKsAdoption
- Node ClientParticipation
- Developer ToolsVelocity
- ABI SpecificationInteroperability
- Example NodesReference
- Example Mesh-Native AppsEcosystem
Open source components exist to build trust, accelerate adoption, and enable ecosystem growth. Anyone can run a node, inspect the client, and build mesh-native apps on top of the published ABI.
Why DOSFI is closed
The scheduler, router, runtime, protocol, and models are DOSFI's category-defining advantage. Keeping them proprietary protects safety, ensures device integrity, sustains monetization, and secures category ownership. A distributed OS is only trustworthy if its core orchestration cannot be forked, weaponized, or degraded.
Why the node client is open
The node client runs on your device — so it must be inspectable. Open-sourcing the client, SDKs, and ABI builds trust, accelerates adoption, and lets anyone verify exactly what runs on their hardware. The open surface grows the ecosystem; the closed core keeps it safe.
Free to run. Proprietary to operate. DOSFI is — and always will be — a MeshInfer.AI operating system.