MX Framework
The engine behind MXE and MX Studio, available to build on. Native APIs for Rust and C++, and JavaScript over IPC hooks.
/ 01
The core MXE and MX Studio are built on.
MXE is a hypervisor management OS built on the MX framework, and MX Studio is its control plane. The framework is that same core, available to integrate into your own application rather than only through our products.
/ 02
Rust and C++
Native APIs for both, linked into your own binary.
/ 03
JavaScript over IPC hooks
Drive the engine from JavaScript through IPC hooks, without linking native code into your process.
/ 04
A C ABI underneath
The native APIs sit on a C-level interface, so the framework is reachable from anything that can call C.
/ 05
x86_64, aarch64, arm64e
The same cross-architecture guest support MXE and MX Studio ship: same-architecture guests run on the host's virtualisation extensions, through KVM on Linux and Hypervisor.framework on macOS, and cross-architecture guests fall to the translation engine.
/ 06
The hardware-level debug surface
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.
/ 07
Bring your own frontend
MX Studio is one consumer of the framework, not a requirement. Build the surface you need on top of the same core.
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.