MODU is
- A governed workflow runtime
- A local-first execution and orchestration layer
- A bridge between models, tools, apps, PCs, and phones
- A receipt and recovery system for consequential work
Product
A control layer for agents, tools, devices, and connected services.
MODU coordinates work through explicit procedures, bounded authority, durable state, and verifiable execution.
Active R&D · early validation · not generally available
Product boundary
What MODU is—and what it is not.
MODU is not presented as
- A generally available consumer assistant
- A replacement for legal, medical, or regulated professionals
- A certified compliance platform
- A claim that every experimental capability is production-ready
Core system
Four product components.
01
Governed workflows
Each workflow has a goal, identity references, allowed origins, authority policy, duplicate guard, completion criteria, and durable journal. Reversible work can advance automatically while legal, identity, financial, and destructive consequences remain explicit.
02
Local and heterogeneous compute
The platform can schedule work across local CPU/GPU resources, phones, device accelerators, and selectively used cloud services. Resource choice is part of the procedure rather than hidden behind one provider.
03
Cross-device execution
Connected apps are used directly where available. Local workers, SSH, browser sessions, queues, and device bridges handle work that requires owner-controlled machines or interfaces.
04
Result-bound verification
Execution evidence ties actions to operation IDs, workers, adapters, page or command state, and observed outcomes. Human-only gates can pause and resume without silently replaying earlier writes.
Current work
Where the platform is being exercised.
Code and system auditsConnected-service workflowsPersistent browser automationLocal-model orchestrationPC and phone workersUnreal and Blender workflowsKnowledge and memory infrastructureCompany enrolment operations
These are active development areas, not a statement that each is packaged, supported, or sold as a standalone product.
Next milestone
From infrastructure to repeatable pilots.
The immediate product goal is to select bounded workflows, define measurable completion criteria, package the required worker capabilities, and validate cost, reliability, security, and operator experience in controlled pilots.