Roadmap
What's New with Certo
Core Architecture Enhancements
Asynchronous USB (Pure Virtual Mode Support) (URBs): Full support for intercepting the libusb and usbfs URB (USB Request Block) lifecycle. This will natively queue and reap background memory pointers for ultra-high-speed USB virtualization.
Zero-Copy Memory(Pure Virtual Mode Support) (mmap): Support for allocating and mapping shared memory buffers. This will allow applications to read virtual hardware memory directly without invoking standard system calls, perfect for PCIe, GPU, or V4L2 video buffer spoofing.
Hardware Interrupts (Default and Pure Virtual Mode Support) (eventfd / timerfd): Native routing for asynchronous hardware “ticks” and GPIO pin triggers.
Add More native support for playing back data via raw files.
Enterprise Scaling & CI/CD
Virtual Hardware Recording (.vhr): Record actual physical hardware interactions or spoofed sessions, capturing the exact data payloads and timing of events. Testers can share these .vhr files with developers to perfectly replay and debug intermittent hardware bugs or specific edge-case scenarios. (Desktop App Feature)
Remote Hardware Broadcasting (Hub & Spoke Model): A centralized Certo daemon that runs on a lab server physically connected to rare or expensive hardware. All developers can connect their local Certo instances to this daemon, broadcasting the real hardware’s live data streams directly into their local virtualized environments. (Certo Daemon)
True CI/CD Automation: A headless CLI environment allowing you to inject Certo hardware profiles directly into cloud-hosted runners (like GitHub Actions or GitLab CI) for complete end-to-end integration testing without physical hardware. (Desktop App Feature)
Enterprise FAT Reporting Dashboard: A full web-server interface tailored for VPs, stakeholders, and customers. It will provide a clean, high-level dashboard to observe and sign off on virtualized Factory Acceptance Tests (FAT) in real-time. (Certo Daemon and Certo Webserver)
Unified Virtual Twins (Multi-Layer Testing): Evolving the .vhb ecosystem from single-target intercepts to a unified, multi-layer hardware model. A single .vhb file will contain a core simulation state machine and multiple interface bindings. This allows Software Teams to spoof high-level data (e.g., /dev/radar), Driver Engineers to spoof raw buses (e.g., /dev/i2c-1), and QA teams to inject faults into physical hardware—all synchronized against the exact same virtual source of truth. (Certo Desktop App Feature)
AI & Machine Learning
MCP (Model Context Protocol) Server: Certo will act as a safe-space sandbox for AI agents. By exposing Certo via MCP, Large Language Models (LLMs) will be able to read virtual hardware states, inject edge-case faults, and interact with the system. This enables organizations to train AI models on hardware systems to autonomously detect hardware problems and develop real-time mitigation techniques without risking physical damage. (Certo Desktop App Feature)