Your application. Independent modules.
Build modular applications with C++23 and Python. Manage their lifecycle, exchange messages, and keep ownership explicit.
Documented releasev0.2.0/Stable main branch
A clear place for every responsibility
Section titled “A clear place for every responsibility”Run modules in separate processes. Use the inherited Context for framework services. Keep lifecycle control on sockets and message payloads in shared memory.
RUNTIME AT A GLANCEC++23 / Python
VINCCentral runtimeLifecycle · Shell · Service management
↕ Socket control + bidirectional heartbeat ↕
PROCESS 01CameraSame App (Host) + Plugin
PROCESS 02AnalysisPython Module
↕Shared-memory Message BusMessage data exchanged between processes
Start with one working connection
Section titled “Start with one working connection”Define a message, build a module, and bring it up from the central Shell. C++ modules are plugins loaded in child processes of the same App executable; Python modules use an installed system interpreter.
Build and runFind the requirements, build options and release-specific instructions.
Understand ContextLearn who owns the process, the services and the callback loop.
Designed for explicit contracts
Section titled “Designed for explicit contracts”| Capability | What it provides |
|---|---|
| Message Bus | Generated message types, per-publisher rings, local push and shared-memory loans |
| Param and Log | Typed parameter caches, pump callbacks, and module-aware diagnostics |
| RPC | Typed requests and responses dispatched through the module’s pump |
| Shell | Central module commands, Tcl startup scripts and a socket interface |
OpenVinc’s main branch provides stable releases. See release status for platform validation, SDK requirements and available features.