Build on the MX core.
The core behind MX Studio, MX Deep Dive and MX Executor, available to build on.
- Native
- Rust and C++A C ABI underneath
- Scripting
- JavaScript over IPC hooks
- Architectures
- x86_64, aarch64, arm64e
- Platforms
- macOS, Windows and LinuxIntel, AMD and arm64 hosts
Bring your own frontend.
MX Studio, MX Deep Dive and MX Executor are each built on the framework, but you do not need any of them. Build the surface you need on the same core.
Reach the core from Rust, C++, C or JavaScript.
Native APIs for both, linked into your own binary.
The same debug surface as MX Studio.
The surface behind MX Studio's debugger is part of the framework: registers, memory, MMIO, interrupt lines, and the device models behind them, with the same controls whether the guest is in hypervisor mode or being translated.
Read how the core works first.
- Welcome to MXWhat MX is, and how the products share one engine.
- Fusion EngineHow a guest CPU runs on WHPX, KVM or Hypervisor.framework, and what falls to software.
- How devices workMMIO, the device factory, wrappers, virtio and DMA.
- ExtensionsThe Studio extension protocol, packaging and debug methods. Needs MX Studio Pro.
Talk to us about integrating MX.
Send over what you are building and how you would use the framework. Enquiries go to the engineering side directly, not a general sales queue.